Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Find information on known issues and the status of the Windows 11, version 24H2 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 September 30, 2025
Windows 11, version 25H2, also known as the Windows 11 2025 Update, is now available. We recommend you move to version 25H2 to stay up to date.
The rollout is phased and will expand over the next few months. Starting today, version 25H2 is available on eligible Windows 11, version 24H2 devices for users who have turned on the setting Get the latest updates as soon as they’re available. If the update is ready for your device, it will download and install automatically, and a single restart will complete the process.
For more details on how to install Windows 11, version 25H2, watch this video.
Note that devices running Home and Pro editions of Windows 11, versions 23H2, 22H2, and 21H2 that are not managed by IT departments have been receiving the update to Windows 11, version 24H2 automatically. You can choose the time to restart your device or postpone the update.
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).
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Non-admins might receive unexpected UAC prompts when doing MSI repair operations This issue can affect apps that use Windows Installer (MSI), such as Autodesk AutoCAD or Office Professional Plus 2010. | OS Build 26100.4946 KB5063878 2025-08-12 | Resolved KB5065426 | 2025-11-26 17:36 PT |
| IIS websites might fail to load Server-side applications that rely on HTTP.sys may experience issues with incoming connections. | OS Build 26100.6725 KB5065789 2025-09-29 | Resolved KB5067036 | 2025-11-26 17:36 PT |
| Task Manager process might continue to run in background after app is closed Overall system performance might be impacted when multiple instances of Task Manager app remain running after closure. | OS Build 26100.7019 KB5067036 2025-10-28 | Mitigated | 2025-10-31 10:45 PT |
| 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. | OS Build 26100.4202 KB5058499 2025-05-28 | Mitigated | 2025-09-30 10:04 PT |
| Parental consent may not show for some browser versions with web filtering on Children may not be able to use some browsers when web filtering is on, and Activity reporting is off in Family Safety | N/A | Mitigated | 2025-07-24 16:24 PT |
Issue details
October 2025
IIS websites might fail to load
| Status | Originating update | History |
|---|---|---|
| Resolved KB5067036 | OS Build 26100.6725 KB5065789 2025-09-29 | Resolved: 2025-10-28, 10:00 PT Opened: 2025-10-16, 16:06 PT |
After further investigation, we concluded that this issue was not applicable to Windows Server 2025. It affects only Windows 11, version 25H2 and 24H2.
This issue can be disregarded by Windows Server users.
To learn about the impact of this issue for Windows 11, select from the links below:
The issue mentioned below was published prior to this finding and November 14, 2025 edits:
Following installation of Windows updates releases on or after September 29, server-side applications that rely on HTTP.sys may experience issues with incoming connections. As a result, IIS websites might fail to load, displaying a message such as "Connection reset - error (ERR_CONNECTION_RESET)", or similar error. This includes websites hosted on http://localhost/, and other IIS connections.
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2
Task Manager process might continue to run in background after app is closed
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 26100.7019 KB5067036 2025-10-28 | Last updated: 2025-10-31, 10:45 PT Opened: 2025-10-31, 09:57 PT |
After installing Windows Updates released on or after October 28, 2025 (KB5067036), you might encounter an issue where closing Task Manager using the Close (X) button does not fully terminate the process. When you reopen Task Manager, the previous instance continues running in the background even though no window is visible. This results in multiple lingering instances of taskmgr.exe, consuming system resources and potentially degrading device performance. Additional instances appear as “Task Manager” in the Processes tab and as “Taskmgr.exe” in the Details tab. Although the impact is less if Task Manager is opened and closed a few times, many instances accumulated over time can cause noticeable slowdowns in other applications.
Workaround: If you are experiencing this issue, you can mitigate the issue by following one of the steps below:
- When closing Task Manager, instead of closing it with the 'X' button, use End Task on the Task Manager process itself. This can be done by going to the Processes tab, selecting the Task Manager process, and clicking End Task.
- To close multiple instances of Task Manager, you can use the command line prompt:
- Click Start (Windows icon) or press the Windows key.
- Type cmd or Command Prompt in the search box.
- Click Command Prompt from the results.
- To run as Administrator: Right-click Command Prompt and select Run as administrator.
- Run the command taskkill.exe /im taskmgr.exe /f and press enter.
- This will close all instances of Task Manager
Next Steps: We are working on a resolution for this issue and will provide more information when it is available.
Affected Versions:
- Client: Windows 11, version 25H2; Windows 11, version 24H2
- Server: None
September 2025
Non-admins might receive unexpected UAC prompts when doing MSI repair operations
| Status | Originating update | History |
|---|---|---|
| Resolved KB5065426 | OS Build 26100.4946 KB5063878 2025-08-12 | Resolved: 2025-09-09, 10:00 PT Opened: 2025-09-03, 14:28 PT |
(Updated 11/26/25: Additional improvements were added to the Resolution section.)
A security improvement was included in the August 2025 Windows security update (KB5063878) and later updates to enforce the requirement that User Account Control (UAC) prompt for administrator credentials when performing Windows Installer (MSI) repair and related operations. This improvement addressed security vulnerability CVE-2025-50173.
As a result, after installing the August 2025 Windows security update and later updates, UAC prompts for administrator rights can appear for standard users in the following scenarios:
- Running MSI repair commands (such as msiexec /fu).
- Launching Autodesk applications, including some versions of AutoCAD, Civil 3D and Inventor CAM, or when installing an MSI file after a user signs into the app for the first time.
- Installing applications that configure themselves per user.
- Running Windows Installer during Active Setup.
- Deploying packages via Manager Configuration Manager (ConfigMgr) that rely on user-specific "advertising" configurations.
- Enabling Secure Desktop.
If a standard user runs an app that initiates an MSI repair operation without displaying UI, it will fail with an error message. For example, installing and running Office Professional Plus 2010 as a standard user will fail with Error 1730 during the configuration process.
Resolution:
After installing the September 2025 Windows security update (KB5065426) or later updates, UAC prompts will only be required during MSI repair operations if the target MSI file contains an elevated custom action. This requirement is further refined after installing Windows updates released on and after October 28, 2025, so that UAC prompts will only be required if the elevated custom actions are executed during the repair flow.
Installing the latest Windows updates will resolve this issue for apps that do not execute such elevated custom actions, such as Autodesk AutoCAD.
Since UAC prompts will still be required for apps that perform custom actions, after installing the September 2025 update, IT admins will have access to a workaround to disable UAC prompts for specific apps by adding MSI files to an allowlist. For details, see the KB article: Unexpected UAC prompts when running MSI repair operations after installing the August 2025 Windows security update.
A Group Policy had previously been made available from Microsoft’s Support for business using Known Issue Rollback (KIR) to work around this issue. Organizations no longer need to install and configure this Group Policy to address this issue.
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2; Windows Server 2008 SP2
August 2025
Updates installed via WUSA might fail if installed from a shared folder
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 26100.4202 KB5058499 2025-05-28 | 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. These issues might occur on devices that installed updates released May 28, 2025 (KB5058499) and later.
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
June 2025
Parental consent may not show for some browser versions with web filtering on
| Status | Originating update | History |
|---|---|---|
| Mitigated | N/A | Last updated: 2025-07-24, 16:24 PT Opened: 2025-06-24, 16:25 PT |
Certain laws require Microsoft to protect children from harmful and illegal content on the internet. Microsoft is committed to creating tools for parents and guardians to help them in guiding their children’s digital experiences and protect them from harmful and illegal online content.
One of the available tools is web filtering, which lets a parent or guardian filter websites. Currently, Microsoft Edge is the only supported browser that provides this functionality within Microsoft Family Safety, allowing Edge to be used by default on the child’s device after web filtering is enabled. Once web filtering is enabled, a parent or guardian needs to approve other unsupported browsers (any browser other than Edge) before they can be used. This helps parents understand that different settings apply to other browsers when it comes to blocking inappropriate websites and filtering search results for their children.
The blocking behavior continues to work for unsupported browsers, however, when unsupported browsers update to a new version, the latest version of the browser cannot be blocked until we add it to the block list. Microsoft is currently adding the latest versions of unsupported browsers, to the block list. As a result, some browsers may temporarily appear unblocked during this update process. We're actively working to ensure all latest versions of browsers are blocked, reinforcing our commitment to parents and guardians.
As Microsoft continues to update the block list, we’ve received reports of a new issue affecting Google Chrome and some browsers. When children try to open these browsers, they shut down unexpectedly. However, the standard workflow is to prompt a parental approval message stating, “You’ll need to ask to use this app”. Once the approval is consented, the browser operates as intended. This issue is only observed when the Activity reporting feature is turned off.
Workaround: The browser shutdown issue can be temporarily mitigated by turning on Activity reporting under Windows settings in Family Safety. Parents will then be able to receive approval requests as expected.
Resolution:
- Temporary access to unsupported browsers: As of June 25, 2025, Microsoft included the latest versions of unsupported browsers into the Family Safety’s feature, and they are now blocked as intended. However, new versions of unsupported browsers released after this date might temporarily appear unblocked. This temporary gap will be resolved in the future, and this documentation will be updated to inform you when the full resolution is available.
- Missing parental consent prompt: Fixed in the July non-security preview update (KB5062660), released July 22, 2025. The fix is gradually rolling out and will be automatically enabled on devices with KB5062660 installed or later updates.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- Server: None
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.