Schools and labs running AutoCAD on Windows 11 24H2 are in crisis mode after the August 2025 Patch Tuesday update, KB5063878, began demanding administrator privileges just to launch the software. The unexpected User Account Control (UAC) prompt completely locks out students and other non-admin account holders, rendering Autodesk’s flagship design tools unusable. Microsoft has acknowledged the bug and confirmed it is working with Autodesk on a fix, but the only immediate relief for affected organizations is to roll back the security update—a risky short-term trade-off.

Simultaneously, Microsoft disclosed that KB5063878 introduces severe stuttering and lag in NDI (Network Device Interface) audio/video streams, clobbering workflows for streamers and broadcasters who rely on OBS Studio and similar tools. The streaming regression specifically targets Reliable UDP (RUDP) transport, forcing users to switch to legacy UDP or Single TCP as a workaround. Together, these two regressions—on top of separate August glitches that broke Windows Recovery tools and triggered reports of SSDs disappearing under heavy load—mark a turbulent update cycle for Windows 11 24H2.

The AutoCAD Admin Prompt Bug

What’s Actually Happening

After applying KB5063878 (build 26100.4946), launching AutoCAD products from version 2022 through 2026—including Civil 3D and Inventor—kicks off an MSI self-repair action that immediately triggers a UAC elevation request. Standard user accounts hit a hard wall: canceling the prompt yields MSI error 1730 and the application never opens. Several educational institutions told Windows Latest that clean student profiles on up-to-date lab machines suddenly became useless for CAD coursework, with the prompt appearing even on some administrator accounts sporadically.

Scope and Acknowledgment

Microsoft confirmed to Windows Latest that it is aware of the behavior and is collaborating with Autodesk. While no public KB “known issue” entry exists yet for this specific regression, the advisory has been shared via press outreach. The bug appears tied to August updates beyond just KB5063878: Windows 11 KB5063875 and KB5064010, plus their Windows 10 counterparts KB5063877 and KB5063709, can trigger the same admin demand. For IT managers, this means the blast radius extends across multiple OS versions and update packages.

Why This Hits Education and Enterprise Hard

Managed labs and corporate deployments routinely enforce standard user baselines, making the forced UAC gate a workflow blocker. The MSI repair trap is especially insidious because resetting user profiles doesn’t clear the condition—every login for every non-admin user will face the prompt. Temporary elevation of all student accounts is a compliance nightmare, leaving rollback as the most reliable path until a permanent fix ships.

Context: Earlier AutoCAD Hiccups on 24H2

This isn’t the first friction point between AutoCAD and Windows 11 24H2. Earlier in 2025, Microsoft briefly placed a safeguard hold preventing some devices with AutoCAD 2022 from upgrading to 24H2 due to launch failures. That issue was later resolved, but the recurrence highlights how complex CAD suites remain sensitive to OS plumbing changes, especially around installer and identity services.

NDI Streaming Stutters, Lag, and Drops

The Symptom Set

Microsoft officially acknowledged that the August security updates can degrade NDI transport, causing “severe stuttering, lag, and choppy audio/video.” The problem is most pronounced when the source PC uses Display Capture in apps like OBS Studio or NDI Tools, and it persists even under low-bandwidth conditions, pointing to a timing or buffering issue rather than a simple throughput limitation. Independent reports and vendor notes align: the regression isolates to RUDP mode.

Fingerprint: RUDP Specifically

When NDI Receive Mode is switched to legacy UDP or Single TCP, streams stabilize immediately. Left on RUDP, users report regular hiccups every few seconds—video stutters, audio drifts, and lipsync breaks. The pattern suggests that KB5063878 altered socket timing, buffering thresholds, or network stack scheduling just enough to upset RUDP’s retransmission and congestion-control heuristics. For two-PC streaming rigs where one machine captures and the other encodes via NDI, the result is a broadcast-unusable feed.

Workaround and Trade-offs

