Windows 11 Update KB5063878 Breaks AutoCAD and OBS NDI

You've probably realized that an update doesn’t always mean an improvement. And Windows 11 has reminded us of that once again with update KB5063878, which has brought more headaches than solutions.

If you work with AutoCAD or use OBS with NDI for streaming, you've likely noticed that something's not right. The worrying part? This isn't just a minor glitch—it’s a failure that’s blocking critical workflows and forcing many professionals to urgently look for workarounds to keep their projects going.

At TecnetOne, we want to help you understand what’s happening, why this bug is so significant, and what you can do to minimize the impact on your business.

What Happened with the KB5063878 Update?

Microsoft released this cumulative update as part of its regular maintenance cycle for Windows 11 24H2. But instead of enhancing security, it turned into a major issue for thousands of users.

Reports began surfacing in mid-August 2025:

1. AutoCAD (versions 2022–2026) started requesting admin permissions every time it launched.

1. In environments with standard user accounts—common in schools, labs, or businesses with strict security policies—the program simply wouldn’t run.

1. Trying to cancel the User Account Control (UAC) prompt would trigger an error code that halted execution entirely.

This disrupts user experience and complicates environments where not all users have admin rights.

And it doesn’t stop at AutoCAD. The update also affects OBS with NDI, causing severe audio and video lag, ruining live stream quality.

You might also be interested in: Windows 11 KB5063878: The Update That Could Damage Your SSDs

What Is NDI and Why Is This a Big Deal?

NDI (Network Device Interface) is a technology that allows high-quality video and audio to be transmitted over a local network. It’s widely used in audiovisual production, live streaming, and corporate broadcast environments.

The KB5063878 update causes:

1. Video/audio sync issues

1. Lag

1. In some cases, total signal dropout

This matters because:

1. Live streams can’t be redone—what cuts off is lost.

1. Media companies, universities, and streamers depending on OBS+NDI are unable to work in real time.

1. Even non-OBS apps that rely on NDI are affected.

What was meant to be a security update has turned into a direct productivity blocker for entire industries.

Why Is This Happening?

Microsoft hasn’t provided full technical details yet, but the issue seems related to:

1. How Windows handles permission elevation after the update

1. Changes to system libraries affecting AutoCAD and the audio/video stack used by NDI

For AutoCAD:

1. It now demands elevated permissions that weren’t needed before.

1. This breaks standard user environments—common in enterprise IT.

For OBS + NDI:

1. Windows is mishandling AV sync, likely affecting NDI system-level handling, not just OBS.

NDI in OBS is experiencing problems for streaming on Windows 1.

Who’s Most Affected?

1. Students and educational institutions: AutoCAD is essential in architecture and engineering; permission issues render it unusable.

1. Engineering and construction companies: Where AutoCAD is mission-critical.

1. Content creators and streamers: Who rely on OBS+NDI for pro-grade broadcasting.

1. Corporate AV environments: For conferences, hybrid events, or remote training.

How Can You Protect Yourself?

While Microsoft works on a fix, here are some actionable steps you can take:

Reconsider Installing KB5063878

If your environment isn't vulnerable to what the patch fixes, consider temporarily uninstalling it.

Explore Alternative Tools

Some users are using open-source tools like DistroAV to run NDI in OBS without relying on affected capture devices.

Strengthen Backup & Recovery

Ensure you regularly back up AutoCAD work to avoid data loss or delays.

Monitor Official Channels

Microsoft’s Release Health portal often posts workarounds and temporary patches.

Test Before Full Deployment

At TecnetOne, we always recommend testing updates in a sandbox environment before deploying organization-wide.

Lessons from This Failure

This incident shows how even security patches can introduce operational risks if poorly handled.

Key takeaways:

1. Patch management must be strategic—not every update should be rolled out immediately.

1. Resilience matters—fallback tools, extra hardware, and open-source options can keep work moving.

1. Communication is critical—if design or AV teams don’t know what to do, things spiral fast.

Learn more: Microsoft Changes the Backup System in Windows 11

TecnetOne’s Role in All This

At TecnetOne, we help ensure situations like this don’t shut your business down.

We support you in:

1. Assessing updates before implementation

1. Deploying test environments to catch issues early

1. Designing incident response plans for update-induced failures

1. Implementing backup/recovery strategies that minimize disruption

Conclusion

The Windows 11 KB5063878 update is a reminder that security and stability are two sides of the same coin. Updates are meant to protect—but if not properly tested, they can disrupt your daily operations.

Don’t leave your infrastructure to chance: evaluate, test, communicate, and protect. And if you need expert support to navigate these challenges, TecnetOne is here to help.