Windows 11 August 2025 KB5063878: AutoCAD Admin Prompts & NDI/OBS Stutter

Microsoft has acknowledged two separate issues introduced by the August cumulative update for Windows 11 version 24H2 (KB5063878): an AutoCAD launch problem that triggers an unexpected administrator permission prompt, and a streaming regression that causes severe lag or stutter in NDI-based audio/video feeds used by OBS and other tools. While both bugs appear to hit specific workflows rather than the broad consumer base, their impact is outsized in schools, labs, and production environments where standard user accounts and multi‑PC streaming rigs are common. (windowslatest.com, bleepingcomputer.com)

Overview​

The August 12 cumulative update for Windows 11 24H2, KB5063878 (OS Build 26100.4946), is a security rollup layered on July’s preview and servicing stack updates. It delivers routine hardening and reliability fixes—but also coincides with a cluster of regressions now coming to light in vendor advisories and Microsoft’s release health notes. On Windows 10, the parallel Patch Tuesday updates—KB5063709 (22H2) and KB5063877 (LTSC 2019)—share some of the same “known issue” fingerprints, particularly around recovery and NDI streaming.

• Windows 11 24H2: KB5063878, OS Build 26100.4946.
• Windows 10 22H2: KB5063709, OS Builds 19044/19045.6216.
• Windows 10 LTSC 2019: KB5063877, OS Build 17763.7678.

Beyond the two headline issues (AutoCAD and NDI/OBS), admins should also be aware of unrelated August regressions affecting recovery tools and, in some reports, SSD behavior under heavy write workloads—topics we’ll examine for completeness in the sections that follow. (bleepingcomputer.com, tomshardware.com, windowscentral.com)

---

The AutoCAD admin-prompt bug: what’s happening​

The symptom​

After installing KB5063878 (and, in some environments, related August updates), launching AutoCAD products can invoke an unexpected MSI action and raise a User Account Control (UAC) dialog requesting administrator permission. In schools and labs where students use standard accounts, that prompt is a hard stop: canceling it can throw MSI errors such as 1730 and the app does not open. Reports indicate the behavior is reproducible on clean student profiles and, sporadically, even on some administrator profiles.

Products and updates implicated​

• Affected Autodesk titles reportedly include AutoCAD 2022–2026, plus Civil 3D and Inventor in that range.
• Triggering Windows updates include Windows 11 KB5063878 and (in some deployments) KB5063875/KB5064010; on Windows 10, KB5063877/KB5063709 have been observed to behave similarly.

Microsoft confirmed to Windows Latest that it is aware of the AutoCAD behavior and is working with Autodesk on a fix. At the time of writing, the primary vendor-endorsed mitigation is to roll back the offending Windows update and pause quality updates for a short window while a correction is readied. That is a blunt instrument—especially for security rollups—but for shared labs and teaching spaces it restores service immediately. (windowslatest.com, ithome.com)

Why this matters to IT and teaching labs​

• Standard user baselines: Many academic and corporate labs enforce non‑admin accounts; a forced UAC gate effectively de‑authorizes AutoCAD for the cohort that needs it.
• MSI repair traps: When an update flips a state that triggers an MSI self‑repair, Windows Installer can demand elevation if the action touches machine‑scope locations—exactly the kind of scenario that surfaces UAC prompts and error codes like 1730 on cancellation.
• Operational blast radius: Because profile resets don’t clear the prompt, the workaround burden shifts to IT—either elevate accounts temporarily, script per‑machine rules, or remove the LCU.

Context: earlier AutoCAD compatibility holds​

This is not the first AutoCAD hiccup on Windows 11 24H2. Earlier this year, Microsoft placed and then lifted a safeguard hold that prevented some devices with AutoCAD 2022 from updating to 24H2 due to launch failures. While that issue and this month’s UAC/installer prompt are distinct, the recurrence underscores how delicate complex CAD suites can be when OS plumbing shifts.

---

Microsoft confirms NDI streaming stutter with OBS and others​

The symptom set​

