Windows 11 KB5063878 causing major streaming issues on OBS NDI, Microsoft shares workaround

The latest August Patch Tuesday Windows 11 24H2 KB5063878 update has been an eventful one for sure. The first major concern hit us in the form of SSD issues where something in the latest update is triggering Phison controller-based NVMe drives to potentially corrupt user data.

Interestingly in the comments of the article, one of Neowin's long-time forum members Jaybonaut, pointed out that OBS streaming via NDI also broke following the KB5063878 update.

Now, Microsoft has confirmed the issue when using Network Device Interface (NDI) for streaming or transferring audio and video feeds between PCs. According to the company, users may experience "severe stuttering, lag, and choppy playback, even under low-bandwidth conditions." The problem has been observed in popular streaming apps such as Open Broadcaster Software (OBS) and NDI Tools, with the impact most noticeable when the “Display Capture” feature is enabled.

For those not familiar, NDI is a widely used protocol for transmitting high-quality, low-latency video and audio over standard networks, making it a staple in live production, remote collaboration, and professional streaming setups. Any disruption to its performance can have significant consequences for broadcasters, content creators like streamers, and production teams who rely on real-time feeds.

The company has explained that the problem appears to be linked to the default NDI Receive Mode, which uses Reliable User Datagram Protocol (RUDP) for data transport.

So, as an interim measure, Microsoft recommends manually changing the NDI Receive Mode to use either Transmission Control Protocol (TCP) or standard User Datagram Protocol (UDP) instead of RUDP. The tech giant has pointed to a newly published advisory on the official NDI website that shows detailed steps on how to proceed:

1. Download and install the free NDI Tools pack.

    

2. Launch the NDI Access Manager app.

    

3. Go to the Advanced tab.

    

4. Change Receive Mode to Single TCP or UDP, then press OK.

    

5. Repeat on any other affected computers.

Microsoft has stated that it is actively investigating the cause of the problem and will provide further information when available. You can find the issue here on Microsoft's official Windows health dashboard website.

Source

Hope you enjoyed this news post. Feedback welcome.

Posted Saturday 23 August 2025 at 5:41 am AEST (my time).

News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of July): 3,458

RIP Matrix