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 10, 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.
Current status as of May 2, 2025
On October 14, 2025, Windows 10 will reach end of support*. After this date, devices running Windows 10 will no longer receive fixes for known issues, time zone updates, technical support, or monthly security and preview updates containing protection from the latest security threats.
See our blog post to help you prepare for Windows 10 end of support and options for moving to Windows 11. The options include:
- Check if your current Windows 10 PC can upgrade to Windows 11.
- Purchase a new Windows 11 PC.
- Purchase Extended Security Updates (ESU) for organizations of all sizes as previously announced in April 2024.
- For the first time, purchase an ESU option for individuals.
*Note: Long-Term Servicing Branch (LTSB) and Long-Term Servicing Channel (LTSC) releases are subject to different lifecycle support policies. Check out the Microsoft lifecycle website for more information.
To learn about Windows 10 servicing timelines and lifecycle, see Windows 10 release information and Lifecycle FAQ - Windows.
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 |
|---|---|---|---|
| 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 | Mitigated | 2025-06-17 16:39 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:04 PT |
| 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 | Mitigated | 2025-04-21 16:44 PT |
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 19045.5965 KB5060533 2025-06-10 | Last updated: 2025-06-17, 16:39 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.
Workaround: 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.
While recovery steps are being prepared for the Surface Hub v1 devices that are unable to start, you can continue using the Hub's screen and collaboration tools through two supported fallback modes:
- Guest Mode – Allows a connected external PC to use the Surface Hub’s screen, touch + pen input, and speakers.
- Replacement PC Mode – Offers the same features as Guest Mode, but also enables access to the cameras and microphones, ideal for Teams or Zoom meetings.
You can learn more about using external inputs at Surface Hub: Connect and Display with Guest or Replacement PC Mode.
Next steps: Resolution steps to recover the limited number of Surface Hub v1 devices that were impacted by this issue and are unable to start will be provided in the coming days.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
| 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
| Status | Originating update | History |
|---|---|---|
| Mitigated | N/A KB5057589 2025-04-08 | Last updated: 2025-04-21, 16:44 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:
If you install KB5057589 after 2 PM PT on April 21, 2025, you will not observe the incorrect error message about the install failure. If you have already installed this update, you will not see this update offered again and can check the status of this update with the Dism /Online /Get-Packages command.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2
- Server: Windows Server 2022
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.