In August 2025, Microsoft released cumulative updates for both Windows 11 and Windows 10 that introduced significant performance issues in NDI (Network Device Interface) streaming. These updates, specifically KB5063878 for Windows 11 and KB5063709 for Windows 10, were meant to improve system stability and security but have caused notable disruptions in the streaming community. Users of popular OBS software and other NDI tools reported significant lag, stuttering, and quality degradation when attempting to stream audio or video between devices over a network. The issue affects not only high-bandwidth environments but also those with limited bandwidth, highlighting its pervasive nature across different use cases. Microsoft acknowledged these problems on their Windows Release Health Dashboard and have provided an interim workaround while they investigate a long-term solution.
Stream Performance Deteriorates After Update – Troubleshooting Tips | Support Forums
This recent issue highlights the delicate balance between security updates and user experience in modern operating systems. As someone who frequently deals with various software solutions, I’ve found that these kinds of problems often lead to frustration among users but also create opportunities for companies offering alternative streaming solutions or repair services. It’s crucial for Microsoft and other major players in the tech industry to maintain transparency and provide effective support during such disruptions. While it’s unfortunate for those affected by this issue now, it serves as a reminder of why robust testing before updates is so important. Companies that can quickly address user concerns will likely see an increase in loyalty and trust from their customer base.
Similar questions
What are cumulative updates?
When were the problematic updates released?
Which Windows versions are affected?
What is NDI and how does it work?
Why did Microsoft release these updates?
What specific issues do users face with streaming?
Is this problem consistent across different network environments?
Where can I find information about Microsoft acknowledging the issue?
Are there any temporary fixes available for now?
When will a permanent solution be ready?