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.
Known issues
Summary | Originating update | Status | Last updated |
---|---|---|---|
Authentication issues due to failed password rotation in Kerberos This issue is observed in a niche scenario when using PKINIT protocol and is resolved in the April 2025 security update. | N/A | Resolved KB5055523 | 2025-04-08 15:01 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 |
Remote Desktop might disconnect with January 2025 preview updates and later A resolution is rolling out to affected devices. IT admins can use a Group Policy to apply the rollback immediately. | OS Build 26100.3037 KB5050094 2025-01-28 | Resolved KB5053656 | 2025-03-28 12:11 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 |
Remote Desktop might freeze after installing the January 2025 preview update This issue currently affects Windows Server 2025 devices. A resolution is available for Windows 11, version 24H2. | OS Build 26100.3037 KB5050094 2025-01-28 | Resolved KB5052093 | 2025-03-25 11:19 PT |
Asphalt 8 might periodically stop responding Devices running Asphalt 8 might see an exception and compatibility hold has been applied to safeguard update experience. | N/A | Resolved | 2025-03-19 10:04 PT |
Disk Cleanup might incorrectly report space available for cleanup Despite cleaning up files, the application might display an incorrect estimate of space still available for cleanup | N/A | Resolved KB5044384 | 2025-03-14 16:46 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 |
Safe Exam Browser application might fail to open Devices running version 3.7 or lower versions of this application are incompatible with Windows 11, version 24H2. | N/A | Confirmed | 2024-10-01 07:05 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
April 2025
Authentication issues due to failed password rotation in Kerberos
Status | Originating update | History |
---|---|---|
Resolved KB5055523 | N/A | Resolved: 2025-04-08, 10:00 PT Opened: 2025-04-07, 16:30 PT |
After installing Windows 11, version 24H2, devices using the Identity Update Manager certificate/Public Key Cryptography for Initial Authentication (PKNIT), might experience an issue with passwords not rotating correctly, causing authentication failures. This issue occurs particularly when Kerberos Authentication is used and the Credential Guard feature is enabled. Note that machine certification using PKINIT path is a niche use case, and this issue affects a small number of devices in enterprise environments.
With this issue, devices fail to change their password every 30 days as the default interval. Because of this failure, devices are perceived as stale, disabled, or deleted, leading to user authentication issues.
Devices running Windows Home edition are unlikely to be affected by this issue, as Kerberos authentication is typically used in enterprise environments and is not common in personal or home settings.
Resolution:
This issue is resolved in the April 2025 Windows security update (KB5055523) and later updates. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: The feature Machine Accounts in Credential Guard, which is dependent on password rotation via Kerberos, has been disabled until a permanent fix is made available.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: Windows Server 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
March 2025
Remote Desktop might disconnect with January 2025 preview updates and later
Status | Originating update | History |
---|---|---|
Resolved KB5053656 | OS Build 26100.3037 KB5050094 2025-01-28 | Resolved: 2025-03-27, 10:00 PT Opened: 2025-03-24, 18:11 PT |
After installing the January 2025 Windows preview update (KB5050094) and later updates on Windows 11, version 24H2 devices, users might experience unexpected disconnections with Remote Desktop Protocol (RDP) sessions, including Remote Desktop Services (RDS). We've observed a significant increase in reports of this issue following the release of the March 2025 Windows security update (KB5053598).
Users might notice their RDP sessions unexpectedly disconnecting after 65 seconds when establishing UDP-based connections from Windows 11, version 24H2 devices to RDS deployments running versions Windows Server 2016 or earlier. Resulting from this issue, users might experience frequent disconnections from their Remote Desktop and RDS sessions.
IMPORTANT: Windows Server 2025 itself is not affected as an RDS host but may experience disconnects when acting as an RDP client connecting to older servers.
Resolution:
This issue was resolved by installing Windows updates released March 27, 2025 (KB5053656) on Windows 11, version 24H2 devices. You don't need to install any specific update on affected Windows Server 2025 devices to address this issue as servers were only affected when acting as an RDP client. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
If you have an enterprise-managed device and have installed the update released March 27, 2025 (KB5053656) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before March 27, 2025, and have this issue, your IT administrator can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > <Group Policy name 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:
- Download for Windows 11 Version 24H2 and Windows Server 2025 – Windows 11 24H2 and Windows Server 2025 KB5053598 250314_20401 Known Issue Rollback
This Group Policy will resolve this issue caused by the recent updates released in January, February, and March 2025.
Important:
You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting. Note that the Group Policy will temporarily disable the change causing this issue.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: Windows Server 2025
Remote Desktop might freeze after installing the January 2025 preview update
Status | Originating update | History |
---|---|---|
Resolved KB5052093 | OS Build 26100.3037 KB5050094 2025-01-28 | Resolved: 2025-02-25, 14:00 PT Opened: 2025-03-25, 10:26 PT |
After installing the January 2025 Windows preview update (KB5050094), released January 21, 2025, and later updates, on Windows 11, version 24H2 devices, you might experience Remote Desktop sessions freezing shortly after connection. When this issue occurs, mouse and keyboard input become unresponsive within the session, requiring users to disconnect and reconnect.
Resolution:
This issue was resolved in the February 2025 Windows preview update (KB5052093) available for Windows 11, version 24H2.
The resolution for this issue will be available in a future Windows update for Windows Server 2025.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: Windows Server 2025
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
Disk Cleanup might incorrectly report space available for cleanup
Status | Originating update | History |
---|---|---|
Resolved KB5044384 | N/A | Resolved: 2024-10-24, 10:00 PT Opened: 2024-10-14, 14:33 PT |
After using the Windows Disk Cleanup application, it may display an incorrect amount of disk space that can be freed up in the 'Windows Update Cleanup' category.
Please note this is a reporting error. When 'Windows Update Cleanup' is selected and Disk Cleanup is run for the first time, some or all files in that category (for example, 15 GB) are cleaned up correctly and the related disk space is freed as expected. However, after this initial run, the tool may inaccurately report an amount of space still available for cleanup (for example, 88 GB) in the 'Windows Update Cleanup' category. This inaccurate amount of disk space is reported even though the space was already freed in the initial run.
Resolution: Windows updates released October 24, 2024 (KB5044384) and later include improvements to the Windows Disk Cleanup tool which address some of the causes for incorrect estimates. We will continue to improve the accuracy of the free space estimates provided by the Disk Cleanup application in future Windows updates.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
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
Asphalt 8 might periodically stop responding
Status | Originating update | History |
---|---|---|
Resolved | N/A | Resolved: 2025-03-19, 10:04 PT Opened: 2024-09-30, 17:47 PT |
After installing Windows 11, version 24H2, you might face issues with Asphalt 8 (Airborne). The game might stop responding with an exception while you are using or exiting it, and you will have to restart the game to recover from the exception.
To safeguard your update experience, we have applied a compatibility hold on devices using Asphalt 8. 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: 52796746.
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: This issue has been resolved. The safeguard hold (ID 52796746) that was previously in place for this issue has been lifted.
It may take up to 48 hours for the Windows 11, version 24H2 update to be offered in the Windows Update in Settings. Restarting your device might expedite the process.
Affected platforms:
- Client: Windows 11, version 24H2
- Server: None
Safe Exam Browser application might fail to open
Status | Originating update | History |
---|---|---|
Confirmed | N/A | Last updated: 2024-10-01, 07:05 PT Opened: 2024-09-30, 17:47 PT |
After installing Windows 11, version 24H2, you will experience issues while opening the Safe Exam Browser app if you are running version 3.7 or lower versions of this application.
To safeguard your update experience, we have applied a compatibility hold on devices using versions 3.7 or older of this app. 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: 49562592.
If you are trying to install Windows 11, version 24H2 through the media creation tool, you will be able to proceed with the installation after you follow the instructions in the UI that pops up during the installation.
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant until this issue has been resolved.
Next steps: Safe Exam Browser and Microsoft are working on a resolution, and we will provide more information when it is available.
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.