Microsoft has acknowledged that the August security updates can degrade NDI (Network Device Interface) transport, yielding “severe stuttering, lag, and choppy audio/video,” particularly when the source PC uses Display Capture in tools such as OBS Studio or NDI Tools. The behavior shows up even on low‑bandwidth loads, pointing away from a simple throughput cap and toward timing or queueing side effects in the networking stack.
The pattern aligns across independent reports and vendor notes: the regression primarily affects NDI connections using Reliable UDP (RUDP). When NDI Receive Mode is switched to legacy UDP or Single TCP, streams stabilize; when left on RUDP, traffic can drop or jitter in regular intervals. Microsoft’s release health communication and third‑party coverage converge on that fingerprint. (bleepingcomputer.com, neowin.net)

Quick, vendor‑aligned workaround​

Until an OS‑level fix is shipped, Microsoft and the NDI team recommend forcing NDI to use UDP or Single TCP instead of RUDP. Here is the step‑by‑step process that creators and IT can deploy quickly:

• Install NDI Tools (if not already present).
• Open NDI Access Manager on the receiving host.
• Switch to the Advanced tab.
• Set Receive Mode to Single TCP or UDP, then click OK.
• Restart affected NDI‑using apps (OBS, vMix, Studio Monitor) so they pick up the change.

Practical trade‑offs:

• Single TCP is the safest fallback across mixed network gear but can add latency and is susceptible to head‑of‑line blocking under loss.
• UDP preserves latency on clean LANs but forgoes RUDP’s recovery logic; use it on a stable, low‑loss segment.

Why RUDP would be sensitive to OS changes​

RUDP adds application‑layer reliability and pacing atop UDP. If underlying socket timing, buffering thresholds, or scheduler behavior shifts—even slightly—the retransmission and congestion control heuristics RUDP expects can get out of tune. The result looks like the field reports: smooth for a few seconds, then a burst of drops or a buffer oscillation that degrades lip‑sync and frame pacing. That is consistent with the “stutter every several seconds” pattern users described after KB5063878.

Who is most affected​

• Two‑PC streaming setups where one system captures (via Display Capture) and the other encodes or mixes via NDI.
• Corporate or education AV teams using NDI for classroom capture, overflow rooms, or remote guest workflows.
• Small production houses with tightly budgeted latency, where adding TCP’s overhead would break timing for switchers or graphics keying.

---

What’s safe to say—and what remains unclear​

• Confirmed by Microsoft: The NDI/OBS regression exists and correlates with the August security updates on Windows 11 24H2 and supported Windows 10 builds. Workaround: change NDI transport away from RUDP.
• Reported to Microsoft and acknowledged via media outreach: AutoCAD launch can spur an admin/UAC prompt post‑update, blocking standard users; Autodesk and Microsoft are collaborating on a fix. While the mechanism looks like an MSI self‑repair hitting machine scope, neither vendor has published a root‑cause statement yet.

For admins building incident notes, that difference matters. The NDI issue is in the official release health stream; the AutoCAD case is vendor‑acknowledged via press statements and field reports but not yet documented on the public KB page for KB5063878. Track both, but expect the NDI item to receive a documented resolution first. (support.microsoft.com, bleepingcomputer.com)

---

Collateral August regressions worth tracking​

Recovery and reset tools can fail on some client builds​

Microsoft’s August security updates introduced a separate, high‑impact bug that can break Reset this PC and “Fix problems using Windows Update” on Windows 10 and earlier Windows 11 branches (22H2/23H2). The glitch impacts both local reset and certain remote reset operations and has been acknowledged in release health. Windows 11 24H2 is not listed among the affected platforms.

WSUS deployment hiccup and CertEnroll noise​

Organizations pushing KB5063878 via WSUS reported installation failures with error 0x80240069; Microsoft has since addressed the distribution-side issue and noted a Known Issue Rollback Group Policy that some admins may have applied temporarily. Separately, the update can log benign Event ID 57 errors tied to the Pluton Cryptographic Provider component; Microsoft says the message is noise while a feature is in development.

Storage anomalies under heavy write load​

Multiple outlets and independent testers have raised alarms about SSDs becoming temporarily or permanently unavailable under heavy I/O on systems patched with the August updates, with early anecdotes calling out Phison‑based controllers among others. The pattern appears workload‑sensitive (e.g., >50 GB transfers on nearly full drives) and not universal. While Microsoft’s public notes have been cautious, testing recaps indicate enough signal for admins to defer stress‑testing storage in production until more data emerges. (tomshardware.com, windowscentral.com)

