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 22H2. 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 |
|---|---|---|---|
| The April 2025 Windows RE update might show as unsuccessful in Windows Update Users might observe installation failure while trying to install the WinRE update which resolves after device restarts. | N/A KB5057589 2025-04-08 | Resolved KB5063523 | 2025-07-08 10:00 PT |
| Surface Hub v1 fails to start with error, "Secure Boot Violation" Surface Hub v1 devices might fail to start after installing the June 2025 security update | OS Build 19045.5965 KB5060533 2025-06-10 | Resolved KB5063159 | 2025-06-16 10:00 PT |
| Windows 10 might repeatedly display the BitLocker recovery screen at startup After installing the May 2025 update (KB5058379), Windows 10 might start to the BitLocker recovery screen. | OS Build 19045.5854 KB5058379 2025-05-13 | Resolved KB5061768 | 2025-05-19 10:00 PT |
| 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 19045.4780 KB5041580 2024-08-13 | Resolved KB5058379 | 2025-05-13 10:00 PT |
| Start menu jump lists for some apps might not work as expected on Windows 10 This issue affects all applications on the Start menu and has been automatically resolved for affected devices. | OS Build 19045.5555 KB5052077 2025-02-25 | Resolved | 2025-05-02 13:56 PT |
| USB printers might print random text with the January 2025 preview update This issue is observed with USB dual-mode printers that support both USB Print and IPP Over USB protocols. | OS Build 19045.5440 KB5050081 2025-01-28 | Resolved KB5053643 | 2025-03-25 10:00 PT |
| Users might be unable to update or uninstall packaged apps on Windows 10 This issue impacts users who have received WinAppSDK 1.6.2 package on their Windows 10 devices. | N/A | Resolved KB5046714 | 2024-11-21 10:00 PT |
| Apps that set UIAccess=true might fail to start for non-admin users This issue is due to child processes of these apps running with Integrity level low instead of Integrity level medium | OS Build 19045.4957 KB5043131 2024-09-24 | Resolved KB5046613 | 2024-11-12 10:00 PT |
| Azure Virtual Desktop users might experience black screen during login This issue affects enterprise users with multi-session environments due to issues with AppX Deployment Service | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved KB5045594 | 2024-10-22 10:00 PT |
| AVD users might experience extended black screen during logon and SSO failures This issue affects enterprise users using FSLogix user profile containers on multi-session environments. | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved KB5045594 | 2024-10-22 10:00 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 19045.4651 KB5040427 2024-07-09 | Resolved KB5041580 | 2024-08-13 10:00 PT |
| CrowdStrike issue impacting Windows endpoints causing an error message Affected systems might restart repeatedly and require recovery operations in order to restore normal use. | N/A | Resolved External | 2024-08-05 16:07 PT |
| Enterprise customers might be unable to use Microsoft Connected Cache This issue affects Windows devices which use the DHCP Option 235 to configure the Microsoft Connected Cache endpoint | OS Build 19045.3996 KB5034203 2024-01-23 | Resolved KB5040525 | 2024-07-23 10:00 PT |
| Desktop icons might move unexpectedly between monitors This issue is only observed if you are using more than one monitor when attempting to use Copilot in Windows. | OS Build 19045.3758 KB5032278 2023-11-30 | Resolved KB5039299 | 2024-06-25 14:00 PT |
| Apps show "Open With" dialog when right-clicking on Taskbar or Start menu icons You might experience this when right-clicking an app icon shown in your Taskbar or Start menu to execute a task. | OS Build 19045.4355 KB5036979 2024-04-23 | Resolved KB5039299 | 2024-06-25 14:00 PT |
Issue details
June 2025
Surface Hub v1 fails to start with error, "Secure Boot Violation"
| Status | Originating update | History |
|---|---|---|
| Resolved KB5063159 | OS Build 19045.5965 KB5060533 2025-06-10 | Resolved: 2025-06-16, 10:00 PT Opened: 2025-06-11, 18:07 PT |
After installing the June 2025 Windows security update (KB5060533), Surface Hub v1 devices might fail to start with the following error:
Secure Boot Violation Invalid signature detected. Check Secure Boot Policy in Setup
Note: Surface Hub 2S and Surface Hub 3 are not impacted by this issue.
Mitigation: A Windows out-of-band update was released June 16, 2025, (KB5063159), which prevents new Surface Hub v1 devices from encountering this issue. This out-of-band update is offered to Surface Hub v1 devices instead of update KB5060533.
Resolution: If you need to recover your Surface Hub v1 device for this issue, the Surface team has developed a recovery solution that can be used in coordination with Microsoft Support. Please create a support request or contact Surface support for steps to recover your device.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
May 2025
Windows 10 might repeatedly display the BitLocker recovery screen at startup
| Status | Originating update | History |
|---|---|---|
| Resolved KB5061768 | OS Build 19045.5854 KB5058379 2025-05-13 | Resolved: 2025-05-19, 10:00 PT Opened: 2025-05-16, 08:58 PT |
We are aware of a known issue on devices with Intel Trusted Execution Technology (TXT) enabled on 10th generation or later Intel vPro processors. On these systems, installing the May 13, 2025, Windows security update (KB5058379) might cause lsass.exe to terminate unexpectedly, triggering an Automatic Repair. On devices with BitLocker enabled, BitLocker requires the input of your BitLocker recovery key to initiate the Automatic Repair.
Affected devices then enter one of two states:
- Some devices might make several attempts to install update KB5058379 before Startup Repair successfully rolls back to the previously installed update.
- Startup Repair might experience a failure that creates a reboot loop, which again initiates an Automatic Repair, returning the device to the BitLocker recovery screen.
Consumer devices typically do not use Intel vPro processors and are less likely to be impacted by this issue. This issue ONLY applies to the affected platforms listed below.
Additional symptoms reported on affected devices include:
- Event ID 20 might appear in the Windows Event Viewer in the System event log, with the following text: "Installation Failure: Windows failed to install the following update with error 0x800F0845: 2025-05 Cumulative Update for Windows 10 22H2 for x64-based Systems (KB5058379)."
- Event ID 1074 might appear in the System event log, with the text: "The system process 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status code -1073740791."
Resolution:
This issue was resolved in the out-of-band (OOB) update KB5061768, which is only available via the Microsoft Update Catalog. If your organization uses the affected platforms and hasn’t yet deployed the May 13, 2025, Windows security update, or if KB5058379 failed to install, we recommend you apply this OOB update instead.
If your device has already installed the May 2025 Windows security update and is unable to start Windows:
- To start Windows, temporarily disable Intel VT for Direct I/O (also known as VTD or VTX) and Intel Trusted Execution Technology (TXT) in your BIOS / UEFI settings. This step will require entering your BitLocker recovery key.
- Install update KB5061768 via the Microsoft Update Catalog.
- After restarting Windows, return to your BIOS / UEFI settings and re-enable Intel VT for Direct I/O (also known as VTD or VTX) and TXT. (This step will require entering your BitLocker recovery key.)
Important: Microsoft Support doesn't have the ability to retrieve, provide, or recreate a lost BitLocker recovery key. For help finding your BitLocker recovery key, see Find your BitLocker recovery key.
Affected platforms:
- Windows 10, versions 22H2; Windows 10 Enterprise LTSC 2021
- Server: None
Start menu jump lists for some apps might not work as expected on Windows 10
| Status | Originating update | History |
|---|---|---|
| Resolved | OS Build 19045.5555 KB5052077 2025-02-25 | Resolved: 2025-05-02, 13:56 PT Opened: 2025-05-02, 13:24 PT |
Microsoft has received reports of users being unable to view the jump list for apps, which includes the recent list of files used, while right-clicking on an app tile in the Start menu, on devices that installed updates released February 25, 2025 (KB5052077) and later. Jump list is a feature in Windows 10 that provides quick access to files and tasks when right-clicking the app's icon in the taskbar or Start menu. The rollout causing this issue has been paused since April 25, 2025, so no new devices should experience it, and users affected earlier should not be experiencing it after this date.
This issue primarily affected home users of Windows 10 Home and Pro editions.
This issue was caused by a recent feature rollout that integrates account control experiences in the Start Menu for users on Windows 10 22H2. Account control provides users with an easily accessible way to manage their accounts and helps them get the most value from their accounts. This rollout began gradually in March 2025 via Controlled Feature Rollout (CFR), which is the process of gradually rolling out new features to compatible devices.
Resolution: This issue was resolved by a service change that was rolled out on April 25, 2025. If you are still facing this issue, please ensure that your device is connected to the internet to receive the automatic resolution that has been rolled out. After the next reboot, this issue should be resolved.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
April 2025
The April 2025 Windows RE update might show as unsuccessful in Windows Update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5063523 | N/A KB5057589 2025-04-08 | Resolved: 2025-07-08, 10:00 PT Opened: 2025-04-11, 17:03 PT |
After installing the April 2025 Windows Recovery Environment update [KB5057589], you might see the following error message in the Windows Update settings page: 0x80070643 – ERROR_INSTALL_FAILURE. This error message is not accurate and does not impact the update or device functionality. The Windows Recovery Environment (WinRE) is a recovery environment that can repair common causes of unbootable operating systems.
This error is observed when the device installs the WinRE update when there is another update in a pending reboot state. Although the error message suggests the update did not complete, the WinRE update is typically applied successfully after the device restarts. Windows Update might continue to display the update as failed until the next daily scan, at which point the update is no longer offered and the failure message is cleared automatically.
Resolution:
The ERROR_INSTALL_FAILURE error message that was previously observed with KB5057589 installed before 2 PM PT on April 21, 2025 has been resolved with the Windows update released July 8, 2025 (KB5063523). We recommend you install the latest update for your device as it contains important improvements and issue resolutions.
Please note: This update does not remove the incorrect error message which might still appear in the Windows Update History page.
Users who installed KB5057589 after 2 PM PT on April 21, 2025, should not observe the incorrect error message about the install failure. If the update is already installed, it will not be offered again, and the status of this update can be verified with the Dism /Online /Get-Packages command.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2
- Server: Windows Server 2022
March 2025
USB printers might print random text with the January 2025 preview update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5053643 | OS Build 19045.5440 KB5050081 2025-01-28 | Resolved: 2025-03-25, 10:00 PT Opened: 2025-03-11, 17:04 PT |
After installing the January 2025 Windows preview update (KB5050081), released January 29, 2025, or later updates, you might observe issues with USB connected dual-mode printers that support both USB Print and IPP Over USB protocols. You might observe that the printer unexpectedly prints random text and data, including network commands and unusual characters. Resulting from this issue, the printed text might often start with the header "POST /ipp/print HTTP/1.1", followed by other IPP (Internet Printing Protocol) related headers. This issue tends to occur more often when the printer is either powered on or reconnected to the device after being disconnected.
The issue is observed when the printer driver is installed on the Windows device, and the print spooler sends IPP protocol messages to the printer, causing it to print unexpected text.
Resolution:
This issue was resolved by Windows updates released March 25, 2025 (KB5053643), 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 have an enterprise-managed device and have installed the update released March 25, 2025 (KB5053643) 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 25, 2025, 2024, 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.
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 23H2 and 22H2 - Windows 11 22H2 KB5050092 250131_150523 Known Issue Rollback
- Download for Windows 10, version 22H2 - Windows 10 22H2, 21H1, 21H2 and 22H2 KB5050081 250131_082569 Known Issue Rollback
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 the printing issue.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- Server: None
November 2024
Users might be unable to update or uninstall packaged apps on Windows 10
| Status | Originating update | History |
|---|---|---|
| Resolved KB5046714 | N/A | Resolved: 2024-11-21, 10:00 PT Opened: 2024-11-20, 19:54 PT |
Starting November 12, 2024, Windows 10 users might experience issues while trying to update or uninstall packaged apps. Affected Windows 10 devices have received the WinAppSDK 1.6.2 package (published on November 12, 2024). When users download an app that relies on WinAppSDK, the necessary components of the SDK are automatically downloaded and installed along with the app.
Resulting from this issue, you might observe that Microsoft Store displays the error message, ‘Something happened on our end’ in the ‘Downloads’ panel.
If you are an IT administrator trying to manage packaged apps through PowerShell using ‘Get-AppxPackage’ command you might observe the error ‘Deployment failed with HRESULT: 0x80073CFA’, ‘Please contact your software vendor. (Exception from HRESULT: 0x80073CFA’) in PowerShell.
You will also notice that apps like Microsoft Teams and other 3rd party apps are impacted if you choose to uninstall and re-install the apps as part of the update process.
Please note, this issue is not caused by a Windows security or preview monthly update.
Resolution: This issue was resolved by Windows updates released November 21, 2024 (KB5046714), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
AVD users might experience extended black screen during logon and SSO failures
| Status | Originating update | History |
|---|---|---|
| Resolved KB5045594 | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved: 2024-10-22, 10:00 PT Opened: 2024-11-01, 14:11 PT |
A small subset of Azure Virtual Desktop customers using multi-session hosts (AVD) who have installed Windows Updates released between KB5040525 on July 23, 2024, and KB5044273 released October 8, 2024, may experience the following issues:
- An extended 10-to-30-minute-long hang at a black screen following user logon.
- Office applications including Outlook and Teams experience single sign-on (SSO) failures, preventing users from connecting or synchronizing data.
This issue is caused by a deadlock in the interactions between the Azure Active Directory(AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service.You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Resolution:
This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
October 2024
Apps that set UIAccess=true might fail to start for non-admin users
| Status | Originating update | History |
|---|---|---|
| Resolved KB5046613 | OS Build 19045.4957 KB5043131 2024-09-24 | Resolved: 2024-11-12, 10:00 PT Opened: 2024-10-30, 12:45 PT |
After installing the September 2024 preview update (KB5043131), released September 24, 2024 or later, you might observe that apps such as Quick Assist, Microsoft Teams, Windows Narrator, etc might fail to start if you are a non-admin user. You might experience this issue on any app that sets UIAccess=true while trying to run the app as a non-admin user. The uiAccess=true attribute in an application's manifest file is used to request that the application be granted higher privileges. Apps using this attribute launch from a secure path, such as :
- %ProgramFiles% (including subdirectories)
- %ProgramFiles(x86)% (including subdirectories for 64-bit versions of Windows)
- %systemroot%\system32
- %systemroot%\syswow64 (for 64-bit versions of Windows)
If you have the Procmon monitoring tool installed in your device, you will observe that the application runs with the wrong integrity level, Integrity:Low instead of the expected Integrity:Medium. You are less likely to encounter this issue if you are running the application as an administrator.
Resolution:
This issue was resolved by Windows updates released November 12, 2024 (KB5046613), 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 November 12, 2024 (KB5046613), and 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 November 12, 2024, 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.
Group Policy downloads with Group Policy name:
- Download for Windows 10, version 22H2 – Windows 10 20H2, 21H1, 21H2 and 22H2 KB5041582 241027_11353 Known Issue Rollback
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: The below steps apply to enterprise devices that are domain joined.
- Wait for the KIR group policy changes to replicate in Active Directory and the SYSVOL
- Follow one of the steps below before applying the KIR:
- Wait for group policy to refresh in the background then restart your device (or)
- Run ‘gpupdate /force’ from a command prompt then restart your device
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
Azure Virtual Desktop users might experience black screen during login
| Status | Originating update | History |
|---|---|---|
| Resolved KB5045594 | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved: 2024-10-22, 10:00 PT Opened: 2024-10-14, 11:48 PT |
After installing the July 2024 non-security preview update (KB5040525), released July 23, 2024 or subsequent updates, you might experience a black screen when you login to Azure Virtual Desktop (AVD). You might also notice that you are unable to log out of your account and the black screen persists even after disconnecting and reconnecting to AVD. Resulting from this issue, the application event log in Event viewer will show an application error with Event ID:1000 indicating a fault with the application ‘svchost.exe_AppXSvc’.
Please note that AppX Deployment Service (AppxSvc) being in an invalid state could also cause other symptoms like the Start Menu to close unexpectedly due to registration issues.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Resolution:
This issue is resolved by installing the Windows updates released October 22, 2024 (KB5045594) or later updates and by applying one of the options mentioned in the Resolution section in KB5048864. Note that you need to perform both actions to resolve the issue.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
Click here to manage email notifications for Windows known issues.
August 2024
August 2024 security update might impact Linux boot in dual-boot setup devices
| Status | Originating update | History |
|---|---|---|
| Resolved KB5058379 | OS Build 19045.4780 KB5041580 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, (KB5041580) 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 (KB5058379), 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 KB5041580 | OS Build 19045.4651 KB5040427 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 (KB5040427), 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 (KB5041580), 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 (KB5041580) 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
CrowdStrike issue impacting Windows endpoints causing an error message
| Status | Originating update | History |
|---|---|---|
| Resolved External | N/A | Last updated: 2024-08-05, 16:07 PT Opened: 2024-07-19, 07:30 PT |
Microsoft has identified an issue impacting Windows endpoints which are running the CrowdStrike Falcon agent, developed by CrowdStrike Holdings. Following updates released and delivered by CrowdStrike on July 18, 2024, devices running the Falcon agent may encounter an error message on a blue screen and experience a continual restarting state.
Affected systems might restart repeatedly and require recovery operations in order to restore normal use.
Updated July 25, 2024: Microsoft released further guidance on Windows resiliency: Best practices and the path forward. Read more about how we are working in close cooperation to improve resiliency across the Windows ecosystem and explore best practices you can use to support resiliency in your organization.
Updated July 22, 2024: Microsoft has released a third mitigation option for this issue impacting Windows clients and servers. If devices are unable to recover with the two previous options mentioned below, IT admins can use PXE to remediate. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on prerequisites and configurations to use PXE Recovery.
Updated July 21, 2024: As a follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. Based on customer feedback, this new release includes a new option for recovery using safe boot, the option to generate ISO or USB, a fix for ADK detection when the Windows Driver Kit is installed, and a fix for the USB disk size check. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on using the signed Microsoft Recovery Tool.
Updated July 20, 2024: Microsoft has released KB5042426, which contains step-by-step guidance for Windows Servers hosted on-premises that are running the CrowdStrike Falcon agent and encountering a 0x50 or 0x7E error message on a blue screen. We will continue to work with CrowdStrike to provide the most up-to-date information available on this issue.
A new USB Recovery Tool is available to help IT admins expedite the repair process. The new tool can be found in the Microsoft Download Center. Read more about the new recovery tool and usage instructions at New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints.
Updated July 19, 2024: A new Knowledge Base article, KB5042421, with additional step-by-step guidance for Windows 11 and Windows 10 clients is now available. We will continue to work with CrowdStrike to provide up-to-date mitigation information as it becomes available.
To mitigate this issue ahead of additional resolution options, you can follow these steps:
- Start Windows into Safe Mode or the Windows Recovery Environment.
- Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
- Locate the file matching “C-00000291*.sys” and delete it.
- Restart the device.
- Recovery of systems requires a Bitlocker key in some cases.
For Windows Virtual Machines running on Azure follow the mitigation steps in Azure status.
Additional details from CrowdStrike are available here: Statement on Windows Sensor Update - CrowdStrike Blog.
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 LTSC 2019
- Server: Windows Server 2022; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
June 2024
Apps show "Open With" dialog when right-clicking on Taskbar or Start menu icons
| Status | Originating update | History |
|---|---|---|
| Resolved KB5039299 | OS Build 19045.4355 KB5036979 2024-04-23 | Resolved: 2024-06-25, 14:00 PT Opened: 2024-06-17, 09:45 PT |
Following installation of the Windows update released April 23, 2024 (KB5036979)and updates released after that, certain apps might display an "Open With" dialog box asking, "How do you want to open this file?". You might experience this issue when you place your mouse on an app icon shown in your Taskbar or Start menu and right-click on the app to execute a task in that app. Resulting from this, you might see the “Open With” dialog box instead of the execution of the selected task.
This issue was reported by Teams, new Outlook for Windows, and Snip & Sketch users. This issue can also affect other applications attempting to right-click on its icon to find a context menu with a list of tasks.
Workaround: Although the "Open With" dialog prevents the use of the tasks available from the right-click context menu, it's likely that those same operations can be performed by making the application interface visible, and navigating the application interface and menus.
Resolution: This issue was resolved in updates released June 25, 2024 (KB5039299) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2
- Server: None
April 2024
Enterprise customers might be unable to use Microsoft Connected Cache
| Status | Originating update | History |
|---|---|---|
| Resolved KB5040525 | OS Build 19045.3996 KB5034203 2024-01-23 | Resolved: 2024-07-23, 10:00 PT Opened: 2024-04-05, 11:09 PT |
After installing the February 2024 Windows security update (KB5034203), released February 13, 2024, or later updates, some Windows devices which use the DHCP Option 235 for discovery of Microsoft Connected Cache (MCC) nodes in their network might be unable to use the MCC nodes. Instead, these Windows devices will download updates and apps from the public internet and IT administrators would see increased download traffic on their internet routes.
Home users of Windows are unlikely to experience this issue, as Microsoft Connected Cache configured via DHCP Option 235 is more commonly used in enterprise environments.
Workaround:
- Option1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSource has to be set to 1 or removed as indicated in Cache hostname source. Note that by default, the DOCacheHost and DOCacheHostSource policies have no value.
- Option2: This issue can also be mitigated using Group Policies available through our support channel. Organizations can request help through Support for business.
Resolution: This issue was resolved by Windows updates released July 23, 2024 (KB5040525), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 10, version 21H2, Windows 10, version 22H2
- Server: None
November 2023
Desktop icons might move unexpectedly between monitors
| Status | Originating update | History |
|---|---|---|
| Resolved KB5039299 | OS Build 19045.3758 KB5032278 2023-11-30 | Resolved: 2024-06-25, 14:00 PT Opened: 2023-11-30, 17:09 PT |
Windows devices using more than one monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview).
To prevent users from encountering this issue, Copilot in Windows might not be available on devices that have been used or are currently being used in a multimonitor configuration. You might also not be able to update to Windows 11, version 23H2 as we have applied a compatibility hold on devices encountering this issue.
If your organization is using Windows Update for Business reports, the safeguard ID is 47615939.
Resolution: We are gradually rolling out a new Copilot experience for devices with Windows updates released June 25, 2024 (KB5039299) or later. This new experience will resolve this issue for Windows 10, version 22H2. This update (KB5039299) was released on June 25, 2024, and you can expect to receive the new Copilot experience between now and the coming months.
Safeguard Resolution: This issue was resolved on the service-side for Windows 11, version 23H2 and Windows 11, version 22H2 on devices with updates released January 9, 2024 or later. Non-managed consumer Windows devices with no other compatibility hold should now have Copilot for Windows available. The safeguard hold has been removed as of February 7, 2024. Eligible Windows 10 and Windows 11 devices with no other safeguards should now be able to upgrade to Windows 11, version 23H2. Please note, it can take up to 48 hours before the update to Windows 11, version 23H2 is offered. Restarting your device might help it offer faster. Note: Managed devices in your environment that have been used or are currently being used in a multimonitor configuration will not yet have Copilot for Windows available.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
- 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.