Microsoft has confirmed that the August 29 and September 9, 2025 cumulative updates for Windows 11—KB5064081 and KB5065426—contain a regression that breaks playback of DRM-protected video content in applications that rely on the Enhanced Video Renderer (EVR) with HDCP enforcement. The company is already delivering a targeted fix through the Release Preview channel, but until that patch reaches all users, owners of Blu-ray discs, DVDs, and digital TV tuners are left with broken media playback.

This isn't a universal media failure. Streaming apps like Netflix, Amazon Prime Video, and YouTube continue to work without a hiccup. The problem is buried deep in a legacy playback path that many specialized applications still depend on—and if you bought a Blu-ray movie and popped it into your PC only to see a copyright error or a black screen, you're not imagining things.

What Got Broken, and Why

The two servicing updates—KB5064081 from late August and KB5065426 from September's Patch Tuesday—included security hardening that inadvertently tripped up the DRM handshake between the operating system and certain media players. Specifically, the glitch affects software that relies on the Enhanced Video Renderer (EVR) while also enforcing High-bandwidth Digital Content Protection (HDCP) or operating system-level DRM for audio.

EVR is a component of the Windows media pipeline, sitting inside DirectShow and Media Foundation. Its job is to composite and present protected video frames using trusted Direct3D surfaces. When HDCP is required—as it is for Blu-ray playback and for copy-protected broadcast TV—EVR must guarantee that frames aren't exposed unprotected to the GPU or capture paths. The August and September updates altered a low-level interaction in the OS DRM stack, and that change was enough to make the EVR-HDCP handshake fail. Instead of video, the player gets a content-protection error.

Microsoft's own documentation on its support and Release Health pages, along with statements by a moderator on the official Q&A forums, make clear that this is a known issue caused by a security fix. Engineering is working on a corrected update, and a small cumulative package—KB5065789—has been released to the Release Preview channel to restore protected playback without rolling back the broader security improvements.

Who Feels the Pain: Home Theater Buffs, Power Users, and Enterprises

The impact is narrow but acute. Streaming services are untouched because they use modern protected pipelines with their own decryption and secure path handling. The affected apps are almost all legacy players, TV tuner software, and specialized tools that still rely on EVR.

For home users, the symptoms are unmistakable:
- You insert a Blu-ray or DVD and immediately get a "copyright protection" or "protected content" error dialog.
- Playback starts but freezes, stutters, or drops to a black screen while audio continues—or stops entirely if DRM for audio is enforced.
- Some users report the problem only in specific applications, like third-party Blu-ray players or broadcast tuner apps, while others find their whole physical media library is unplayable.

If you maintain a home theater PC (HTPC) that you use to watch your disc collection or record over-the-air TV, these updates have likely ruined your evening. Ditto for cord-cutters who rely on tuner capture software and need protected pipelines for premium channels.

For IT administrators and enterprises, the stakes are higher. Digital signage systems, lecture-capture rigs, and kiosks that present protected streams may suddenly fail. Organizations that distribute training or compliance content on physical media could face disruptions until every machine is patched or rolled back. One system integrator described the situation as "death by a thousand cuts"—each workstation that handles protected video now needs individual validation before it can be trusted again.

Power users sit somewhere in between. If you've already installed the August or September update on a machine that doubles as your media center, you're stuck either hunting for a workaround or joining the Release Preview ring to test the fix. If you haven't installed it yet, you're faced with a choice: skip critical security patches or lose access to your legally purchased content.

How We Got Here: A Timeline of Breakage and Response

The troubles began with the optional August 29, 2025 servicing update (KB5064081). Early reports trickled in from enthusiasts who found that their Blu-ray software suddenly stopped working. Because the update wasn't forced, many users simply avoided it. But when the September 9 security rollup (KB5065426) landed—mandatory for anyone who didn't pause updates—the floodgates opened. Machines that had never seen the problem suddenly refused to play protected discs.

Microsoft acknowledged the regression on its support channels within days. A moderator on the official Q&A forum confirmed that the behavior is a known issue, tied directly to a security fix in the servicing stack, and that engineering was already working on a corrected update. The company's triage approach was to preserve the security hardening while issuing a surgical correction for the media-path regression—a decision that shows just how delicate the DRM chain can be.

On the technical side, the root cause almost certainly lies in the initialization order of trusted Direct3D surfaces, driver cooperation, or protected audio/digital rights initiation. A tiny shift in permissioning or API behavior can be enough to make the handshake fail. Because EVR and HDCP require precise coordination between the OS, the graphics driver, and the playback application, any servicing update that touches the kernel or user-mode DRM components risks a regression.

