Microsoft recently released the September monthly update KB5065789 for Windows 11 version 25H2. You can read more about the Windows 11 update KB5065789 by clicking here. They have now acknowledged and confirmed two new issues after the installation of August update on devices.
After this update, Some Digital TV and BluRay/DVD applications might experience problems playing protected content and also windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files.
First issue
Problems playing protected content in some BluRay/DVD/Digital TV applications
Expand table
Status Originating update History
Mitigated N/ALast updated: 2025-09-30, 17:29 PT
Opened: 2025-09-19, 14:24 PT
Some Digital TV and BluRay/DVD applications might experience problems playing protected content. Applications using Enhanced Video Renderer with HDCP enforcement or Digital Rights Management (DRM) for digital audio might experience copyright protection errors, frequent playback interruptions, freezing or black screens. This issue does not impact streaming services.Resolution: This issue is partially resolved. Problems affecting certain applications that use Enhanced Video Renderer with HDCP enforcement have been addressed in the September 2025 Windows preview update (KB5065789), and later updates. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
However, some applications using DRM for digital audio might continue to experience problems.
Next steps:Â We are working on a permanent fix for applications that still experience this issue and will provide more information when it is available.
Affected platforms:
Client: Windows 11, version 25H2; Windows 11, version 24H2
Server: None
Updates installed via WUSA might fail if installed from a shared folder
Expand table
Status Originating update History
Mitigated N/ALast updated: 2025-09-30, 10:04 PT
Opened: 2025-08-15, 11:56 PT
Windows updates installed using the Windows Update Standalone Installer (WUSA)Â might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files.WUSA is a method of installing updates using the Windows Update Agent API which is typically only employed in enterprise environments. It is not common in personal or home settings.
Please note that this issue does not occur when there is only one .msu file in the network share or when the .msu files are stored locally on the device. In addition, after installing an .msu file by double-clicking or using WUSA and restarting Windows, you might notice that the Update History page in Settings continues to indicate that a restart is required to complete the update. This is temporary and should be resolved on its own.
Workaround: To work around this issue, save the .msu files locally on the device and install the update from this location. Also, if you’ve restarted Windows after installing an .msu file via WUSA, please wait 15 minutes or more before checking the Update History page in Settings. After this short delay, the Settings app should properly indicate if the update installed successfully.
Mitigation:Â This issue is addressed using Known Issue Rollback (KIR) and is resolved automatically for most home users and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster.
IT admins can resolve this issue for managed devices which have installed the affected update and encountered this issue. It can be fixed by installing and configuring the Group policy listed below. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. The special Group Policy can be found in Computer Configuration > Administrative Templates > [Group Policy name].
Group Policy downloads with Group Policy name:
Download for Windows 11, version 24H2 and Windows Server, version 2025 – Windows 11 24H2 and Windows Server 2025 KB5062660 250806_17201 Known Issue Rollback.msi
Next steps: We are working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available.Affected platforms:
Client: Windows 11, version 25H2; Windows 11, version 24H2
Server: Windows Server 2025