- Microsoft confirms DRM/HDCP flaws with EVR after KB5064081 and later; streaming is not affected.
- KB5065426 increases reporting: SMB network errors, problematic installation and uninstallation codes.
- NDI, UAC/MSI, and other recent bugs are fixed in KB5065426; DRM/HDCP remains open.
- Mitigations: Postpone update, DISM/SFC, avoid WUSA on network, temporary SMB settings.
The latest cumulative updates of Windows 11 have raised dust: after installing KB5064081 (August preview) and later, KB5065426 (September security), numerous users have encountered issues with playing DRM/HDCP-protected content, problems with network shares, and in some cases, errors when installing or uninstalling patches. In this article, we compile everything confirmed by Microsoft and what users are experiencing, with Symptoms, scope, official status, and mitigations.
If you rely on physical media (Blu-ray/DVD) or apps of digital TV, or if you manage environments with SMB resources, you might be interested in continuing reading. Microsoft has acknowledged some of these flaws in its status panel, and while fixes are underway for certain issues, the DRM/HDCP bug remains open; for now, the only solid official recommendation is postpone installation if it affects you.
What happened to KB5064081 and KB5065426?
Microsoft has confirmed that after the update KB5064081 (August 29, 2025, non-security preview) and later updates, some digital TV and Blu-ray/DVD apps cannot play protected content. The issue affects apps that still use Enhanced Video Renderer (EVR) along with HDCP or DRM audio protection. Symptoms include copyright errors, frequent stops, freezes and black screens; on the other hand, streaming services (Netflix, Disney+, etc.) are not affected.
EVR is a legacy technology from Windows who works with Media Foundation and DirectShow to render video securely. Its mission, when HDCP or DRM is present, is to compose and present protected frames only on trusted Direct3D surfaces, preventing unauthorized copying. Microsoft indicates in Release Health that the flaw is confirmed and under investigation to Windows 11 24H2, with no official workaround other than delaying the update while waiting for a patch.
The September Update KB5065426 has intensified reports in recent hours, according to multiple media outlets and users. In particular, those who installed the patch have observed that the playback of protected videos It simply stops working on certain Blu-ray or digital TV apps, while everything remains normal on streaming platforms. This nuance is key: the impact is felt by use cases with physical means and applications that still rely on EVR.
As if that were not enough, separate but contemporaneous incidents have also appeared: error codes during the installation of KB5065426, problems with SMB shared resources and difficulties in uninstall The patch. Microsoft has acknowledged several of these issues on its official dashboard and in technical releases with specific IDs, indicating what has been fixed and what remains open.
Symptoms of DRM/HDCP failure in Windows 11
The reports agree on the essentials: after installing KB5064081 or updating later (including KB5065426), applications from Digital TV and Blu-ray/DVD that use EVR with HDCP or audio DRM experience errors when playing protected content. The user encounters messages of rights protection, constant cuts, hangs or even a black screen. This is not a problem of hardware of the PC; Microsoft itself has pointed this out as a side effect of the update.
It is striking that the platforms of streaming are not affected. This suggests that the flaw is limited to the legacy EVR route in combination with the security enforcement (HDCP/DRM) applied by these applications, which are typically much closer to the licensing ecosystem of Blu-ray and digital TV than modern OTT services.
In its Windows Release Health dashboard (Windows 11 24H2), Microsoft classifies the issue as "Confirmed" and maintains the “Open” status as of the last update. The official message: they are working on resolutions for future updates and will provide more information when available. There is no alternative solution official beyond postponing installation if you depend on these apps.
SMB shares and errors after KB5065426
Users and administrators have reported that after installing KB5065426 (and/or KB5064081), folder sharing on the local network stops working. In one detailed case, uninstall KB5064081 The problem initially disappeared; then, upon installing KB5065426, the error reappeared. Furthermore, upon removing KB5065426 and rebooting, it was observed that the KB5064081 reappeared as installed again, forcing both to be uninstalled to return to normal.
The experience is not limited to sharing: outages have been reported connectivity After the patch was applied, the "System error 86" message appears when attempting to access SMB resources. For some, uninstalling the patch would be the logical course of action, but there are cases where removing KB5065426 leak with strange errors, making it difficult to return to a stable state.
In corporate environments, this type of regression is especially annoying because it breaks workflows and access policies. While Microsoft investigates, several technical communities have shared temporary mitigations and system repair procedures to try stabilize the teams.
Common errors when installing KB5065426
The installation of the September update has also been plagued by bugs involving very specific codes. Among the most reported are 0x800F0991 (download or check components), 0x800F0922 (access or permissions), 0x80071A2D (DFS conflict or service unavailable), 0x800F081F (required files are missing), 0 x 80070302 (services of Windows Update problematic), 0 x 80070306 (corruption in system or .NET files) and 0x8000FFFF (generic error “unknown catastrophe”).
The striking thing is that these errors appear both when updating from Windows Update such as when attempting manual installation from the Microsoft Update Catalog, which suggests underlying service, integrity, or installation path issues on some computers.
Official status on Windows Release Health and other recent issues
Beyond the DRM/HDCP bug (open and confirmed for Windows 11 24H2 after KB5064081), the Microsoft dashboard documents other recent issues. Several have already been resolved by KB5065426 and later, while others have been mitigated or are gradually being resolved. It's useful to keep them on your radar because they explain anomalous behaviors you might be seeing in parallel.
For example, in August a security enhancement was introduced that tightened the UAC requests during MSI repairs (linked to CVE‑2025‑50173), which caused unexpected messages for standard users in certain scenarios (silent repairs, first-time Autodesk runs, per-user installs, etc.). Microsoft indicates that, starting with KB5065426, UAC prompts in MSI repairs are only enforced if the package contains a custom action with elevated privileges, and even offer an “allow list” strategy for administrators.
There was also a serious performance issue with NDI (lag, choppy audio/video) when streaming or transferring sources after the August update; it affected OBS and NDI Tools, especially with “Screen Capture” enabled. This was resolved in KB5065426 and later; if you are unable to install the patch, NDI recommended manually changing the receive mode to TCP or UDP instead of RUDP as a temporary solution.
The Event Viewer recorded, after July and August, error entries (ID 57) of CertificateServicesClient (CertEnroll) with the message “The Microsoft Pluton Cryptographic Service Provider could not be loaded because an initialization error occurred.” Microsoft clarified that the event was harmless and had no real impact, and that the resolution is being automatically enabled on devices with KB5064081, being completed in a few weeks.
Another issue: installing updates via WUSA from a shared folder with multiple .msu files could trigger ERROR_BAD_PATHNAME. The mitigation is to save the .msu locally (or have only one in the shared folder) and wait about 15 minutes after the restart for the Settings app to correctly mark the status. Microsoft applied a Known Issue Reversal (KIR) for unmanaged users; a final resolution will come in a future update.
In the area of family security, certain combinations of web filtering and unsupported browser versions caused unexpected shutdowns without prompting for parental approval when Activity Reports were disabled. Enabling “Activity Reports” mitigated the symptom, and the fix was included in the July preview (KB5062660) with gradual deployment.
There are more compatibility holds and safeguards: critical driver conflict sprotect.sys (SenseShield) that caused blue/black screens; audio loss on some devices with Dirac Audio (cridspapo.dll) After 24H2 (resolved and suspension lifted); camera apps crashing when using object/face detection (resolved); and lag for certain drivers Intel SST (IntcAudioBus.sys 10.29.0.5152/10.30.0.5152) that could cause BSOD when upgrading to 24H2, fixable by upgrading to versions 10.29.00.5714/10.30.00.5714 or higher.
Mitigations and practical steps if you are affected by the failures
For the DRM/HDCP issue, Microsoft does not offer an official workaround: if you rely on Blu-ray or digital TV, the wisest course of action is to delay installation KB5064081/KB5065426 and later until they release the fix. If you have already updated and are affected, check if your app allows you to skip the update. EVR or if you have an alternative rendering engine (e.g., SVR); in many cases this isn't possible, but it's worth checking out the advanced options.
If you experience network or share errors after KB5065426, several technical communities recommend, as a temporary solution, disable SMBv1 from “Turn Windows features on or off” when dealing with related issues (on some computers it helps stabilize). This is a temporary measure; it should be reversed when Microsoft releases the hotfix definitive or when you confirm that it does not provide any improvement.
For installation failures, run in a console with administrator privileges: DISM / Online / Cleanup Image / RestoreHealth and then, sfc / scannow. If everything is clean, try the manual installation again by downloading the package from the Microsoft Update CatalogIf you're using WUSA, save the .msu locally (avoid multiple .msu shares) and allow time after the reboot for Setup to update the status.
If you are unable to install or uninstall, consider using Windows Update Assistant or the Media Creation Tool for a data-preserving in-place reinstallation. Leave this as a last resort, but it works well for rebuilding computers that have been stuck due to Windows Update services or component corruption.
In the case of NDI and OBS, install KB5065426 or later and if you can't yet, change the receive mode to TCP/UDP in NDI to avoid the latency and choppy video issue. If you encounter the UAC requests unexpected in MSI repairs, make sure you have KB5065426 or higher and, if you manage a fleet of computers, study the allowed list of MSIs that Microsoft proposes for cases with elevated custom actions.
Why streaming is saved and not Blu-ray
There's a technical explanation for why Netflix and company aren't left to suffer while your Blu-ray drive refuses to play protected content. Modern OTT platforms don't rely on the legacy EVR pipeline with the same intensity, and use browser/app-specific paths and DRM/EME that are less sensitive to the changes introduced by KB5064081. However, applications that physical means and digital TV must comply with licensing and end-to-end protection requirements (HDCP/audio DRM) that fit directly with the affected subsystem.
In practice, that means that if your primary use is the streaming, you probably won't notice anything. If your routine includes playing CDs or receiving digital TV signals with EVR-based apps, then you are in the risk group. The worrying thing is that, without alternative solution official, the only guaranteed way today is to delay the patch or revert it if it is critical for you.
What Microsoft says today and what to expect
The section “Problems playing protected content” is available in Windows Release Health as open, originating from KB5064081 and affecting Windows 11 24H2. Microsoft indicates that it is working on resolutions for future updates. The company has already demonstrated rapid reaction capacity on other fronts (NDI, UAC/MSI), so it is reasonable to expect a cumulative correction in an upcoming patch date or a one-time hotfix.
In parallel, resolutions continue to be deployed for minor issues such as the event of CertEnroll and compatibility safeguards are maintained (drivers, audio, camera, backgrounds, Intel SST) to prevent the update from being offered to potentially problematic devices. This approach of selective retentions and gradual fixes helps limit the impact while finishing polishing 24H2.
If you manage IT, keep an eye on the Release Health dashboard, IDs issue and KIR documentation. If you're a home user, monitor Windows Update and consider pausing updates if your use case depends on Blu-ray/digital TV. Microsoft's priority should be to restore EVR/HDCP/DRM-secured playback as quickly as possible without breaking other parts of the system.
In the meantime, it's worth remembering that most of the bugs that appeared this month are unrelated. The coincidence of installation errors, SMB regressions, and the DRM bug creates a sense of chaos that doesn't always match technical reality. Separate each problem, apply the mitigation proper and waiting for the right patch often makes the difference.
Despite the noise, there are positive signs: Microsoft has already "cleaned up" sensitive issues (NDI, UAC/MSI), has been lifting safeguards (Dirac, camera), and is providing clear indications in Release Health. The key point for those who collect movies or use digital TV apps: Restore protected playback without any issues. If you're in that group, be patient, keep a backup of your drivers, and check your app to see if it offers an alternative rendering option to EVR.
If after installing KB5064081/KB5065426 If you're experiencing copyright errors, black screens on Blu-ray, or constant stuttering, it's not your graphics card or external player: it's a known bug. For problematic installations, run DISM/SFC and avoid WUSA from shared resources. For SMB, try temporary tweaks like disabling SMBv1 and checking permissions. And if you're streaming NDI, install the September patch or switch to TCP/UDP. When the EVR/HDCP/DRM fix arrives, it's ideal to update as soon as possible and completely close this chapter.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.