The Release Preview fix, KB5065789, is a targeted package that repairs the specific interaction broken by KB5064081. It doesn't roll back the security improvements, meaning enterprises and home users can eventually get both protection and playback.

What to Do Right Now: A Step-by-Step Guide

Your immediate action depends on whether you've already installed the problematic updates and how critical protected playback is to your workflow.

If you haven't installed KB5064081 or KB5065426:
- Pause updates on machines used for Blu-ray/DVD or digital TV. Windows 10 and 11 let you pause updates for up to 35 days. This buys time for Microsoft's validated fix to reach the general public.
- Check your playback software's dependency on EVR. Most classic players—PowerDVD, WinDVD, and many open-source media centers—rely on it. If you're unsure, test protected playback on a non-critical machine that already has the update, or search your player's documentation for terms like "EVR" or "DirectShow."

If you already installed the updates and are seeing errors:
- Option 1: Uninstall the update. Go to Settings > Windows Update > Update History > Uninstall Updates. Remove KB5064081 or KB5065426. This restores playback immediately but also removes the security fixes. It's a trade-off—fine for a home theater PC that never touches the internet outside of your home network, risky for a daily driver.
- Option 2: Join the Release Preview channel and install the fix. Navigate to Settings > Windows Update > Windows Insider Program, enroll in the Release Preview ring, and check for updates. KB5065789 should appear. Once installed, test your player. After confirmation, you can opt out of future Insider builds if you prefer. This gives you the fix without waiting, but note that Release Preview builds are still technically pre-release.
- Option 3: Use a fallback device. If you have a secondary PC, a dedicated Blu-ray player, or a game console that hasn't received the update, switch to that until the fix is widely available.

For IT administrators managing fleets:
1. Inventory all systems that might play protected physical media or use tuner/capture apps. This includes executive conference room PCs, training workstations, and digital signage players.
2. Create a pilot group of one to five representative devices. Apply the Release Preview fix to those machines first.
3. Validate that your specific applications work. Don't assume—test with the actual Blu-ray discs, TV tuners, or encrypted videos your users depend on. Capture timestamps and Event Viewer logs for baseline comparisons.
4. If the pilot succeeds, decide on a rollout strategy. You can either push the Release Preview fix to all affected machines (not ideal for production stability) or wait for the fix to land in a regular cumulative update. If you wait, communicate the playback outage to users and provide workarounds.
5. Prepare rollback and fallback plans. Have a clean system image or a known-good backup for critical machines. If the fix doesn't work for your software, you'll need to revert.

Throughout this process, collect logs and file feedback with Microsoft via the Feedback Hub or the Q&A threads. The more data they get, the faster a durable resolution will arrive.

The Bigger Picture: DRM, Updates, and Trust

This incident is a stark reminder that DRM is a double-edged sword. It protects content creators' rights, but when it breaks, it locks legitimate customers out of their own media. Windows servicing updates have occasionally tripped over DRM before—remember the Windows 10 1809 fiasco that broke certain protected audio tracks?—but each time, the affected user base is small enough that the problem doesn't get the red-carpet treatment. For the people who hit the bug, though, it's a complete showstopper.

Microsoft's handling of the regression has been relatively swift. The company acknowledged the problem, documented it, and delivered a targeted fix to the Release Preview channel within weeks. That's better than some past incidents where it took months for a fix to materialize. The decision to surgically repair rather than roll back security hardening is also a delicate balance that many enterprises will appreciate.

Still, the episode highlights a testing gap. Specialized media workflows—Blu-ray playback, TV tuner capture—are not as well-covered in Microsoft's servicing validation as mainstream scenarios. As long as Windows supports these legacy paths, it needs to test them more thoroughly before pushing updates that touch the DRM chain.

What to Watch For: The Road Ahead

Microsoft has said the corrected behavior will be included in upcoming cumulative releases once it's fully validated. That likely means the fix will roll into the October 2025 Patch Tuesday update, or possibly even a late September out-of-band release if pressure mounts. Keep an eye on the Windows Release Health dashboard and the official Windows Insider blog for announcements.

Until then, the safest bet for content-critical systems is to stay on the paused update track or pilot the Release Preview fix. The workaround window is uncomfortable, but manageable. Above all, verify that your specific playback application works before you trust the fix across your entire fleet or home setup. As one exasperated Redditor put it, "I just want to watch my copy of Dune without having to disable security updates." Soon, you should be able to.