Share via


Windows 11, version 25H2 known issues and notifications

Find information on known issues and the status of the Windows 11, version 25H2 rollout. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.

Current status as of December 4, 2025  
 
Windows 11, version 25H2 is now available to all eligible Windows 11 devices for users who have turned on the setting Get the latest updates as soon as they’re available. If you have an eligible Windows 10 or Windows 11 device, you can check if the update is available by selecting Settings > Windows Update and selecting Check for updates. If your device is ready for the update, you’ll see the option to Download and install Windows 11, version 25H2. For more details, watch this video.

The machine learning-based intelligent rollout has begun for devices running Home and Pro editions of Windows 11, version 24H2 that are not managed by IT departments. As part of a gradual rollout, these devices will automatically receive the update to Windows 11, version 25H2 when they’re ready. No action is required, and you can choose when to restart your device or postpone the update.
See all messages >

Known issues

See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

SummaryOriginating updateStatusLast updated
Updates installed via WUSA might fail if installed from a shared folder
This issue might occur when installing an update from a network folder containing multiple .msu files.
N/A

Mitigated
2025-09-30
10:04 PT

Issue details

August 2025

Updates installed via WUSA might fail if installed from a shared folder

StatusOriginating updateHistory
MitigatedN/A

Last 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:

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
Back to top

Report a problem with Windows updates

To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.

Need help with Windows updates?

Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.

For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.

View this site in your language

This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.