Share via

Windows 11, version 24H2 known issues and notifications

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.
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
Connection and authentication failures in Azure Virtual Desktop and Windows 365
January 2026 Windows update causes Windows App credential prompt failures on Azure Virtual Desktop and Windows 365
OS Build 26100.7623
KB5074109
2026-01-13		Confirmed
2026-01-14
20:26 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

January 2026

Connection and authentication failures in Azure Virtual Desktop and Windows 365

StatusOriginating updateHistory
ConfirmedOS Build 26100.7623
KB5074109
2026-01-13		Last updated: 2026-01-14, 20:26 PT
Opened: 2026-01-14, 00:52 PT

After installing the January 2026 Windows security update (KB5074109), credential prompt failures occurred during Remote Desktop connections using the Windows App on Windows client devices, impacting Azure Virtual Desktop and Windows 365. The issue affects Windows App on specific Windows builds, causing sign-in failures. Investigation and debugging are ongoing, with coordination between Azure Virtual Desktop and Windows Update teams.

Workaround:

If you are impacted, please use one of the following connection options as a workaround:

Next steps: We are actively working on a resolution and plan to release an out-of-band (OOB) update in the coming days. Additional details will be shared as soon as they become available.

Affected platforms:

  • ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2, Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
  • ​Server: Windows Server 2025, Windows Server 2022, Windows Server 2019
Back to top

August 2025

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

StatusOriginating updateHistory
MitigatedOS 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:

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

June 2025

Parental consent may not show for some browser versions with web filtering on

StatusOriginating updateHistory
MitigatedN/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
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.

  • Last updated on