Resolved issues in Windows 10 Enterprise LTSC 2021
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 |
|---|---|---|---|
| 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 19044.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 |
| Devices with locale set to Croatia might not utilize the expected currency This can affect applications which retrieve the device's currency for purchases or other transactions | N/A | Resolved KB5037768 | 2024-05-14 10: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 19044.4412 KB5037768 2024-05-14 | Resolved KB5040427 | 2024-07-09 10:00 PT |
| VPN connections might fail after installing the April 2024 security update We are investigating user reports, and we will provide more information in the coming days | OS Build 19044.4291 KB5036892 2024-04-09 | Resolved KB5037768 | 2024-05-14 10:00 PT |
| The January 2024 Windows RE update might fail to install WinRE is the Windows Recovery Environment. The update fails if there's insufficient free space in the WinRE partition. | N/A KB5034441 2024-01-09 | Resolved | 2024-04-30 14:07 PT |
| BitLocker might incorrectly receive a 65000 error in MDMs "Requires Device Encryption" might incorrectly report as an error in some managed environments. | N/A | Resolved KB5034763 | 2024-02-13 10:00 PT |
| Printer names and icons might be changed and HP Smart app automatically installs In most cases, it is possible to use the printer for printing jobs and other features such as copy, scan, or fax. | N/A | Resolved | 2023-12-22 15:53 PT |
| The October 2023 security update might fail to install Some Windows 10 devices might initially display progress, but then fail to complete. | OS Build 19044.3570 KB5031356 2023-10-10 | Resolved KB5032189 | 2023-11-14 10:00 PT |
| Apps deployed via ClickOnce might prompt for installation when opened Apps which were deployed using ClickOnce might begin to prompt for installation even though they're already installed. | OS Build 19044.3324 KB5029244 2023-08-08 | Resolved KB5031356 | 2023-10-10 10:00 PT |
Issue details
July 2024
Devices might boot into BitLocker recovery with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5041580 | OS Build 19044.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 KB5040427 | OS Build 19044.4412 KB5037768 2024-05-14 | Resolved: 2024-07-09, 10:00 PT Opened: 2024-06-17, 09:45 PT |
Following installation of the Windows update released April 23, 2024 (KB5037768)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 July 9, 2024 (KB5040427) 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
VPN connections might fail after installing the April 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5037768 | OS Build 19044.4291 KB5036892 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:15 PT |
Windows devices might face VPN connection failures after installing the April 2024 security update (KB5036892) or the April 2024 non-security preview update.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037768), 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 11, version 23H2; Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2, Windows 10, version 21H2.
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
January 2024
The January 2024 Windows RE update might fail to install
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A KB5034441 2024-01-09 | Resolved: 2024-04-30, 14:07 PT Opened: 2024-01-12, 14:10 PT |
Devices attempting to install the January 2024 Windows Recovery Environment update (KB5034441) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.
Resulting from this error, the following message might be displayed.
- "0x80070643 - ERROR_INSTALL_FAILURE"
Important: If your Windows device does not have a recovery environment configured, you do not need this update (KB5034441). In this case, the error can be ignored.
To determine whether your device has a recovery environment configured, inspect the WinRE status by following these steps:
- Open a Command Prompt window (cmd) as admin.
- To check the WinRE status, run reagentc /info. If the WinRE is configured, a "Windows RE status" field will appear in the output, with value "Enabled". If WinRE is not configured, this field will have the value "Disabled".
Resolution: Automatic resolution of this issue won't be available in a future Windows update. Manual steps are necessary to complete the installation of this update on devices which are experiencing this error.
The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action. For guidance on making this change, review the following resources:
- A code script can be used to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE. See Extend the Windows RE Partition.
- Guidance to manually change the WinRE partition size can additionally be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.
Completion of these manual steps will allow the installation of this update to succeed.
Affected platforms:
- Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2
- Server: Windows Server 2022
December 2023
Printer names and icons might be changed and HP Smart app automatically installs
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2023-12-22, 15:53 PT Opened: 2023-12-04, 18:46 PT |
Some issues related to printer configurations are being observed on Windows devices. Microsoft is investigating this issue and coordinating with partners on a solution.
Symptoms can include the following:
- Some Windows devices are installing the HP Smart app.
- Printers may show LaserJet M101-M106 model information regardless of their manufacturer. Printer icons might also be changed.
- Double clicking on a printer displays the on-screen error "No tasks are available for this page".
Note: Our investigations indicate that this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work.
Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool – December 2023. In addition to this tool, a critical troubleshooter is being gradually rolled out to all affected Home and non-managed business devices. Critical troubleshooting happens automatically in the background and won’t get in the way of using your device. To learn more about critical and recommended troubleshooters, see Keep your device running smoothly with recommended troubleshooting.
If you need support to resolve this issue, go to https://support.microsoft.com/contactus, and select 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, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
- Server: Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
October 2023
BitLocker might incorrectly receive a 65000 error in MDMs
| Status | Originating update | History |
|---|---|---|
| Resolved KB5034763 | N/A | Resolved: 2024-02-13, 10:00 PT Opened: 2023-10-09, 14:51 PT |
Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.
Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured.
Resolution: This issue was resolved by Windows updates released February 13, 2024 (KB5034763), 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 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
- Server: None
The October 2023 security update might fail to install
| Status | Originating update | History |
|---|---|---|
| Resolved KB5032189 | OS Build 19044.3570 KB5031356 2023-10-10 | Resolved: 2023-11-14, 10:00 PT Opened: 2023-10-13, 10:33 PT |
Microsoft has received reports of an issue where Windows updates released October 10, 2023 (KB5031356) fail to install. Devices might initially display progress, but then fail to complete installation.
Based on our reports, some of the most common errors being encountered is Error 8007000D (ERROR_INVALID_DATA). This error can be found from the Windows Update view under System settings, by selecting Update History.
For additional guidance on quality update install errors, see Troubleshoot problems updating Windows.
Resolution: This issue was resolved in updates released November 14, 2023 (KB5032189) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released November 14, 2023 or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue.
If necessary, the following manual steps can be used to speed up the recovery:
- Run command Prompt as Administrator. To do this, you can open the Start menu and type 'cmd'. From the right-side panel of the search results, select the option 'Run as administrator'
- In the window that opens, type the following to execute a restore command: Dism /online /cleanup-image /RestoreHealth
- Wait for it to complete successfully, then close the windows. You can now search for updates again from the Windows Updates from the Settings view.
The Windows Updates settings view can always be found by opening the Start menu and typing 'Windows Updates'. Then select 'Check for updates' from the search results.
If you are using an update released before November 14, 2023 (KB5032189), and have this issue, you 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 and Windows 10, version 21H2 - Windows 10 21H2 and 22H2 KB5026879 230627_173533 Known Issue Rollback.msi
Please note that it might take up to 48 hours for the resolution to propagate automatically to consumer devices and non-managed business devices.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2
August 2023
Apps deployed via ClickOnce might prompt for installation when opened
| Status | Originating update | History |
|---|---|---|
| Resolved KB5031356 | OS Build 19044.3324 KB5029244 2023-08-08 | Resolved: 2023-10-10, 10:00 PT Opened: 2023-08-13, 18:39 PT |
After installing KB5029244 or later updates, apps which were deployed using ClickOnce might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”.
Workaround: To temporarily workaround the issue, uninstall the impacted ClickOnce Application and reinstall the application again.
Resolution: This issue was resolved in updates released October 10, 2023 (KB5031356) and later. After installing KB5031356 or later updates, 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 October 10, 2023, and have this issue, you 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, version 21H2 - Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_03351 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2
- Server: None
February 2023
Devices with locale set to Croatia might not utilize the expected currency
| Status | Originating update | History |
|---|---|---|
| Resolved KB5037768 | N/A | Resolved: 2024-05-14, 10:00 PT Opened: 2023-02-23, 13:22 PT |
The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device's currency for purchases or other transactions.
Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.
Workaround: Changing the currency in Windows can help. This can be accomplished via the Windows Control Panel.
- Open the "Windows Region" settings. This can be done in one of the following ways:
- Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
- On your keyboard, press and hold the Windows key, then press the letter R. This will open the "Run" window. Type INTL.CPL into the Open field,
- In the Region settings, choose one of the 2 locales for Croatia:
- Croatian (Bosnia & Herzegovina)
- Croatian (Croatia)
- In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
- Change the currency symbol from "KN" to Euro, "€"
Additional information can be seen here: Currency formatting - Globalization | Microsoft Learn.
Manually changing currency might also be an option in some applications. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Some applications might not allow this manual change. Please view the settings and documentation for your applications.
Resolution: This issue was resolved in updates released May 14, 2024 (KB5037768) and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; 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 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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.