---

Practical guidance for Windows admins and lab managers​

Decision framework: who should roll back​

• Campus labs and training rooms where AutoCAD is part of the curriculum and students do not have local admin: consider rolling back KB5063878 on Windows 11 lab images and pausing updates for at least one ring while monitoring for an upstream fix. Document and communicate the exception clearly due to the security trade‑off.
• Streaming and AV teams using NDI with RUDP: prefer the protocol switch (RUDP → Single TCP or UDP) before removal of a security update. Only consider uninstalling the LCU if your workflows demand RUDP semantics and the trade‑off is unacceptable.

Safer rollback playbook (Windows 11 24H2)​

• Confirm the update: Settings > Windows Update > Update history, or run Get-HotFix in PowerShell and verify KB5063878.
• Uninstall the LCU using DISM: dism /online /remove-package /packagenameackage_for_RollupFix… (exact package name from DISM /online /get-packages).
• Pause quality updates for a defined maintenance window (e.g., 7 days) while tracking release health for a fix.
• Reboot and validate: confirm AutoCAD launches under a standard account and that NDI workflows are back to normal if you chose rollback.

Note: Combined SSU+LCU packages cannot have the SSU removed independently, and wusa /uninstall will not work for the combined package. Use DISM and target the LCU.

AutoCAD‑specific mitigation ideas (for managed fleets)​

There’s no vendor‑approved workaround beyond rollback, but experienced IT teams have had partial success with the following tactical moves—use with caution and test thoroughly:

• Create a temporary elevation policy (via Microsoft Intune Endpoint Privilege Management or equivalent) that auto‑elevates the specific child process implicated in the MSI repair when AutoCAD starts. This can let standard users pass the transient UAC gate without broad admin rights.
• Pre‑stage per‑machine repairs under maintenance windows: run a silent repair as an administrator so that common components are in the expected state before students log on, reducing the chance of per‑user repair triggers. This is not guaranteed but may blunt the worst‑case prompts in lab conditions.
• Avoid blanket “Run as administrator” shims on AutoCAD shortcuts; they can mask the symptom but open other permission and profile‑data hazards, especially with networked license services and per‑user caches. Historical Autodesk forum guidance has suggested elevation for unrelated issues, but it’s not a clean fix here.

NDI/OBS: deployment‑scale fixes​

• Standardize the transport: push a configuration change to NDI Access Manager across capture/receive hosts to set Receive Mode uniformly to Single TCP (safer) or UDP (lower latency on clean LANs).
• Audit your sources: prioritize replacing Display Capture with game/window capture where possible; some reports suggest Display Capture amplifies the regression’s impact.
• Test under synthetic load: rehearse with full‑bandwidth scenes and audio to confirm the jitter is gone after switching transport; watch for audio drift that signals queue oscillation.

---

For security and compliance teams: balancing risk​

Rolling back a monthly security update is never a decision to take lightly. The August updates close dozens of CVEs, and deferring them widens your exposure window. If you do choose to pause or uninstall KB5063878 on a subset of machines, offset the risk:

• Raise EDR sensitivity or temporarily enforce stricter Smart App Control and ASR (Attack Surface Reduction) rules on those machines.
• Narrow firewall rules for devices that remain on the pre‑August patch baseline, particularly for SMB, RDP, and inbound services.
• Shorten the pause: target a 7–14 day window, with pre‑approved change windows to reapply the patched build when Microsoft ships a fix.

---

Signals to watch in the next update cycle​

• Release health entries: Expect Microsoft to publish and then close a formal “known issue” item for the NDI/RUDP regression with a specific “Resolved” date and an OS build that carries the fix. The timeline could line up with late‑month preview or the next Patch Tuesday.
• Autodesk guidance: Look for Autodesk‑issued advisories or updated deployment notes that address the MSI/UAC behavior, potentially with guidance on repairing shared components or registry state to stop self‑repair triggers. Windows Latest indicates both vendors are collaborating.
• Storage findings: If your estate includes at‑risk NVMe controllers, hold off on stress testing large transfers until Microsoft or controller vendors publish clearer root‑cause and mitigation notes. (tomshardware.com, windowscentral.com)

