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 Enterprise LTSC 2021. 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 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 |
|---|---|---|---|
| Some devices might fail to shut down or hibernate This issue affects some Secure Launch-capable PCs with Virtual Secure Mode enabled after installing Jan '26 updates. | OS Build 19044.6809 KB5073724 2026-01-13 | Resolved | 2026-02-10 10:13 PT |
| Apps might become unresponsive when saving files to cloud-backed storage Affected apps include Outlook, which can become unresponsive when accessing PST files stored on Microsoft OneDrive. | OS Build 19044.6809 KB5073724 2026-01-13 | Resolved KB5078129 | 2026-01-23 14:00 PT |
| Connection and authentication failures in Azure Virtual Desktop and Windows 365 January 2026 Windows update causes Windows App credential prompt failures on Azure Virtual Desktop and Windows 365 | OS Build 19044.6809 KB5073724 2026-01-13 | Resolved KB5077796 | 2026-01-17 14:00 PT |
| Message Queuing (MSMQ) might fail with the December 2025 Windows security update This issue causes MSMQ operations to fail unless users are granted full administrative privileges on the system. | OS Build 19044.6691 KB5071546 2025-12-09 | Resolved KB5074976 | 2025-12-18 14:00 PT |
| An incorrect "End of Support" message might appear in Windows Settings Devices enrolled in the Extended Security Updates (ESU) program and LTSC 2021 editions will continue to receive updates. | OS Build 19044.6456 KB5066791 2025-10-14 | Resolved KB5068781 | 2025-11-11 10:00 PT |
| Non-admins might receive unexpected UAC prompts when doing MSI repair operations This issue can affect apps that use Windows Installer (MSI), such as Autodesk AutoCAD or Office Professional Plus 2010. | OS Build 19044.6216 KB5063709 2025-08-12 | Resolved KB5065429 | 2025-09-09 10:00 PT |
| Problems with NDI streaming performance after installing the August 2025 update Severe stuttering, lag, and choppy audio/video are reported on streaming apps, such as OBS and NDI Tools. | OS Build 19044.6216 KB5063709 2025-08-12 | Resolved KB5065429 | 2025-09-09 10:00 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 | Resolved KB5063523 | 2025-07-08 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 19044.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 19044.4780 KB5041580 2024-08-13 | Resolved KB5058379 | 2025-05-13 10:00 PT |
Issue details
January 2026
Some devices might fail to shut down or hibernate
| Status | Originating update | History |
|---|---|---|
| Resolved | OS Build 19044.6809 KB5073724 2026-01-13 | Resolved: 2026-02-10, 10:13 PT Opened: 2026-01-15, 18:33 PT |
After installing Windows updates released on or after January 13, 2026 (KB5073724), some Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled are unable to shut down or enter hibernation. Instead, the device restarts. This issue does not affect devices with AMD or ARM64 processors and is limited to the affected platforms listed below.
Resolution: This issue was resolved by Windows updates released February 10, 2026 (), and updates released after that date. 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 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2019
Apps might become unresponsive when saving files to cloud-backed storage
| Status | Originating update | History |
|---|---|---|
| Resolved KB5078129 | OS Build 19044.6809 KB5073724 2026-01-13 | Resolved: 2026-01-23, 14:00 PT Opened: 2026-01-20, 22:10 PT |
After installing Windows updates released on or after January 13, 2026 (KB5073724), some applications might become unresponsive or experience unexpected errors when opening files from or saving files to cloud-backed storage, such as OneDrive or Dropbox.
For example, in some configurations of Outlook that store PST files on OneDrive, Outlook might become unresponsive and fail to reopen unless its process is terminated in Task Manager, or the system is restarted. In addition, sent emails might not appear in the Sent Items folder, and previously downloaded emails might be downloaded again. The affected Outlook configurations primarily involve classic Outlook, which is commonly tied to enterprise licensing and is not included with most home installations of Windows. To check your Outlook configuration, see Feature comparison between new Outlook and classic Outlook.
Resolution:
This issue is resolved in the out-of-band (OOB) update KB5078129, released on January 24, 2026, and available via the Microsoft Update Catalog, as well as in updates released after this date. We recommend installing the latest update for your device, as it contains important improvements and issue resolutions, including this one.
Note: To download updates from the Microsoft Update Catalog, follow the steps described on this article.
For devices that have not yet installed the OOB update, there is an optional workaround for Outlook-specific scenarios. Moving the Outlook PST files out of OneDrive should resolve this issue. For guidance, please see documentation at How to remove an Outlook .pst data file from OneDrive. In addition, email accounts can still be accessed via webmail, if supported by your email provider.
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2025; Windows Server, version 23H2; Windows Server 2022; Windows Server 2019
Connection and authentication failures in Azure Virtual Desktop and Windows 365
| Status | Originating update | History |
|---|---|---|
| Resolved KB5077796 | OS Build 19044.6809 KB5073724 2026-01-13 | Resolved: 2026-01-17, 14:00 PT Opened: 2026-01-14, 00:52 PT |
After installing the January 2026 Windows security update (KB5073724), credential prompt failures might occur in some remote connection applications. This includes remote desktop connections using the Windows App on Windows client devices, on Azure Virtual Desktop and Windows 365. The Windows App is affected by this issue on specific Windows builds and can experience sign-in failures.
Other remote connections and related applications may be similarly impacted.
Resolution: To address this issue, an out-of-band (OOB) update was released January 17, 2026, in the Microsoft Update Catalog. It can be found as KB5077796.
If you have not yet deployed the January 2026 Windows security update and your IT environment includes the affected applications and features, we recommend applying this OOB update instead. For additional guidance, see How to download updates from the Microsoft Update Catalog. As always, we recommend you install the latest update for your device as it contains important improvements and issue resolutions including this one.
If the OOB is not installed, one of the following connection options can be used as a temporary workaround:
- Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (/previous-versions/remote-desktop-client/whats-new-windows?tabs=windows-msrdc-msi)
- Connect using the Windows App Web Client at windows.cloud.microsoft
Affected platforms:
- Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2, Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2025; Windows Server 2022; Windows Server 2019
December 2025
Message Queuing (MSMQ) might fail with the December 2025 Windows security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5074976 | OS Build 19044.6691 KB5071546 2025-12-09 | Resolved: 2025-12-18, 14:00 PT Opened: 2025-12-12, 17:13 PT |
After installing the December 2025 Windows security update (KB5071546), users might face issues with the Message Queuing (MSMQ) functionality. This issue also impacts clustered MSMQ environments under load. Due to this issue, users might encounter the following symptoms:
- MSMQ queues becoming inactive
- IIS sites failing with “Insufficient resources to perform operation” errors
- Applications unable to write to queues
- Errors such as "The message file 'C:\Windows\System32\msmq\storage*.mq' cannot be created” when creating message files
- Misleading logs like “There is insufficient disk space or memory", despite sufficient disk space and memory being available
This issue is caused by the recent changes introduced to the MSMQ security model and NTFS permissions on C:\Windows\System32\MSMQ\storage folder. MSMQ users now require write access to this folder, which is normally restricted to administrators. As a result, attempts to send messages via MSMQ APIs might fail with resource errors.
Individuals using Windows Home or Pro editions on personal devices are very unlikely to experience this issue. This issue primarily affects enterprise or managed IT environments.
Resolution: This issue was resolved by the Windows out-of-band update, released December 18, 2025 (KB5074976), which is available via the Microsoft Update Catalog, and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: To download updates from the Microsoft Update Catalog, follow the steps described on this article.
Affected versions:
- Client: Windows 10, version 22H2, Windows 10, version 21H2, Windows 10, version 1809, Windows 10, version 1607
- Server: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
November 2025
An incorrect "End of Support" message might appear in Windows Settings
| Status | Originating update | History |
|---|---|---|
| Resolved KB5068781 | OS Build 19044.6456 KB5066791 2025-10-14 | Resolved: 2025-11-11, 10:00 PT Opened: 2025-11-03, 10:53 PT |
The message, "Your version of Windows has reached the end of support", might incorrectly display in the Windows Update Settings page for the following OS versions:
- Windows 10, version 22H2 Pro, Education or Enterprise editions that are correctly enrolled in the Extended Security Updates (ESU) program and configured with an ESU product key
- Windows 10 Enterprise LTSC 2021
- Windows 10 IoT Enterprise LTSC 2021
The message might occur after installing Windows updates released on or after October 14, 2025 (KB5066791).
This issue only involves the incorrect display of the "end of support" message.
- Windows 10 devices that have an activated ESU license will continue to receive security updates.
- Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021 remain in support and will continue to receive security updates according to their respective lifecycles.
Resolution:
This issue was resolved by Windows updates released on November 11, 2025 (KB5068781), and updates released after that date. 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 updates released on or after November 11, 2025, (KB5068781), 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 11, 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 10, version 21H2 and 22H2 — KB5066791 251020_20401 Known Issue Rollback
The special Group Policy can be found in Computer Configuration > Administrative Templates > KB5066791 251020_20401 Known Issue Rollback > Windows 10, version 20H2, 21H1, 21H2 and 22H2. After installing the group policy, configure the KB5066791 251020_20401 Known Issue Rollback value to Disabled and restart your device(s) to apply the group policy setting. For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2
- Server: None
September 2025
Non-admins might receive unexpected UAC prompts when doing MSI repair operations
| Status | Originating update | History |
|---|---|---|
| Resolved KB5065429 | OS Build 19044.6216 KB5063709 2025-08-12 | Resolved: 2025-09-09, 10:00 PT Opened: 2025-09-03, 14:28 PT |
A security improvement was included in the August 2025 Windows security update (KB5063709) and later updates to enforce the requirement that User Account Control (UAC) prompt for administrator credentials when performing Windows Installer (MSI) repair and related operations. This improvement addressed security vulnerability CVE-2025-50173.
As a result, after installing the August 2025 Windows security update and later updates, UAC prompts for administrator rights can appear for standard users in the following scenarios:
- Running MSI repair commands (such as msiexec /fu).
- Launching Autodesk applications, including some versions of AutoCAD, Civil 3D and Inventor CAM, or when installing an MSI file after a user signs into the app for the first time.
- Installing applications that configure themselves per user.
- Running Windows Installer during Active Setup.
- Deploying packages via Manager Configuration Manager (ConfigMgr) that rely on user-specific "advertising" configurations.
- Enabling Secure Desktop.
If a standard user runs an app that initiates an MSI repair operation without displaying UI, it will fail with an error message. For example, installing and running Office Professional Plus 2010 as a standard user will fail with Error 1730 during the configuration process.
Resolution:
After installing the September 2025 Windows security update (KB5065429) or later updates, UAC prompts will only be required during MSI repair operations if the target MSI file contains an elevated custom action.
Since UAC prompts will still be required for apps that perform custom actions, after installing this update, IT admins will have access to a workaround to disable UAC prompts for specific apps by adding MSI files to an allowlist. For details, see the KB article: Unexpected UAC prompts when running MSI repair operations after installing the August 2025 Windows security update.
A Group Policy had previously been made available from Microsoft’s Support for business using Known Issue Rollback (KIR) to work around this issue. Organizations no longer need to install and configure this Group Policy to address this issue.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
August 2025
Problems with NDI streaming performance after installing the August 2025 update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5065429 | OS Build 19044.6216 KB5063709 2025-08-12 | Resolved: 2025-09-09, 10:00 PT Opened: 2025-08-21, 16:25 PT |
Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update (KB5063709). The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when "Display Capture" is enabled on the source PC. The problem persists even under low bandwidth conditions.
Resolution: This issue was resolved by Windows updates released September 9, 2025 (KB5065429), and updates released after that date. 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 September 9, 2025 (KB5065429) or later, you do not need to use a workaround for this issue. If you are using an update released before September 9, 2025, and have this issue, you have the option to apply the following workaround.
Workaround: NDI recommends manually changing the NDI Receive Mode to use TCP or UDP instead of RUDP.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 10, version 22H2; Windows 10, version 21H2
- Server: None
May 2025
Windows 10 might repeatedly display the BitLocker recovery screen at startup
| Status | Originating update | History |
|---|---|---|
| Resolved KB5061768 | OS Build 19044.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
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
August 2024
August 2024 security update might impact Linux boot in dual-boot setup devices
| Status | Originating update | History |
|---|---|---|
| Resolved KB5058379 | OS Build 19044.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
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.