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 recently resolved issues for Windows 10, version 1507. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). 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.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| 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 10240.20751 KB5041782 2024-08-13 | Resolved KB5058387 | 2025-05-13 10:00 PT |
| Security policies might not work as expected and fail without an error message Prevent this issue by compiling the policy on a version of Windows released after 2016. | OS Build 10240.20752 KB5041782 2024-08-13 | Resolved | 2025-04-08 10:02 PT |
| Devices might boot into BitLocker recovery with the July 2024 security update This issue is more likely to affect devices that have the Device Encryption option enabled | OS Build 10240.20710 KB5040448 2024-07-09 | Resolved KB5041782 | 2024-08-13 10:00 PT |
Issue details
March 2025
Security policies might not work as expected and fail without an error message
| Status | Originating update | History |
|---|---|---|
| Resolved | OS Build 10240.20752 KB5041782 2024-08-13 | Resolved: 2025-04-08, 10:02 PT Opened: 2025-03-18, 16:04 PT |
Some security policies might not work as expected and fail without an error message. Administrators may notice that App Control for Business policies (formerly Windows Defender Application Control) are not being enforced, and their intended effects are not applying in their environments.
Please note that this issue occurs 'silently'; Windows will not display any warning or notification that the policy has failed. For affected devices, application blocks won’t work as expected, meaning applications intended to be blocked by a policy can still be run. The only way to detect if a device is affected by this issue is to monitor or manually test to confirm whether applications targeted by a block are able to run or not.
Resolution: This issue was resolved by Windows updates released April 8, 2025 (), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
If you install an update released April 8, 2025 or later, you do not need to use a workaround for this issue. If you are using an update released before April 8, 2025, and are experiencing this issue, you may consider the following workaround. This issue arises from the policy compilation processes used in Windows 10 Enterprise 2016, Windows Server 2016, or Windows 10 Enterprise 2015. If the policy is generated on systems running these versions, the resulting policy will carry the issue when applied across an environment. However, policies compiled on more recent Windows versions - such as Windows 10, version 22H2, or Windows Server 2022 - will work as expected, and the issue will not occur when they're applied.
Prevent this issue by compiling the policy on a version of Windows released after 2016. Afterwards, you can transfer and apply that policy to the target environment. The policy should then work as expected, even on devices running Windows versions released prior to 2016 (the versions listed in the Affected platforms section).
Affected platforms:
- Client: Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2016
August 2024
August 2024 security update might impact Linux boot in dual-boot setup devices
| Status | Originating update | History |
|---|---|---|
| Resolved KB5058387 | OS Build 10240.20751 KB5041782 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, (KB5041782) 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 (KB5058387), 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
July 2024
Devices might boot into BitLocker recovery with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5041782 | OS Build 10240.20710 KB5040448 2024-07-09 | Resolved: 2024-08-13, 10:00 PT Opened: 2024-07-23, 13:57 PT |
After installing the July 2024 Windows security update, released July 9, 2024 (KB5040448), you might see a BitLocker recovery screen upon booting your device. This screen does not commonly appear after a Windows update. You are more likely to face this issue if you have the Device Encryption option enabled in Settings under Privacy & Security -> Device encryption. Resulting from this issue, you might be prompted to enter the recovery key from your Microsoft account to unlock your drive.
Resolution: This issue was resolved by Windows updates released August 13, 2024 (KB5041782), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
If you install an update released August 13, 2024 (KB5041782) or later, you do not need to use a workaround for this issue. If you are using an update released before August 13, 2024, and have this issue, your device should proceed to start up normally from the BitLocker recovery screen once the recovery key has been entered. You can retrieve the recovery key by logging into the BitLocker recovery screen portal with your Microsoft account. Detailed steps for finding the recovery key are listed here: Finding your BitLocker recovery key in Windows.
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, Windows Server 2008 R2, Windows Server 2008
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.