Live video production pipelines across the globe seized up this week after Microsoft’s August 2025 security update for Windows 11 introduced a crippling regression in NDI streaming. The cumulative patch, KB5063878, shipped on August 12 for Windows 11 version 24H2 (OS Build 26100.4946), and within hours broadcasters, streamers, and production engineers reported severe stuttering, lag, and frame drops—even on pristine local networks. Microsoft has confirmed the breakage and issued an urgent workaround: manually change the NDI Receive Mode from Reliable UDP (RUDP) to either TCP or legacy UDP, using the free NDI Tools suite.
The failure hits at the core of modern multi-PC live production. NDI, or Network Device Interface, is the de facto standard for moving high-bandwidth, low-latency video and audio over gigabit Ethernet without specialized capture cards. Creators use it to pipe camera feeds from a capture rig into Open Broadcaster Software (OBS), run graphics machines, feed multiviewer monitors, and connect remote contributors—all on commodity LAN hardware. When NDI transport breaks, the show stops. In this case, the break was immediate and widespread, catching everyone from solo Twitch streamers to enterprise broadcast engineers off guard.
Microsoft’s official guidance, published through the Windows release health dashboard and echoed by supporting documentation, zeroes in on the NDI Receive Mode. KB5063878 disrupts the protocol when it’s set to RUDP, the default and performance-tuned option that combines UDP’s low latency with an application-layer reliability layer. The update appears to interfere with how Windows handles that reliability traffic, producing packet-handling delays or retransmission storms. The result is a constant stutter that tears apart lip sync, makes multi-camera switching impossible, and frequently forces show producers to abort transmission.
The symptom is especially vicious when using Display Capture in OBS—a common setup for game streamers, presentation hosts, and anyone sharing application windows. In these configurations, the stutter becomes unworkable almost immediately. Users in community forums, broadcast engineering subreddits, and vendor channels reported the issue within hours. OBS contributor threads and vMix support boards independently confirmed the same pattern: a clean pre-update system would push flawless NDI feeds, but after KB5063878 installed, the feeds became a slideshow. Reverting the update or switching transport modes instantly restored smooth playback.
NDI Transport Modes and What Went Wrong
To understand the mitigation, you need to grasp the three transport strategies NDI offers and why RUDP matters. NDI’s Access Manager exposes a Receive Mode that every NDI-aware application reads from a shared configuration file. The options are:
- RUDP (Reliable UDP): The default. It sends video data via UDP datagrams but layers a custom reliability mechanism on top—lost packets are retransmitted, head-of-line blocking is avoided, and latency stays low. This is ideal for most production LANs because it balances speed with integrity without hitting TCP’s full overhead.
- UDP (Legacy): Plain, connectionless datagrams. No retransmissions, no reliability. It’s the lowest overhead mode and shines in zero-loss networks, but any packet loss shows as visible glitches.
- Single TCP: Full TCP stream. It guarantees delivery and order, but at the cost of higher latency and the possibility that a single lost segment stalls the whole stream until retransmission. TCP also copes better with network middleboxes that mangle UDP.
Before KB5063878, the trusty RUDP mode delivered buttery-smooth video. After the update, that same mode became a source of constant micro-freezes. The root cause hasn’t been detailed by Microsoft in public, but engineers familiar with the Windows network stack suspect a timing change in socket processing or a new security validation path that inadvertently throttles or reorders the RUDP acknowledgment traffic. What’s clear is that the reliability layer—designed to fix occasional packet drops—is now misfiring continuously, turning a safety net into a performance trap.
The workaround, therefore, is to sidestep RUDP entirely. By switching the Receive Mode to Single TCP or UDP (Legacy), you remove the broken component from the equation. TCP’s own reliability is handled by the kernel’s mature TCP implementation, which remains unaffected. UDP Legacy just forgoes reliability altogether, which is a viable tradeoff on tightly controlled, high-quality LAN segments.
Step-by-Step: Fixing the Stutter Right Now
Microsoft’s advisory, corroborated by NDI’s official documentation, outlines a straightforward fix that any creator or IT admin can implement in minutes:
- Download and install the latest NDI Tools package from NDI’s official distribution site. The Access Manager utility is part of the suite.
- On the receiving machine—the one running OBS, Studio Monitor, vMix, or any NDI client—launch NDI Access Manager.
- Click the Advanced tab.
- Locate Receive Mode and change it from RUDP (the default) to either Single TCP or UDP (Legacy).
- Press OK to save the configuration. NDI writes the change to
%programdata%\\NDI\ di-config.v1.json. - Completely restart all NDI-receiving applications. This is critical: NDI only reads the config file at application startup; running programs will not pick up the change automatically.
- Repeat steps 2–6 on every machine in your NDI chain that receives video, not just the main studio PC. This includes remote contribution endpoints, monitoring stations, and playback machines.
After applying this change, the vast majority of users report that NDI streams recover instantly. Test your full workflow—especially if you rely on Display Capture—before going live. A sustained 10–15 minute trial in your exact capture mode is the safest insurance.
Important tradeoffs:
- Single TCP is the safest one-click fix for networks with strict firewalls or Wi-Fi segments, but it adds measurable end-to-end latency and will exhibit head-of-line blocking if any packet loss occurs. For tightly synchronized multi-camera productions or low-latency gaming streams, you might see a slight drift.
- UDP Legacy preserves the lowest latency but offers zero retransmission. On a pristine, wired gigabit LAN with negligible packet loss, it works beautifully. Any network hiccup, however, will manifest as visible corruption.
Choose the mode that fits your environment. For most home and small studio setups, Single TCP is the path of least resistance and greatest network compatibility.
Risk Assessment and Operational Impacts
While the transport mode switch is simple for a single PC, the incident exposes a fragility that reverberates across professional live production:
- Security vs. availability: Uninstalling the security rollup restores RUDP functionality, but that removes all the security fixes shipped in the August cumulative update, including likely zero-day patches. Rolling back a security update on a production machine increases exposure and violates most compliance policies. The transport switch is the recommended first line of defense; resort to uninstall only if the latency tradeoffs are unacceptable and you have compensating controls in place.
- Latency sensitivity: Productions with stringent sync requirements—e-sports casting, IMAG feeds, multi-panel talk shows—must validate that the switch to TCP does not introduce a drift that irritates viewers or disrupts automated replay systems. UDP Legacy might be better here, but only after network testing.
- Remediation scale: A single streamer can fix their setup in one sitting. A distributed broadcast team with dozens of machines across subnets faces a massive coordination challenge. IT must push the configuration change via management tools or on-site support, often in a pre-show window with zero room for error.
- Coincident regressions: This same update brought unrelated but severe issues: Windows recovery and reset workflows broke for some, and certain NVMe SSDs reportedly dropped offline under heavy sequential writes. While the NVMe problem is hardware-specific, its presence alongside the NDI stutter complicated initial triage—systems that were both stuttering and losing storage were especially hard to diagnose. Administrators should treat KB5063878 as a high-risk patch and block it from production rings until a permanent fix addresses all known regressions.
Community and Vendor Echo Chamber Confirms the Scope
Within 48 hours of the Patch Tuesday release, multiple independent actors had reproduced the NDI failure and validated Microsoft’s workaround. This consensus is critical because it shifts the blame unequivocally to the OS update rather than NDI, OBS, or network hardware.
- vMix support channels posted direct confirmation that switching from RUDP to TCP resolved the issue, and they linked to Microsoft’s advisory.
- NDI Tools documentation for Access Manager explicitly explains that Receive Mode changes only take effect after client restart, matching the recommended procedure perfectly.
- OBS community forums and the broader r/VIDEOENGINEERING subreddit collected dozens of reports with identical symptoms, each resolved by the transport switch or by uninstalling the KB.
- Windows Report, a major Windows news outlet, published the first widely read synthesis of the problem, including the exact steps many community members had already discovered. That article, quoting Microsoft’s guidance, became the reference point for most subsequent coverage.
This broad independent corroboration means that if you’re affected, you’re not chasing a local network ghost. Follow the known fix, and your feeds will steady.
A Permanent Fix and the Known Issue Rollback Mechanism
Microsoft has publicly acknowledged the problem and confirmed an active investigation. No timeline for a permanent patch has been shared, but historical patterns provide clues. For high-severity regressions that cannot be resolved with a simple configuration change, Microsoft often deploys a Known Issue Rollback (KIR). A KIR is a small, targeted fix that can be pushed through Windows Update or controlled via Group Policy and Intune, effectively rolling back the specific offending change without removing the entire cumulative update. This is the preferred path for enterprise customers because it maintains all other security fixes.
The company has used KIRs for similar network-stack regressions in the past, sometimes within a week of acknowledgment. Monitoring the Windows release health dashboard and the official KB article for KB5063878 is the best way to catch a KIR or a new cumulative that explicitly lists this fix. In the meantime, the transport mode switch is the stable bridge.
Recommendations for Every Tier of User
Solo creators and small teams
- Pause Windows Update if KB5063878 hasn’t reached you yet. Defer feature updates for 30 days in Settings > Windows Update > Advanced options.
- If already updated, install NDI Tools, switch Receive Mode to Single TCP, and restart your streaming software. Do this today, not an hour before your next scheduled stream.
- Run a full end-to-end rehearsal with all sources—Display Capture, game capture, webcam—for at least 10 minutes. Watch for any new latency artifacts.
Production teams with latency constraints
- Test both Single TCP and UDP Legacy on a dedicated LAN segment. If your internal network is a flat gigabit switch with minimal hops, UDP Legacy might preserve the low latency you need without visible artifacts.
- Consider network-level workarounds: a direct 1:1 cable between capture and stream PCs, a quality managed switch with flow control enabled, or jumbo frames if your equipment supports them. These can reduce packet loss to near zero and make UDP Legacy viable.
- Do not uninstall the security update unless your risk officer signs off and you have no alternative. If you must roll back, isolate the machine from the internet or apply strict firewall rules to limit exposure.
IT administrators and enterprise broadcast ops
- Block KB5063878 from approval rings in WSUS or Windows Update for Business until Microsoft resolves all high-profile regressions (NDI, storage, recovery).
- Pilot the NDI Receive Mode change on a representative subset of machines. Validate that your Group Policy or management tooling can push the NDI config file change automatically—the JSON file at %programdata%\\NDI\
di-config.v1.json can be scripted via PowerShell.
- Prepare a KIR deployment playbook now. If Microsoft releases a KIR, you’ll need to apply it through your existing endpoint management stack quickly. Make sure your security team signs off on a “known issue rollback allowed” policy in advance.
- Document all compensating controls if you must remove KB5063878 from any machine. That documentation should include the specific security vulnerabilities mitigated by the update, the compensating controls in place, and a timeline for reinstallation or replacement.
Looking Ahead: The Fragile Symbiosis of OS Patches and Niche Workflows
KB5063878 is a stark reminder that Windows updates, however carefully tested, can fracture specialized, latency-sensitive ecosystems. NDI is not an obscure protocol—it’s the backbone of an entire segment of the content creation industry—yet the regression slipped through the pre-release validation pipeline. Whether that points to insufficient testing coverage for UDP-based reliability protocols, or a broader challenge in simulating real-world multi-PC production environments, the result was same-day chaos for thousands of professionals.
The swift diagnostic and mitigation from Microsoft and the NDI community is commendable, but the episode raises strategic questions. Should such performance-critical protocols have automated health checks built into the OS? Could Windows feature an “update guard” that detects NDI usage and pauses deployment until the user confirms compatibility? And how can independent developers like NDI better collaborate with Microsoft during Insider builds to catch these breaks before general availability?
For now, the priority is restoring reliable live video. The fix is straightforward, and the confirmed recovery rate is high. Every NDI user should take ten minutes today to switch their Receive Mode and restart their apps. The shows must go on—and with a quick config change, they will.<｜end▁of▁thinking｜>{