Windows 11 version 25H2 is now available for download. On September 30, 2025, Microsoft started the rollout of this year"s feature update for its operating system, thus kicking off a new 24-month lifecycle for regular users and a 36-month cycle for business customers.
Even though Windows 11 version 25H2 shares the same branch and features with Windows version 24H2, it still has a separate documentation for known issues and bugs that Microsoft is currently busy fixing. If you want to upgrade from a previous Windows 11 release, be sure to check out the list of known issues. Perhaps, there is a deal-breaking bug for you, so beware.
As of October 1, 2025, Windows 11 version 25H2 has the following known bugs:
| Bug | Status | Resolution |
|---|---|---|
| Problems playing protected content in some Blu-ray/DVD/Digital TV applications. Some Digital TV and Blu-ray/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. | Mitigated | 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. Microsoft is working on a permanent fix. |
| Updates installed via WUSA might fail if installed from a shared folder. 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. 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. | Mitigated | 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 was installed successfully. 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. |
You can track Windows 11 version 25H2 issues on the official Microsoft Learn website. As usual, Neowin will keep an eye on those developments and update you as they occur. If you want to install Windows 11 25H2 right now, check out this article, and those with unsupported PC can try this guide to install Windows 11 25H2 on ineligible hardware.