Microsoft and the NDI team recommend forcing NDI away from RUDP. The steps are straightforward:

  1. Install NDI Tools if not already present.
  2. Open NDI Access Manager on the receiving host.
  3. Switch to the Advanced tab.
  4. Set Receive Mode to Single TCP or UDP, then click OK.
  5. Restart all NDI-using applications (OBS, vMix, Studio Monitor).
  • Single TCP is the safest fallback across mixed network gear but adds latency and can suffer head-of-line blocking under packet loss.
  • UDP preserves low latency on clean LANs but lacks RUDP’s recovery logic, making it fragile on lossy segments.

For most streamers, Single TCP is the pragmatic choice until Microsoft issues a code fix. If your workflow absolutely demands RUDP semantics, the only alternative is to uninstall the cumulative update—a heavier lift discussed below.

Who Is Most Affected

  • Two-PC streaming setups using OBS with DistroAV (open-source NDI plugin).
  • Corporate or education AV teams running NDI for classroom capture and overflow rooms.
  • Small production houses that need lip-sync accuracy for switchers or graphics keying.

Collateral Damage: Other August Regressions

Broken Recovery and Reset Tools

Microsoft confirmed that the August security updates for Windows 10 and earlier Windows 11 branches (22H2/23H2) break “Reset this PC” and “Fix problems using Windows Update.” While Windows 11 24H2 is not listed as affected, admins managing mixed fleets should be aware. The recovery failure can block local and remote reset operations, complicating troubleshooting for already-compromised devices.

WSUS Deployment Hiccup

Organizations pushing KB5063878 via Windows Server Update Services encountered installation failures with error 0x80240069. Microsoft resolved the distribution-side issue and noted a Known Issue Rollback Group Policy that some may have applied temporarily. If you hit this, re-synchronizing WSUS and checking that the policy is no longer needed should clear the path.

SSD and Storage Anomalies Under Heavy Write Load

Multiple outlets reported SSDs becoming temporarily or permanently unavailable under heavy I/O after applying August updates. Early anecdotes point to Phison-based controllers, with failures occurring during transfers exceeding 50 GB on nearly full drives. Microsoft’s public statements have been cautious, but enough signal exists for admins to defer stress-testing storage in production until root cause is clearer. If you manage devices with at-risk NVMe controllers, hold off on large file migrations until vendor guidance solidifies.

Practical Guidance for IT Admins

Decision Framework: When to Roll Back

  • AutoCAD labs where students lack local admin: roll back KB5063878 on Windows 11 24H2 lab images and pause updates for at least seven days. This is the most reliable way to restore functionality, but document the exception and understand the security gap.
  • NDI-dependent environments: first apply the protocol workaround (RUDP → TCP/UDP). Only consider rollback if your workflows critically depend on RUDP and the trade-off is unacceptable.

Safer Rollback Playbook (Windows 11 24H2)

  1. Confirm the update: run Get-HotFix -Id KB5063878 or check Update History.
  2. Uninstall the LCU with DISM: dism /online /remove-package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.4946.1.x (exact name from dism /online /get-packages).
  3. Pause quality updates for a defined maintenance window (e.g., 7 days) while tracking release health for a fix.
  4. Reboot and validate: ensure AutoCAD launches under a standard account and that NDI streams are clean if you chose that path.

Note: Combined SSU+LCU packages prevent independent SSU removal, and wusa /uninstall won’t work. Use DISM and target the LCU.

AutoCAD-Specific Mitigation Ideas (for Managed Fleets)

No vendor-approved workaround exists beyond rollback, but some IT teams have had partial success with:
- Temporary elevation policy: Use Microsoft Intune Endpoint Privilege Management or an equivalent to auto-elevate the specific MSI child process when AutoCAD starts, allowing standard users through the transient UAC gate without granting broad admin rights.
- Pre-stage per-machine repairs: Under a maintenance window, run a silent repair as administrator to place common components in the expected state before student logins, reducing per-user repair triggers.
- Avoid blanket “Run as administrator” shims: They can mask the symptom but open profile-data hazards and may conflict with networked license services.

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 capture sources: Replace Display Capture with game/window capture where possible; some reports suggest Display Capture amplifies the regression’s impact.
  • Stress-test under synthetic load: Rehearse with full-bandwidth scenes and audio to confirm jitter is gone after switching transport; watch for audio drift.

