Microsoft has quietly closed the book on two long-running Windows 11 problems that kept a subset of PCs from upgrading to the 24H2 feature update — but the September servicing cycle introduced a fresh regression that breaks playback of DRM‑protected Blu‑ray, DVD and digital‑TV content for some users.
The past year of Windows 11 servicing has been dominated less by headline features and more by compatibility holds and targeted fixes. Microsoft’s feature update model uses a mix of staged rollouts and safeguard holds (targeted compatibility blocks) to keep problematic device configurations from receiving major upgrades until drivers or middleware are corrected. That system worked as intended in several high‑profile cases: it prevented many affected machines from accepting 24H2 while Microsoft and hardware vendors patched broken components.
Two of those compatibility blocks — one tied to integrated camera face/object detection that could freeze apps, and one rooted in an audio middleware incompatibility that broke Bluetooth audio devices — have now been marked resolved. Both were first documented much earlier (one in October 2024, the other in December 2024), and the hold removals landed in September 2025 after vendor and driver updates were staged to Windows Update.
Unfortunately, the September servicing updates introduced a new, separate problem: changes to the protected media pipeline caused applications that use the legacy Enhanced Video Renderer (EVR) together with HDCP and platform DRM to fail when playing protected content. That regression manifests as copyright protection errors, black screens, freezes, or frequent playback interruptions in Blu‑ray/DVD players and some digital‑TV apps. Streaming services that rely on modern app‑managed DRM paths remain unaffected.
The result is a mixed bag: users who were blocked from getting 24H2 due to camera or audio issues can now proceed, while a different group of media‑playback users have a new headache — and administrators must balance upgrade timelines against media playback reliability.
Reported symptoms include:
Failing closed means the system deliberately blocks output rather than degrade it; that behavior is by design to avoid leaking decrypted frames to ordinary memory or to capture/copy channels. But when an update alters the handshake or enforces a stricter validation step, older or non‑compliant playback paths can be unable to establish the secure chain and are therefore denied playback entirely.
Strengths:
The platform’s protected playback model is intentionally conservative: when secure playback can’t be established, it blocks playback to protect content owners’ rights. That’s a hard constraint; the platform will not silently relax protection to preserve compatibility. The only durable solution is fixing the handshake compatibility in the OS or providing updated drivers/apps that conform to the stricter expectations.
For now, affected users should:
Source: TechRadar Microsoft fixes two Windows 11 bugs that've been hanging around for a year - while another unfortunate glitch creeps in
Background / Overview
The past year of Windows 11 servicing has been dominated less by headline features and more by compatibility holds and targeted fixes. Microsoft’s feature update model uses a mix of staged rollouts and safeguard holds (targeted compatibility blocks) to keep problematic device configurations from receiving major upgrades until drivers or middleware are corrected. That system worked as intended in several high‑profile cases: it prevented many affected machines from accepting 24H2 while Microsoft and hardware vendors patched broken components.Two of those compatibility blocks — one tied to integrated camera face/object detection that could freeze apps, and one rooted in an audio middleware incompatibility that broke Bluetooth audio devices — have now been marked resolved. Both were first documented much earlier (one in October 2024, the other in December 2024), and the hold removals landed in September 2025 after vendor and driver updates were staged to Windows Update.
Unfortunately, the September servicing updates introduced a new, separate problem: changes to the protected media pipeline caused applications that use the legacy Enhanced Video Renderer (EVR) together with HDCP and platform DRM to fail when playing protected content. That regression manifests as copyright protection errors, black screens, freezes, or frequent playback interruptions in Blu‑ray/DVD players and some digital‑TV apps. Streaming services that rely on modern app‑managed DRM paths remain unaffected.
The result is a mixed bag: users who were blocked from getting 24H2 due to camera or audio issues can now proceed, while a different group of media‑playback users have a new headache — and administrators must balance upgrade timelines against media playback reliability.
What Microsoft fixed — the camera and Bluetooth audio blocks
Camera face‑detection freeze (safeguard hold)
- Symptom: On affected devices, apps that use the integrated camera for object or face detection — notably the Camera app and Windows Hello facial recognition sign‑in — could freeze or stop responding after upgrading to Windows 11 version 24H2.
- Root cause timeline: The issue was first acknowledged publicly in October 2024. Microsoft applied a targeted compatibility hold to prevent those specific device configurations from receiving the 24H2 feature update while fixes were developed.
- Safeguard details: The camera‑related block was tracked by a safeguard identifier; Microsoft removed that hold in mid‑September 2025 after the necessary fixes and driver updates were published.
- How users were remedied: Microsoft and hardware partners rolled out updated drivers and cumulative updates. Once those updates were installed and the device passed the appraiser checks, eligible systems began being offered the 24H2 update again (it can take up to 48 hours for the offer to appear after installing the remediation updates; a reboot may speed the process).
Bluetooth audio and Dirac middleware (cridspapo.dll)
- Symptom: After installing 24H2 on certain devices, integrated speakers, Bluetooth headsets, and Bluetooth speakers could lose functionality entirely. Applications ceased to detect or output to those audio devices.
- Root cause timeline: Microsoft identified an incompatibility involving the Dirac audio processing middleware — specifically a third‑party DLL named cridspapo.dll — and placed a compatibility hold on devices containing that component in mid‑December 2024.
- Resolution: Driver updates that replaced or updated the offending audio component were distributed via Windows Update. With those updates in place, Microsoft lifted the relevant safeguard hold in September 2025.
- Practical impact: Users who’d been held back from 24H2 by the Dirac problem can now upgrade once their systems receive the updated driver and the 24H2 offer becomes available.
The new problem: protected playback fails after August/September updates
What’s breaking and how it shows up
In the August 29, 2025 non‑security preview update and the September 9, 2025 cumulative rollup, Microsoft introduced changes that tightened the protected media and HDCP enforcement pathways. For most modern streaming clients and app‑managed DRM flows the change was invisible. But legacy playback pipelines that still rely on Enhanced Video Renderer (EVR) in combination with HDCP enforcement or platform DRM for audio/video began failing.Reported symptoms include:
- Black screens when attempting to play protected Blu‑ray or DVD titles.
- Copyright protection error dialogs that prevent playback.
- Frequent interruptions, stuttering, or outright freezes during playback.
- Failures in some digital TV or tuner applications that depend on platform HDCP/DRM enforcement.
Why EVR + HDCP/DRM is fragile
EVR is a legacy rendering component. It was widely used by DirectShow‑based players and older Media Foundation integration patterns because it provided a trusted composition surface capable of participating in the platform’s protected media path. When the operating system or DRM stack tightens expectations in the protected rendering handshake — for example, imposing stricter HDCP/driver validation — any mismatch in that chain causes the platform to “fail closed.”Failing closed means the system deliberately blocks output rather than degrade it; that behavior is by design to avoid leaking decrypted frames to ordinary memory or to capture/copy channels. But when an update alters the handshake or enforces a stricter validation step, older or non‑compliant playback paths can be unable to establish the secure chain and are therefore denied playback entirely.
When the regression appeared and initial response
- Triggering updates: The regression was associated with the August 29, 2025 preview update (delivered as KB5064081) and the September 9, 2025 cumulative update (KB5065426). Users saw playback regressions immediately after installing those packages.
- Microsoft’s response: The company listed the behavior as a known issue on its Windows Release Health dashboard and acknowledged engineering teams were working on a correction to be delivered in a future update. A targeted remediation package was staged to Release Preview channels as part of validation before broader rollout.
- Short‑term mitigation: Microsoft advised affected customers to use alternative playback devices/applications that do not use EVR, or to rely on streaming services while the fix is prepared. In some cases rolling back the offending update is feasible for power users or administrators.
Deep dive: how protected playback, HDCP and DRM interact with OS updates
The protected media chain, in plain terms
Protected playback for premium content depends on several cooperating elements:- The application player requests playback of encrypted content.
- The OS DRM stack (PlayReady, AACS, or platform DRM) validates licensing and decrypts media frames inside a protected boundary.
- The video renderer (EVR or newer Simple Video Renderer) presents frames to a protected rendering surface that guarantees the decrypted frames are never accessible to untrusted processes.
- The GPU driver and display pipeline ensure HDCP (High‑bandwidth Digital Content Protection) is negotiated to the attached display or capture device; if HDCP can’t be established, content is blocked.
- If any link in this chain produces an unexpected response — driver incompatibility, missing API behavior, or tightened OS checks — the platform typically fails closed and refuses to play content to avoid leaks.
Why a security/compatibility hardening can break playback
Security hardening often tightens assumptions made by older drivers and apps. When Microsoft changed enforcement details in the EVR or the platform DRM handshake, some legacy players or drivers no longer matched the expected negotiation sequence. That mismatch triggers the protection logic and prevents playback. Unlike non‑protected playback, you can’t simply fall back to a lower quality or unprotected path — the content license prevents that.The role of GPU drivers and OEM firmware
Because the protected media chain touches GPU drivers, display firmware and HDCP compliance, outdated or vendor‑modified drivers can also be the weak link. Even if the player and OS are updated, an OEM GPU driver that does not support the updated protected rendering handshake can cause playback to fail.Practical steps for users and IT admins
Quick checklist for home users
- Update Windows and drivers: Install the latest cumulative updates and OEM graphics/audio drivers from Windows Update or the manufacturer. Many fixes depend on matching OS and driver versions.
- If you rely on Blu‑ray/DVD playback or digital‑TV tuners, avoid immediately installing the latest optional preview updates until Microsoft rolls the remediation into the general Channel — or verify playback after installing updates.
- If you already have the playback issue:
- Try a different playback application that uses modern Media Foundation APIs rather than legacy EVR/DirectShow pipelines.
- Temporarily use streaming versions of content if available.
- If comfortable and as a last resort, uninstall the most recent update that triggered the issue via Settings → Windows Update → Update history → Uninstall updates. Be aware of security implications.
- Check for driver updates on your PC maker’s support site — especially GPU and audio drivers.
Recommendations for IT administrators and power users
- Pause feature updates on production machines until remediation arrives for known issues impacting your environment.
- Use a pilot group for early adoption of 25H2/24H2 — test physical‑media and tuner workflows specifically.
- Monitor Microsoft’s Release Health dashboard and OEM advisories for confirmations and driver packages.
- If affected systems are mission‑critical (for example, broadcast ingest or media servers), keep a tested rollback/restore plan in case the patched chain causes service disruption.
- Where possible, prefer modern playback paths and SDKs that avoid EVR and older DirectShow pipelines.
Analysis: what this patch cycle says about Microsoft’s release model
Microsoft’s approach — safeguard holds plus staged rollouts and Release Preview validations — is designed to keep the largest number of users safe while allowing problem cases to be isolated and remediated. The model demonstrated both strengths and weaknesses in this cycle.Strengths:
- Targeted safeguards prevented widespread breakage when the camera and Dirac audio regressions were first discovered.
- Collaboration with OEMs and driver vendors eventually produced fixes that let those held devices proceed to 24H2.
- The Release Preview channel provided a place to stage and validate a remediation for the protected‑playback regression before broad distribution.
- The length of some holds — nearly a year in the camera case — is an uncomfortable wait for affected users who want to adopt the latest feature update in a timely manner.
- Tightening of protected media enforcement without visible fallbacks breaks longstanding third‑party players and live‑TV workflows, demonstrating that security‑first changes can impose real operational costs.
- The appearance of a new regression immediately after lifting long‑standing holds highlights the fractured complexity of the Windows ecosystem: multiple vendors, legacy components, and decades of backward compatibility create a brittle surface for change.
How serious is the DRM playback regression?
For the majority of everyday users who rely primarily on streaming services, the regression will appear minor or invisible. However, for specific niches — home theater PC owners, Blu‑ray/DVD collectors, broadcast engineers, and users of certain digital TV/tuner apps — the regression is material and immediately disruptive.The platform’s protected playback model is intentionally conservative: when secure playback can’t be established, it blocks playback to protect content owners’ rights. That’s a hard constraint; the platform will not silently relax protection to preserve compatibility. The only durable solution is fixing the handshake compatibility in the OS or providing updated drivers/apps that conform to the stricter expectations.
Short‑term outlook and expected timeline
Microsoft has publicly acknowledged the playback regression as a known issue and stated engineering teams are working on a fix. The company staged a remediation package in Release Preview for validation before wider distribution. Historically, such targeted fixes can appear in a cumulative update within a few weeks after validation — but the exact timing depends on test results and any additional vendor coordination (GPU and display driver vendors are often involved).For now, affected users should:
- Avoid installing optional preview updates if they rely on legacy protected playback.
- Monitor Windows Update and OEM driver pages for remediation rollouts.
- Use alternative playback workflows if possible until the fix is broadly released.
Final takeaways
- Two long‑standing compatibility holds that previously prevented certain PCs from upgrading to Windows 11 version 24H2 — one impacting camera object/face detection and one rooted in Dirac audio middleware — have been resolved after vendor fixes and driver updates.
- Those fixes allow a broader set of devices to be offered the 24H2 upgrade again. However, because Windows 11 version 25H2 is now rolling out as an enablement package, the practical window for installing 24H2 before 25H2 arrives is narrow.
- A separate regression introduced by late‑August/early‑September 2025 servicing tightened protected playback enforcement and broke DRM/HDCP playback for applications that rely on the legacy Enhanced Video Renderer. The problem causes black screens, copyright protection errors, and frequent playback interruptions in some Blu‑ray, DVD and digital‑TV apps.
- Microsoft has acknowledged the DRM playback issue and staged a fix to the Release Preview channel. A broader rollout is expected after validation, but affected users should plan mitigations in the meantime: update drivers, use alternate players, or temporarily avoid installing the optional preview releases that introduced the regression.
- The episode illustrates the tradeoffs in modern OS servicing: safeguard holds and staged rollouts limit catastrophic breakage, but long remediation timelines and the complexity of the protected media chain mean real users can still face months‑long disruption.
Source: TechRadar Microsoft fixes two Windows 11 bugs that've been hanging around for a year - while another unfortunate glitch creeps in
