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 22H2 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 (formerly Twitter) 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.
Summary | Originating update | Status | Last updated |
---|---|---|---|
August 2024 security update might impact Linux boot in dual-boot setup devices This issue might impact devices with dual-boot setup for Windows and Linux when SBAT setting is applied | OS Build 22621.4037 KB5041585 2024-08-13 | Resolved KB5058405 | 2025-05-13 10:05 PT |
Windows 11, version 24H2 might not download via Windows Server Updates Services Devices with April 2025 security update fail to download, showing error 0x80240069 | OS Build 22621.5189 KB5055528 2025-04-08 | Resolved KB5058405 | 2025-05-13 10:05 PT |
Status | Originating update | History |
---|---|---|
Resolved KB5058405 | OS Build 22621.5189 KB5055528 2025-04-08 | Resolved: 2025-05-13, 10:00 PT Opened: 2025-04-29, 15:40 PT |
Devices which have installed the April Windows monthly security update, released April 8, 2025, (KB5055528), the April 11, 2025, Windows out-of-band update (KB5058919), or the April 22, 2025, Windows preview update (KB5055629), might be unable to update to Windows 11, version 24H2 via Windows Server Update Services (WSUS). WSUS allows Servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization.
As part of this issue, the download of Windows 11, version 24H2 does not initiate or complete. Windows updates log can show error code 0x80240069, and further logs might include text similar to "Service wuauserv has unexpectedly stopped".
Resolution: This issue was resolved by Windows updates released May 13, 2025 (KB5058405), and later. We recommend you install the latest security 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 May 13, 2025 KB5058405, 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 May 13, 2025, and have this issue, your IT administrator can resolve it by installing and configuring the special Group Policy listed below.
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 23H2 and Windows 11, version 22H2 – Windows 11 22H2 KB5055528 250426_03001 Known Issue Rollback.msi (also applicable to Windows 11, version 23H2)
The special Group Policy can be found in Computer Configuration > Administrative Templates > <Group Policy name>. For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2
- Server: None
Status | Originating update | History |
---|---|---|
Resolved KB5058405 | OS Build 22621.4037 KB5041585 2024-08-13 | Resolved: 2025-05-13, 10:00 PT Opened: 2024-08-21, 18:33 PT |
After installing the August 2024 Windows security update, (KB5041585) or the August 2024 preview update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device. Resulting from this issue, your device might fail to boot Linux and show the error message “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.”
The August 2024 Windows security and preview updates apply a Secure Boot Advanced Targeting (SBAT) setting to devices that run Windows to block old, vulnerable boot managers. This SBAT update will not be applied to devices where dual booting is detected. On some devices, the dual-boot detection did not detect some customized methods of dual-booting and applied the SBAT value when it should not have been applied.
IMPORTANT: This known issue only occurs with the installation of the August 2024 security and preview updates. The September 2024 security update and later updates do not contain the settings that caused this issue.
Resolution: This issue was resolved by Windows updates released May 13, 2025 (KB5058405), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: On Windows-only systems, after installing the September 2024 or later updates, you can set the registry key documented in CVE-2022-2601 and CVE-2023-40547 to ensure the SBAT security update is applied. On systems that dual-boot Linux and Windows, there are no additional steps necessary after installing the September 2024 or later updates.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
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.
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.
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.