Balancing Security and Operational Continuity

Rolling back a monthly security update always widens your exposure window. The August updates close dozens of CVEs, so a pause isn’t free. If you must uninstall KB5063878 on a subset of machines, offset the risk:
- Raise EDR sensitivity or temporarily enforce stricter Smart App Control and ASR rules.
- Narrow firewall rules for devices on the pre-August patch baseline, especially for SMB, RDP, and inbound services.
- Shorten the pause to 7–14 days maximum, with pre-approved change windows to reapply the patched build once Microsoft ships a fix.

What to Watch For

  • Release health entries: Expect Microsoft to publish and later close a formal known issue for the NDI/RUDP regression, tied to a specific resolved build. A fix could arrive in a late-month preview or the next Patch Tuesday.
  • Autodesk guidance: Look for an Autodesk advisory or updated deployment notes addressing the MSI/UAC behavior, possibly with registry or component repair steps to stop the self-repair trigger.
  • Storage findings: If your estate includes at-risk NVMe controllers, monitor Microsoft’s known issues page and controller vendor bulletins before stressing large file transfers.

Administrator Checklist

Immediate Triage

  • Identify all machines with KB5063878 (24H2) and relevant Windows 10 patches.
  • On production streaming rigs, push the NDI Receive Mode change and validate streams.
  • In AutoCAD labs, 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.

Monitoring

  • Watch for new “Known issues” updates on Microsoft’s KB5063878 page.
  • Track Autodesk’s official channels for a fix statement.
  • Ignore benign Event ID 57 errors related to Pluton Cryptographic Provider—Microsoft has confirmed they are noise.

Critical Analysis: Windows Quality Posture Under Strain

The Good

  • Rapid acknowledgment: Microsoft’s quick admission of the NDI regression and clear, actionable workaround helped AV teams restore service without full update removal. That’s the release health process functioning as intended.
  • Vendor collaboration: Early signals that Autodesk and Microsoft are jointly working on the AutoCAD issue suggest a coordinated fix path, which is critical for mission-critical design environments.

The Risks and Rough Edges

  • Specialized workflows as canaries: Problems that only surface with RUDP or MSI repair actions can escape mainstream validation, yet these “niche” workflows—NDI pipelines, managed CAD labs—carry outsized economic impact when broken.
  • Recovery and WSUS turbulence: The August cycle also saw recovery feature failures and WSUS deployment friction, piling up to erode admin confidence in Patch Tuesday predictability.
  • Communication gaps: The absence of a public KB “known issue” for the AutoCAD UAC prompt leaves IT pros to triangulate via press reports, increasing reliance on social and media channels for change control decisions—hardly ideal for enterprise governance.

Strategic Takeaways for Windows Shops

  • Maintain a specialty-app ring: Segment devices running complex suites (CAD, DAWs, broadcast tools) into a slower patch ring, trailing the general fleet by one cycle. Use that time for targeted app-validation playbooks.
  • Institutionalize protocol fallbacks: Design AV and streaming workflows with configurable transports, and document trade-offs ahead of time so that switching from RUDP to TCP is a quick, rehearsed move.
  • Keep rollback muscle memory fresh: 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 Now

  • If you stream with OBS and rely on NDI: Change NDI Receive Mode away from RUDP immediately. Stress-test your scenes, especially those using Display Capture. If latency is tight, experiment with UDP first; if stability trumps latency, use 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 for standard users. Home users running as administrator may never notice; multi-user environments should coordinate with IT for a temporary rollback or 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 ensure WSUS is resynced if you hit 0x80240069 earlier in the cycle.

KB5063878 is a sobering reminder that modern Windows update quality is a portfolio problem: 99% of users sail through, but the remaining 1% can be the most complex, high-value scenarios. Microsoft has owned the NDI regression with a practical workaround and is privately validating the AutoCAD UAC bug with Autodesk. Until official fixes ship, applying the mitigations outlined here—rollback where necessary, transport switch for streamers—will keep these edge-case workflows alive without exposing the entire fleet to unnecessary risk.