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 May 2, 2025
Windows 11, version 24H2, also known as the Windows 11 2024 Update, is broadly available. We have reached the last phase of the gradual rollout for version 24H2 via Windows Update on Settings.
If you have an eligible Windows 10 or Windows 11 device, you can look for the update 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 24H2. Note that some devices temporarily may not show the update to version 24H2 if we detect an incompatibility. You can find information on incompatibility issues and safeguard holds below on this page.
Devices running Home and Pro editions of Windows 11, versions 23H2, 22H2, and 21H2 that are not managed by IT departments will receive the update to version 24H2 automatically. You can choose the time to restart your device or postpone the update.
For Copilot+ PC devices, new features will continue rolling out in phases to select devices and markets starting in the Windows Insider community. Note that availability may differ based on the various silicon platforms.
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 |
|---|---|---|---|
| Error events are logged for Windows Firewall These events do not reflect an issue with Windows Firewall. They can be safely ignored. | OS Build 26100.4484 KB5060829 2025-06-26 | Confirmed | 2025-07-15 20:56 PT |
| Some Azure Virtual Machines with Trusted Launch disabled might fail to start This impacts a small subset of Gen 2 VMs on specific SKUs with VBS enabled after installing the July security update. | OS Build 26100.4652 KB5062553 2025-07-08 | Resolved KB5064489 | 2025-07-13 15:47 PT |
| Issues occur when using Microsoft Changjie Input Method Only devices using Traditional Chinese are affected. Reverting to the previous IME version prevents the issue. | OS Build 26100.4652 KB5062553 2025-07-08 | Confirmed | 2025-07-11 09:14 PT |
| AVD applications using App attach feature might fail to start Some AVD users reported errors on Windows 11, 24H2 devices while launching App attach applications. | N/A | Mitigated | 2025-07-01 11:27 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 | Confirmed | 2025-06-24 17:35 PT |
| Wallpaper customization applications might not work as expected Multiple applications are affected. A compatibility hold is in place. Updating applications might resolve the issue. | N/A | Mitigated | 2025-04-11 10:06 PT |
| Devices with apps using sprotect.sys driver might stop responding We have applied a safeguard hold to prevent affected devices from updating to version 24H2 and encountering this issue. | N/A | Confirmed | 2025-04-04 12:25 PT |
| Some devices that have Dirac Audio with cridspapo.dll might lose audio output Affected devices will not be offered the update to Windows 11, version 24H2 until this issue is resolved | N/A | Confirmed | 2025-03-25 14:16 PT |
| Camera use might cause some applications to become unresponsive Only a limited set of devices which use object recognition are confirmed to be impacted by this issue | N/A | Confirmed | 2024-10-18 14:02 PT |
| Some devices using Easy Anti-Cheat stop responding and receive a blue screen Older driver versions of the Easy Anti-Cheat application are incompatible with Windows 11, version 24H2 | N/A | Confirmed | 2024-10-01 07:05 PT |
| Compatibility issues with Intel Smart Sound Technology drivers Windows 11, version 24H2 devices with the affected Intel SST driver might receive an error with a blue screen. | N/A | Confirmed | 2024-10-01 07:00 PT |
Issue details
July 2025
Error events are logged for Windows Firewall
| Status | Originating update | History |
|---|---|---|
| Confirmed | OS Build 26100.4484 KB5060829 2025-06-26 | Last updated: 2025-07-15, 20:56 PT Opened: 2025-07-02, 10:10 PT |
Following installation of the June 2025 Windows non-security preview update (KB5060829), security event logs might include an error event related to Windows Firewall With Advanced Security, which can be safely ignored.
The error is found in Event Viewer as event 2042 for Windows Firewall With Advanced Security. The event appears as "Config Read Failed" with message "More data is available". Although this event is logged in Event Viewer every time the device is restarted, they do not reflect an issue with Windows Firewall, and can be disregarded.
Please note Windows Firewall is expected to function normally, and no action is required to prevent or resolve this error event. This event is related to a feature that is currently under development and not fully implemented. There is no impact to Windows processes associated to this event.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Note: This disclosure was mistakenly updated to Resolved status on July 8. A resolution for this issue is planned to be included in an update to be released in the coming weeks. We apologize for any inconvenience or confusion.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
Some Azure Virtual Machines with Trusted Launch disabled might fail to start
| Status | Originating update | History |
|---|---|---|
| Resolved KB5064489 | OS Build 26100.4652 KB5062553 2025-07-08 | Resolved: 2025-07-13, 14:00 PT Opened: 2025-07-11, 00:18 PT |
A small subset of Azure Virtual Machines (VMs) running Windows Server 2025 or Windows 11, version 24H2, with Trusted Launch disabled, and Virtualization-Based Security (VBS) enforced via registry key might fail to boot after installing the July Windows security update (KB5062553).
To check if your virtual machine might be impacted:
- Check if your VM is created as “Standard”.
- Check if VBS is enabled. Open System Information (msinfo32.exe) and confirm that Virtualization-based security is running and that the Hyper-V role is not installed in the VM.
Resolution: This issue was resolved in the out-of-band (OOB) update KB5064489, which is available via the Microsoft Update Catalog. If your virtual machine configuration is impacted by this issue, we recommend installing this out-of-band update instead of KB5062553.
Administrators can receive updated VM images for all editions of Windows Server 2025, including hotpatch editions. The new media is documented in the article, Windows Server images for July 2025.
Note: You can also prevent this issue by enabling Trusted Launch. Trusted Launch is required for Virtual Machines running Windows 11.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: Windows Server 2025
Issues occur when using Microsoft Changjie Input Method
| Status | Originating update | History |
|---|---|---|
| Confirmed | OS Build 26100.4652 KB5062553 2025-07-08 | Last updated: 2025-07-11, 09:14 PT Opened: 2025-07-11, 08:52 PT |
Following installation of the July 2025 Windows security updates (KB5062553), there might be issues when using the Microsoft Changjie IME (input method editor) for Traditional Chinese.
This issue only affects devices where Traditional Chinese is a preferred or common language or input method, and specifically where Changjie IME is used. Reported symptoms include:
- inability to form or select words after typing the full composition (associate phrase window)
- spacebar or blank key not responding
- incorrect or distorted word outputs
- the conversion candidate window fails to display properly
Microsoft Changjie is an IME that is included in Windows and available in currently supported versions.
Workaround: Windows IME supports a compatibility setting that allows using the previous version of an IME instead. Employing this option should help resolve this issue.
To revert to old version of the Microsoft Changjie IME, follow these steps:
- Open the Language & region setting. This can be accomplished by opening the Settings app, selecting Time & Language, then Language & Regions. You can also open the start menu and type "language" and select the top result.
- If Traditional Chinese is used on this device, the Chinese (Traditional) option will appear near the top. Select the three dots next to Chinese (Traditional) to open a menu and select Language Options.
- Under Keyboards, select the three dots next to Microsoft Changjie and select Keyboard Options from the menu.
- Under Compatibility, set the "Use previous version of Microsoft Changjie" option to On. Then select OK.
Next steps: We are working on a resolution and will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
- Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2016
June 2025
Parental consent may not show for some browser versions with web filtering on
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2025-06-24, 17:35 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 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 browsers 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, however, when a browser updates 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 Chrome and other 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.
Next steps: We are actively working on a resolution for the two key issues: the missing parental consent prompts and the unintended temporary unblocking of the latest versions of Google Chrome and other browsers after a browser update with a version change. This documentation will be updated when more information is available.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- Server: None
May 2025
AVD applications using App attach feature might fail to start
| Status | Originating update | History |
|---|---|---|
| Mitigated | N/A | Last updated: 2025-07-01, 11:27 PT Opened: 2025-05-02, 13:28 PT |
After upgrading to Windows 11, version 24H2, Azure Virtual Desktop (AVD) users might face issues with applications using the App attach feature. While attempting to start App attach applications, users might encounter an error message that displays the error message ‘Element not found’. App attach is a feature that allows users to add applications to user sessions without installing them directly on the virtual machine.
This issue is expected to occur when App attach applications are packaged in CIMFS (Composite Image File System) format. CIMFS is a file system used in Azure Virtual Desktop for managing application images.
This issue only applies to Windows versions running in Azure Virtual Desktop.
Resolution: This resolution is gradually rolling out and will be fully enabled on devices with KB5060829 (released June 26, 2025) and subsequent updates installed. We recommend you install the latest update for your device, as it contains important improvements and issue resolutions, including this one
If you are using an update released before June 26, 2025, and have this issue, you can use a VHDX (Virtual Hard Disk v2) image instead of CIMFS image for packaging files.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
April 2025
Devices with apps using sprotect.sys driver might stop responding
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2025-04-04, 12:25 PT Opened: 2025-04-04, 12:04 PT |
Microsoft is working with SenseShield Technology Co on a compatibility issue between Windows 11, version 24H2 and the sprotect.sys driver. This issue causes affected devices to become unresponsive and display a blue or black screen error. The sprotect.sys driver provides encryption protection and is used by specialized security software and enterprise solutions. This driver can be automatically introduced into a system as part of the installation process of many different applications. The issue impacts devices with any version of the sprotect.sys driver (1.0.2.372 and 1.0.3.48903).
To safeguard your update experience, we have applied a compatibility hold on devices running the incompatible sprotect.sys driver. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel.
If you have a Home or Pro Windows device affected by this hold, the Windows Update page under Settings will display a message saying you don’t need to take any action now. You can click on the Learn more link for details. For more information, see KB5006965: How to check information about safeguard holds affecting your device. IT administrators using Windows Update for Business reports can check this issue using safeguard ID 56318982.
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.
Next Steps: SenseShield is currently investigating this issue. Microsoft is collaborating with SenseShield, and we will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
December 2024
Some devices that have Dirac Audio with cridspapo.dll might lose audio output
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2025-03-25, 14:16 PT Opened: 2024-12-18, 10:34 PT |
A compatibility safeguard hold has been applied to a limited set of devices from one manufacturer due to an audio issue following the installation of Windows 11, version 24H2. This issue was observed on some devices containing Dirac Audio with the cridspapo.dll file. The incompatibility relates to the software component cridspapo.dll, which is part of these devices’ audio processing software. Dirac Audio is a digital sound improvement technology that enhances audio clarity and precision.
After installing Windows 11, version 24H2, some users reported that their device’s integrated speakers, Bluetooth speakers, and Bluetooth headsets stopped functioning. They also reported that both first-party and third-party applications didn’t recognize these devices.
To prevent you from encountering this audio issue, we have applied a compatibility hold on devices containing Dirac Audio with cridspapo.dll. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update channel until this issue is resolved. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 54283088.
If you are using a Windows Home or Pro edition as your personal device, you can check whether your device has this or other safeguard holds applied. Go to Start > Settings >Windows Update > select Check for Windows updates. If your device has a compatibility hold, you will see the message “Upgrade to Window 11 is on its way to your device. There is nothing that requires your attention at the moment. Once the update is ready for your device, you’ll see it available on this page.” This message will be followed by the link “Learn More”, which will direct you to website listing safeguards applicable specifically to your device. For more information, see KB5006965.
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.
Next Steps: Once the driver addressing this issue is released by the manufacturer, Microsoft will partner to offer the new driver via Windows Update to resolve this audio issue. The safeguard hold preventing the update to version 24H2 will be lifted after this issue is resolved on end-users’ devices.
Affected Platforms:
- Client: Windows 11, version 24H2
- Server: None
October 2024
Camera use might cause some applications to become unresponsive
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2024-10-18, 14:02 PT Opened: 2024-10-18, 13:21 PT |
After installing Windows 11, version 24H2, certain devices might experience problems using the integrated camera in scenarios where object or face detection features are enabled. This can include using the Camera app, using facial recognition sign-in options with Windows Hello, and other applications that use the integrated camera.
To safeguard your update experience, we have applied a compatibility hold on device models affected by this issue. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 53340062.
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.
Next Steps: We are working on a resolution and will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
September 2024
Wallpaper customization applications might not work as expected
| Status | Originating update | History |
|---|---|---|
| Mitigated | N/A | Last updated: 2025-04-11, 10:06 PT Opened: 2024-09-30, 17:48 PT |
After installing Windows 11, version 24H2, some wallpaper customization applications might not launch or function correctly. Multiple applications are affected, and symptoms can include wallpapers not appearing correctly, icons disappearing from the desktop, loss of desktop preview functionality, issues with virtual desktops, or error messages displayed by the application.
To safeguard your update experience, we have applied a compatibility hold on devices which are utilizing one of these applications. These devices will not be offered or install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 52754008.
Resolution: We have started to gradually remove this safeguard hold. If you try to install version 24H2 using Windows Update under Settings, Windows 11 Installation Assistant, or Media Creation Tool, you might receive a message requesting you to uninstall your wallpaper app. We also recommend updating the app, since a newer version might be compatible. Or you may uninstall, instead. After you complete this action, you will be able to finish installing version 24H2.
Note that several wallpaper applications are currently included in this compatibility hold. For this reason, the specific timing of the resolution of this issue on a given device may depend on the application being used and the timing of that application's update. As new versions and updates are released for these applications by their respective developers, it's expected that these issues will be resolved.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
Some devices using Easy Anti-Cheat stop responding and receive a blue screen
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2024-10-01, 07:05 PT Opened: 2024-09-30, 16:51 PT |
Microsoft is working with Easy Anti-Cheat on an incompatibility issue between Window 11, version 24H2 and the Easy Anti-Cheat application. This software is automatically installed with some games as part of security and cheat-prevention measures used in multiplayer online PC games. Only devices with Intel’s Alder Lake+ processors and vPro platform are affected. In rare cases, when users open or play certain games, this issue causes affected devices to stop responding and to show a blue screen with the error “MEMORY_MANAGEMENT”. Most devices experiencing this issue use Easy Anti-Cheat drivers released before April 2024.
To safeguard your update experience, we have applied a compatibility hold on devices running the incompatible Easy Anti-Cheat drivers. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 52325539.
If you are trying to install Windows 11, version 24H2 through the media creation tool and your device has incompatible drivers, you will receive a pop-up message alerting that your device is not ready for this new version of Windows.
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.
Resolution: Updating your games might help address this issue, depending on whether a compatible version of Easy Anti-Cheat is also included in the game’s update.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
Compatibility issues with Intel Smart Sound Technology drivers
| Status | Originating update | History |
|---|---|---|
| Confirmed | N/A | Last updated: 2024-10-01, 07:00 PT Opened: 2024-09-30, 16:44 PT |
Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors and Windows 11, version 24H2. Devices running version 24H2 with the affected Intel SST driver might receive an error with a blue screen. The affected driver is named Intel® Smart Sound Technology (Intel® SST) Audio Controller. It is listed under System Devices in Device Manager and is found with the file name 'IntcAudioBus.sys'. If this file is version 10.29.0.5152 or 10.30.0.5152, this issue can occur.
Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10.29.0.5152 or 10.30.0.5152 are affected by this issue.
To safeguard your update experience, we have applied a compatibility hold on Windows devices which have Intel SST driver versions 10.29.0.5152 or 10.30.0.5152. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 51876952.
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.
Resolution: Devices which are encountering this issue will need to install newer versions of the Intel® SST Audio Controller drivers prior to updating to Windows 11, version 24H2. The issue is resolved by updating the Intel® Smart Sound Technology drivers to version 10.30.00.5714 and later, or 10.29.00.5714 and later. Please note that later versions of this driver might refer to only the last part of the version number. For the purpose of addressing this issue, 10.30.x versions are not newer than 10.29.x versions.
For most users, updated drivers can be installed via Windows Update by checking for Windows updates on your device. This is the preferred method of installing these and other drivers. If your device still encounters this safeguard hold 48 hours after updating your drivers, it's possible drivers for this Audio Controller haven't been developed for your specific device hardware configuration. In this case, you will need to contact your device manufacturer (OEM) for more information on the necessary drivers. Microsoft works to make the latest compatible drivers available under Windows Update whenever developers have released them.
IT admins in organizations where devices are managed can refer to the following resources to deploy drivers using one of these tools:
- Windows Update for Business and Intune customers: Learn about Windows Driver updates policy for Windows 10 Windows 11 devices in Intune
- Autopatch: Manage driver and firmware updates
Once you have updated to a compatible version of the Intel® Smart Sound Technology drivers, you should be able to upgrade to Windows 11, version 24H2. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to version 24H2 is offered.
Affected platforms:
- Client: Windows 11, version 24H2
- 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.