---

Administrator checklist​

Immediate triage​

• Identify machines with KB5063878 (24H2) and KB5063709/KB5063877 (Windows 10).
• On production rigs using NDI, push the Receive Mode change and validate streams.
• In labs with AutoCAD, pilot a rollback on a small ring and confirm standard users can launch the suite.

Communications​

• Notify faculty or stakeholders whose classes rely on AutoCAD about the temporary rollback and timeline for re‑patching.
• Inform creators/streamers about the NDI transport change and brief them on latency trade‑offs with TCP vs UDP.

Monitoring​

• Watch for new “Known issues” updates on Microsoft’s KB5063878 page, including any WSUS deployment updates or noise events (e.g., CertEnroll Event ID 57) that can safely be ignored.

---

Critical analysis: what this episode reveals about Windows quality posture​

The good news​

• Rapid acknowledgement: Microsoft’s quick admission of the NDI regression—and clear, actionable guidance—helped teams restore service without ripping out the entire update. That’s the release health process working as intended.
• Vendor collaboration: Early signals that Autodesk and Microsoft are paired up on the AutoCAD issue suggest a coordinated fix path rather than finger‑pointing. For environments where CAD is mission‑critical, that matters.

The risks and rough edges​

• Specialized workflows are canaries: Problems that only appear with RUDP or with MSI repair actions can escape mainstream validation. Yet these “niche” workflows—NDI pipelines, lab‑managed CAD—carry outsized economic impact when broken.
• Recovery and WSUS turbulence: The August cycle also saw recovery feature failures and WSUS deployment friction. While Microsoft moved to resolve the WSUS glitch and flagged recovery issues, the pile‑up erodes admin confidence in Patch Tuesday predictability. (support.microsoft.com, bleepingcomputer.com)
• Communication gaps: The absence (so far) of a public KB “known issue” entry for the AutoCAD UAC prompt leaves IT pros triangulating via press reports. That increases reliance on social and media channels for change control decisions, which is less than ideal for enterprise governance.

Strategic takeaways for Windows shops​

• Keep a “specialty‑app ring”: Segment devices that run complex suites (CAD, DAWs, broadcast tools) into a slower patch ring that trails the general fleet by one cycle. Use that time to run targeted app‑validation playbooks.
• Institutionalize protocol fallbacks: Where possible, design AV and streaming workflows with configurable transports (e.g., the ability to switch NDI from RUDP to TCP quickly), and document the trade‑offs ahead of time.
• Maintain a rollback muscle memory: Ensure admins can remove LCUs with DISM and have update pause policies ready to deploy—rollback is a last resort, but it should be a choreographed one.

---

What Windows enthusiasts and power users should do right now​

• If you stream with OBS and rely on NDI: Change NDI Receive Mode away from RUDP and stress‑test your scenes, especially those using Display Capture. If your latency budget is tight, experiment with UDP first; if stability trumps latency, pick Single TCP.
• If you run AutoCAD 2022–2026 on Windows 11 24H2: Be aware that the August update can trigger an admin prompt and block the app under standard accounts. If you’re a home user running as admin, you may never notice; in multi‑user environments, coordinate with your IT admin for a temporary rollback or a managed elevation rule until a vendor fix lands.
• If you manage a Windows 10 or mixed fleet: Review recovery tooling plans in light of August’s reset issues, and make sure your WSUS is resynced if you hit 0x80240069 earlier in the cycle. (bleepingcomputer.com, support.microsoft.com)

---

The bottom line​

KB5063878 is a reminder that modern Windows update quality is a portfolio problem: ninety‑nine percent of users sail through, but the remaining one percent can be the most complex, high‑value scenarios—AutoCAD in managed labs, or NDI pipelines keeping shows on air. Microsoft has formally acknowledged and offered a practical workaround for the NDI regression, and it has privately confirmed to media that the AutoCAD UAC/installer prompt is real and under investigation with Autodesk. If these edge‑case workflows underpin your work, apply the mitigations now, hold your most sensitive rings, and watch for the official fix to land in the next servicing wave. (bleepingcomputer.com, windowslatest.com)

---

Source: windowslatest.com Microsoft admits Windows 11 KB5063878 AutoCAD admin request issue, OBS NDI audio video lag