Microsoft has acknowledged a new, practical regression introduced by the August cumulative update for Windows 11 (KB5063878) that can cause severe stuttering, dropped frames, and choppy audio/video in NDI‑based streaming flows — a problem that disproportionately affects multi‑PC capture and live‑production setups and for which a vendor‑recommended workaround is already available. rview
Microsoft published the August cumulative update for Windows 11 version 24H2 (identified as KB5063878, OS Build 26100.4946) on August 12, 2025 as part of the regular Patch Tuesday rollup. The package bundled security fixes and a servicing‑stack update intended to keep devices current and protected.
Within days, multipnd vendor advisories converged on a single, reproducible symptom set: NDI (Network Device Interface) video streams between PCs can stutter, lag, or drop frames even on healthy LANs, and the problem is especially visible when the source uses Display Capture in tools like OBS Studio. Microsoft added an entry to its Release Health advisory to confirm the behavior and to point customers toward a temporary mitigation while engineering investigates a permanent remedy.
This is not the only problem tied to the rprise deployment failures and storage regressions have also been reported and tracked — but the NDI regression has been one of the most visible because it directly interrupts live production workflows.
Separate community and vendor‑reported incidents described a more severe storage regression in which certain NVMe SSDs could disappear from the OS during sustained, large sequential writes (commonly reproduced at thresholds around ~50 GB). Those storage reports prompted vendortigation. At the time the primary community reporting circulated, the storage failure cluster had not been universally reproduced at scale and required coordination between Microsoft and SSD vendors to confirm root cause and deliver firmware or software fixes. Treat these storage claims with caution until device vendors or Microsoft publish a formal technical attribution.
Why this matters to admins: enterprise update pipelines exercise different code paths than consumer Windows Update. A regression that impacts WSUS or SCCM can stall entire fleets and force rushed mitigations; conversely, pausing security updates at scale is also risky. Microsoft has historically upatches, and re‑releases to address distribution regressions quickly, but the balance between operational stability and security is delicate.
For production teams the prudent approach is clear: test the recommended transport change immediately, avoid uninstalling security updates where possible, and keep a close watch for Microsoft’s permanent fix or vendor updates. At the same time, administrators should remain alert to other August update regressions (WSUS deployment failures and community‑reported storage anomalies) and treat those with the same mix of urgency and caution: investigate, collect diagnostics vendors before taking irreversible action.
The next few days will be critical for both Microsoft and the vendor ecosystem to close this loop: a permanent patch that preserves low‑latency NDI behavior without undoing important security hardening is the only fully acceptable outcome for creators, IT teams, and the broader Windows ecosystem.
Source: thewincentral.com Microsoft confirms new Windows 11 issues post KB5063878 update
Source: Techweez Windows August Update Causes Streaming Issues: Here’s How to Fix It
Microsoft published the August cumulative update for Windows 11 version 24H2 (identified as KB5063878, OS Build 26100.4946) on August 12, 2025 as part of the regular Patch Tuesday rollup. The package bundled security fixes and a servicing‑stack update intended to keep devices current and protected.
Within days, multipnd vendor advisories converged on a single, reproducible symptom set: NDI (Network Device Interface) video streams between PCs can stutter, lag, or drop frames even on healthy LANs, and the problem is especially visible when the source uses Display Capture in tools like OBS Studio. Microsoft added an entry to its Release Health advisory to confirm the behavior and to point customers toward a temporary mitigation while engineering investigates a permanent remedy.
This is not the only problem tied to the rprise deployment failures and storage regressions have also been reported and tracked — but the NDI regression has been one of the most visible because it directly interrupts live production workflows.
What Microsoft confirmed and what that means
The nt
Microsoft’s Release Health entry for the Windows 11 24H2 update explicitly lists a new problem titled “Problems with NDI streaming performance after installing the August 2025 update.” The entry describes the symptoms — severe stuttering, lag, and choppy audio/video when using NDI, particularly when Display Capture is enabled — and states that engineering is actively investigating. Microsoft also identifies the likely trigger as the interaction with NDI’s default transport mode, and the company points affected users to vendor guidance for a temporary mitigation.Affected platforms and KB mapping
The confirmed scope calls out Windows 11 verswith KB5063878 and notes related behavior in some Windows 10 servicing branches where companion KBs were shipped. That means both creator rigs running Windows 11 and mixed Windows 10/11 studio environments need to evaluate their exposure.Immediate practical impact
For creators, broadcasters, and AV teams the observed failure is not mereup; it is an operational problem. Multi‑PC NDI workflows typically split capture, encoding, graphics, and monitoring across machines. When the transport layer exhibits jitter or retransmission storms, the result is periodic freezes, audio drift, and dropped frames — the precise symptoms organizers have reported in live scenarios. Microsoft’s and NDI vendor notes emphasize that the issue is transport-specific rather than affecting streaming services themselves: consumer playback on services like YouTube, Netflix, or Disney+ is not implicated.Technical primer: NDI transports and why this breaks things
How NDI moves video
NDI supports multiple transport ncy and reliability:- RUDP (Reliable UDP): NDI’s modern default in many setups, designed to keep latency low while incorporating application‑level reliability (sequencing, selective retransmits).
- UDP (Legacy): Unacknowledged datagram mode — lowest overhead but no retransmission guarantees.
- Single TCP: Ordered and reliable TCP transport — higher latency potential but more robust under loss.
Plausible failure mechanics
While Microsoft has not yet published a root‑cause technical deep dive, the symptoms suggest a subtle mismatch betransmission heuristics and changes introduced in the updated networking or transport stack. RUDP attempts to manage timing, retransmissions, and pacing to keep latency low; if scheduling, buffering, or packet‑timing behaviors in the OS change, those heuristics can oscillate — causing retransmission storms, buffer over‑ or under‑flows, and the micro‑pauses streamers see as stutter. This is an informed inference consistent with the transport‑specific nature of the reports but should be treated as provisional until Microsoft releases detailed analysis.How to mitigate the issue now (step‑by‑step guidance)
The vendor‑recommended mitigation is to change NDI’s Receive Mode on affected machines so that streams following steps summarize practical ways to apply that mitigation; UI labels and exact menu paths can vary by NDI version and by the third‑party plugin, so treat these as procedural guidance rather than exact key‑press recipes.- Check whether the machine has installed the August cumulative update (KB5063878). If it has, assume NDI flows that default to RUDP could be impacted.
- In NDI Tools or NDI Access Manager:
- Open NDI Tools (or the NDI Access Manager app).
- Find the Receive Mode or similar transport configuration option in Advanced or *Preferenceceive transport from RUDP to UDP (Legacy) or Single TCP.
- In OBS Studio (NDI Source / NDI plugin):
- Add or edit the NDI Source properties.
- Look for a Receive Mode, Transport, or NDI Mode field and select Single TCP or UDP (Legacy) instead of the default RUDP.
- Restart the streaming/encoding applications and validate end‑to‑end.
- Run local test captures with Display Capture in the scene to confirm the stutter disappears.
- Test both low‑latency and normal capture scenes because the issue has been reported to be more visible with Display Capture.
- If the UI in your NDI/OBS builds differs, consult the vendor documentation for the exact path — the mitigation principle is the same: avoid RUDP until the update is fixed.
- Some NDI features and low‑latency behaviors are tuned for RUDP; switching to TCP can increase latency slightly. Measure your end‑to‑end latency before going live.
- Changes may be required onthe receiver depending on how your workflow is configured.
- If you rely on third‑party capture appliances, check vendor guidance and firmware/driver updates before modifying settings.
Operational guidance for creators and production teams
- Test in a controlled environment first. Apply the Receive Mode change to a test pair of machines and run capture/playback scenarios that match real‑world latency afer configuration changes over uninstalling security updates.** KB5063878 includes security fixes that address a large number of vulnerabilities; removing the update creates a measurable security risk, especially for systems tied to corporate Active Directory or public internet exposure. Microsoft’s security weight for the August slate makes an outright rollback nontrivial.
- Document changes and have a rollback plan. If switching transports introduces unacceptable latency, preserve the ability to revert quickly and be ready to apply the fix from Microsoft when released.
- Coordinate with your team’s network admin. So packet inspection, or appliance‑level handling that can interact with transport behavior. Inform network staff of the change so they can monitor for retransmission storms or flow anomalies.
- If you run large production rigs, schedule redundancy. Where possible, avoid live events that rely on unknown or untested NDI paths until the update is resolved; prefer local capture + hardware encoders for critical streams.
Broader context: other August update regressions and the enterprise picture
The NDI streaming regression is one of several reliability problems that surfaced after the August cumulative updates. Microsoft also acknowledged an enterprise deployment regression where some systems installing the update via WSUS/SCCM saw failures logged as 0x80240069; Microsoft deployed mitigations via Known Issue Rollback (KIR) and guidance for administrators to recover affected distribution flows.Separate community and vendor‑reported incidents described a more severe storage regression in which certain NVMe SSDs could disappear from the OS during sustained, large sequential writes (commonly reproduced at thresholds around ~50 GB). Those storage reports prompted vendortigation. At the time the primary community reporting circulated, the storage failure cluster had not been universally reproduced at scale and required coordination between Microsoft and SSD vendors to confirm root cause and deliver firmware or software fixes. Treat these storage claims with caution until device vendors or Microsoft publish a formal technical attribution.
Why this matters to admins: enterprise update pipelines exercise different code paths than consumer Windows Update. A regression that impacts WSUS or SCCM can stall entire fleets and force rushed mitigations; conversely, pausing security updates at scale is also risky. Microsoft has historically upatches, and re‑releases to address distribution regressions quickly, but the balance between operational stability and security is delicate.
Risk assessment: immediate, medium, and long‑term
Immediate risks
- Live productions and classroom capture setups are at high operational risk because the NDI regression directly affects multi‑PC capture and Display Capture scenarios.
- Small studios and one‑person creators who rely on a single mactform are typically less affected unless they route capture between PCs using NDI.
Medium‑term risks
- Enterprise update fatigue. Frequent rollbacks or emergency mitigations erode trust in the update pipeline and increase administrative burden.
- Potential data integrity exposure if the SSD disappearance reports are confirmed and correlate with actual file corruption — though this remains a contested and undert scale and should be treated cautiously until corroborated by vendors.
Long‑term implications
- OS/firmware coordination matters more than ever. Complex interactions between host drivers, OS transport stacks, and device firmware are becoming a recurring theme; fixes may require joint Microsoft‑vendor engineering across multiple layers.
- Update delivery design tradeoffs — staged deployments, KIRs, and telemetry gating ually improved to catch environment‑specific regressions before they hit production workloads.
Checklist for administrators and production engineers
- Verify device patch status and identify which endpoints have KB5063878 installed.
- If your workflow uses NDI across machines, change NDI Receive Mode from RUDP to UDP (Legacy) or Single TCP on affected machines and validate.
- For WSUS/SCCM‑managed fleets experiencing install failures, consult Microsoft’s release‑health guidance and apply KIR or the re‑released package as recommended.
- For large file transfer or heavy I/O workloads, adopt a conservative posture:uential writes on production devices until vendors provide clarity on any storage regression reports. Flag any incidents to vendor support with logs and SMART dumps.
- Monitor vendor advisories (NDI vendor, OBS plugin maintainers) and Microsoft’s Release Health page for permanent fixes and OOB updates.
Why you should not hastily uninstall the update
It is tempting to remove a recent cumulative update that appears to break a workflow, but KB5063878 patched dozens of vulnerabilities and included fixes that contribute to platform security. Microsoft’s August slact CVEs that can affect Kerberos and domain escalation scenarios — the kind of fixes that organizations should be careful to forgo without a considered compensating control. If you must avoid the update on a production machine, weigh that decision against exposure and consider isolating the device rather than leaving it connected to business networks.What to watch for next
- A Microsoft technical root‑cause statement or a re‑release that addresses the RUDP interaction directly.
- Vendor‑side updates from the NDI maintainers and third‑party plugin authors (NDI Tools, OBS NDI plugin) that may change defaults or add finer‑grained transport selection.
- SSD vendor firmware updates or Microsoft guidance if storage regressions are confirmed to be tied to the updates; utorage reports as high‑priority but partially verified alerts.
Conclusion
The August cumulative update for Windows 11 (KB5063878) brought with it a practical and high‑visibility regression for creators and broadcasters: NDI streams using RUDP can stutter or drop frames, especially when Display Capture is involved. Microsoft has confirmed the issue on its Release Health page and has pointed to a vendor‑recommended mitigation: switch NDI Receive Mode away from RUDP to UDP (Legacy) or Single TCP whilea permanent fix.For production teams the prudent approach is clear: test the recommended transport change immediately, avoid uninstalling security updates where possible, and keep a close watch for Microsoft’s permanent fix or vendor updates. At the same time, administrators should remain alert to other August update regressions (WSUS deployment failures and community‑reported storage anomalies) and treat those with the same mix of urgency and caution: investigate, collect diagnostics vendors before taking irreversible action.
The next few days will be critical for both Microsoft and the vendor ecosystem to close this loop: a permanent patch that preserves low‑latency NDI behavior without undoing important security hardening is the only fully acceptable outcome for creators, IT teams, and the broader Windows ecosystem.
Source: thewincentral.com Microsoft confirms new Windows 11 issues post KB5063878 update
Source: Techweez Windows August Update Causes Streaming Issues: Here’s How to Fix It
