Resolved issues in Windows 10, version 21H1

See a list of known issues that have been resolved for Windows 10, version 21H1 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate resolved
IE mode tabs in Microsoft Edge might stop responding
When a site is viewed in IE mode in Edge and the site uses certain calls, all IE mode tabs might stop responding.
OS Build 19043.1741
KB5014023
2022-06-02
Resolved
2022-06-24
19:42 PT
Microsoft Store apps might fail to install on some Windows devices
You might receive Error code: 0xC002001B when attempting to install apps from the Microsoft Store.
OS Build 19043.1682
KB5011831
2022-04-25
Resolved
KB5014023
2022-06-02
14:00 PT
Azure Active Directory and Microsoft 365 services might be unable to sign in
Windows Arm-based devices might have issues signing into some services after installing updates released June 14, 2022
OS Build 19043.1766
KB5014699
2022-06-14
Resolved
KB5016139
2022-06-20
14:00 PT
Some apps using Direct3D 9 might have issues on certain GPUs
You might have intermittent issues, apps might close unexpectedly, or you might receive an error.
OS Build 19043.1682
KB5011831
2022-04-25
Resolved
KB5014023
2022-06-02
14:00 PT
You might see authentication failures on the server or client for services
Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, and other services might fail.
OS Build 19043.1706
KB5013942
2022-05-10
Resolved
2022-05-27
14:24 PT
Some apps might render images outside the app's window or expected location
Apps using WebView2 to display content might render incorrectly, with some content rendering outside the app's window.
OS Build 19043.1620
KB5011543
2022-03-22
Resolved
2022-04-04
15:51 PT
Devices with certain Bluetooth pairings might receive error messages on a blue screen
Devices using the Bluetooth/ServicesAllowedList CSP Group Policy might receive an "IRQ NOT LESS OR EQUAL" error message.
OS Build 19043.1503
KB5009596
2022-01-25
Resolved
KB5011543
2022-03-22
14:00 PT
Files might persist after resetting a Windows device
Synced OneDrive files might not be deleted when selecting the Remove everything option when the device is reset.
OS Build 19043.1288
KB5006670
2021-10-12
Resolved
KB5011487
2022-03-08
10:00 PT
The text cursor in some apps might move unexpectedly when using a Japanese IME
Text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly.
OS Build 19043.1387
KB5007253
2021-11-22
Resolved
KB5009543
2022-01-11
10:00 PT
Outlook search might not locate recent emails
Searches on Outlook desktop app might fail when emails are stored locally in PST or OST files
OS Build 19043.1387
KB5007253
2021-11-22
Resolved
KB5010342
2022-02-08
10:00 PT
Certain IPSEC connections might fail
Some VPN clients using IPSEC or Layer 2 Tunneling Protocol (L2TP) might have issues connecting.
OS Build 19043.1466
KB5009543
2022-01-11
Resolved
KB5010793
2022-01-17
14:00 PT

Issue details

June 2022

IE mode tabs in Microsoft Edge might stop responding

StatusOriginating updateHistory
ResolvedOS Build 19043.1741
KB5014023
2022-06-02
Resolved: 2022-06-24, 19:42 PT
Opened: 2022-06-24, 19:21 PT

After installing KB5014023 and later updates, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box which requires the user to respond before continuing or interacting with other portions of the webpage or app. Developer Note: Sites affected by this issue call window.focus.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring the special Group Policy 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:

Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: Windows Server 2022

Azure Active Directory and Microsoft 365 services might be unable to sign in

StatusOriginating updateHistory
Resolved KB5016139OS Build 19043.1766
KB5014699
2022-06-14
Resolved: 2022-06-20, 14:00 PT
Opened: 2022-06-17, 09:56 PT

After installing KB5014699 on a Windows Arm-based devices, you might be unable to sign in using Azure Active Directory (AAD). Apps and services which use Azure Active Directory to sign in, might also be affected. Some scenarios which might be affected are VPN connections, Microsoft Teams, OneDrive, and Outlook. Note: This issue only affects Windows devices which are using Arm processors.

Workaround: To mitigate the issue, you can use the web versions of the affected apps, such as OneDrive, Microsoft Teams and Outlook.com.

Resolution: This issue was resolved in the out-of-band security update KB5016139, released June 20, 2022. This update is available only for Arm-based Windows devices. This update is not needed for x86-based or x64-based devices using AMD or Intel CPUs, so it is not available for those architectures. It is available via Windows Update, Windows Update for Business, Windows Server Update Services (WSUS) and Microsoft Update Catalog. It is a cumulative update, so you do not need to apply any previous update before installing it. If you would like to install the update before it is installed automatically, you will need to Check for updates. To get the standalone package for KB5016139, search for it in the Microsoft Update Catalog.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: None

May 2022

Microsoft Store apps might fail to install on some Windows devices

StatusOriginating updateHistory
Resolved KB5014023OS Build 19043.1682
KB5011831
2022-04-25
Resolved: 2022-06-02, 14:00 PT
Opened: 2022-05-19, 12:53 PT

After installing KB5011831 or later updates, you might receive an error code: 0xC002001B when attempting to install from the Microsoft Store. Some Microsoft Store apps might also fail to open. Affected Windows devices use a processor (CPU) which supports Control-flow Enforcement Technology (CET), such as such as 11th Gen and later Intel® Core™ Processors or later and certain AMD processors.

This issue can also affect devices registered in the Autopilot deployment process, which is commonly used to deploy and maintain devices in corporate environments. Profiles can fail to be applied to the device, resulting in settings not being configured correctly.

Resolution: This issue was resolved in updates released June 2, 2022 ( KB5014023) and later. We recommend you install the latest security update for your device.

Affected platforms:

  • ​Client: Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: None

Some apps using Direct3D 9 might have issues on certain GPUs

StatusOriginating updateHistory
Resolved KB5014023OS Build 19043.1682
KB5011831
2022-04-25
Resolved: 2022-06-02, 14:00 PT
Opened: 2022-05-10, 09:41 PT

After installing KB5011831, Windows devices using certain GPUs might have apps close unexpectedly or intermittent issues with some apps which use Direct3D 9. You might also receive an error in Event Log in Windows Logs/Applications with faulting module d3d9on12.dll and exception code 0xc0000094.

Resolution: This issue was resolved in updates released June 2, 2022 ( KB5014023) and later. We recommend you install the latest security update for your device. It contains important improvements and issues resolutions, including this one. If you install an update released June 2, 2022 ( KB5014023) 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 June 2, 2022, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback.

Group Policy downloads with Group Policy name:

Important: You will need to install and configure Group Policies to resolve this issue. Please see, How to use Group Policy to deploy a Known Issue Rollback.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: None

You might see authentication failures on the server or client for services

StatusOriginating updateHistory
ResolvedOS Build 19043.1706
KB5013942
2022-05-10
Resolved: 2022-05-27, 14:24 PT
Opened: 2022-05-11, 18:38 PT

Resolution guidance updated May 27, 2022

After installing updates released May 10, 2022 on your domain controllers, you might see machine certificate authentication failures on the server or client for services such as Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, Extensible Authentication Protocol (EAP), and Protected Extensible Authentication Protocol (PEAP). An issue has been found related to how the mapping of certificates to machine accounts is being handled by the domain controller.

Note: Installation of updates released May 10, 2022, on client Windows devices and non-domain controller Windows Servers will not cause this issue. This issue only affects installation of May 10, 2022, updates installed on servers used as domain controllers.

Workaround: The preferred mitigation for this issue is to manually map certificates to a machine account in Active Directory. For instructions, please see Certificate Mapping. Note: The instructions are the same for mapping certificates to user or machine accounts in Active Directory. If the preferred mitigation will not work in your environment, please see KB5014754—Certificate-based authentication changes on Windows domain controllers for other possible mitigations in the SChannel registry key section. Note: Any other mitigation except the preferred mitigations might lower or disable security hardening.

Resolution: This issue was resolved in out-of-band updates released May 19, 2022 for installation on all Domain Controllers in your environment, as well as all intermediary application servers such as Network Policy Servers (NPS), RADIUS, Certification Authority (CA), or web servers which passes the authentication certificate from the client being authenticated to the authenticating DC. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. This includes the removal of the registry key (CertificateMappingMethods = 0x1F) documented in the SChannel registry key section of KB5014754. There is no action needed on the client side to resolve this authentication issue.

To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically.

Cumulative updates:

Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released May 10, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

Standalone Updates:

Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of May 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released May 10, 2022 to receive the quality updates for May 2022. If you have already installed updates released May 10, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

April 2022

Some apps might render images outside the app's window or expected location

StatusOriginating updateHistory
ResolvedOS Build 19043.1620
KB5011543
2022-03-22
Resolved: 2022-04-04, 15:51 PT
Opened: 2022-04-04, 12:03 PT

After installing KB5011543, some apps might render content incorrectly or outside of the app's window. Affected apps are using WebView2 to render content generated locally or downloaded from the internet.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring a special Group Policies listed below. Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy downloads with Group Policy name:

Important: You will need to install and configure the Group Policies specific to your version of Windows to resolve this issue.

To configure the special Group Policy use the following steps:

  1. ​If the KIR Group Policy has not been installed, install it from the link above.
  2. ​Open Group Policy Editor, navigate to either Local Computer Policy or the Domain policy on your domain controller then: Administrative Templates -> <Name as listed above>, then select the version of Windows you want to use this group policy on. Note: You might need to select the Windows 10 version that use the same update as a version of Server you are using. For example, you might need to select Windows 10, version 1809 if you are using Windows Server 2019.
  3. ​Set it to, "Disabled".
  4. ​If you are setting this on a domain controller, you will need to wait for the Group Policy to replicate group policy changes in Active Directory and the SYSVOL.
  5. ​Devices applying a KIR GP in local or domain policy must either apply a background or manual group policy refresh.
  6. ​Restart the affected device. Note: You should not need to restart the domain controller after installing this KIR Group Policy.
  7. ​Allow Group Policy to refresh on affected devices before installing the affected Windows update.

For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback.

Affected platforms:

  • ​Client: Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: Windows Server 2022

March 2022

Devices with certain Bluetooth pairings might receive error messages on a blue screen

StatusOriginating updateHistory
Resolved KB5011543OS Build 19043.1503
KB5009596
2022-01-25
Resolved: 2022-03-22, 14:00 PT
Opened: 2022-03-11, 10:18 PT

After installing KB5009596 or later updates, some organizations which have Windows devices paired to Bluetooth devices might receive an error message "Your device ran into a problem and needs to restart." with a blue screen and "Stop code: IRQ NOT LESS OR EQUAL". The error logged on affected devices will be in the System log in Event Viewer and will be logged as "Microsoft-Windows-WER-SystemErrorRe event 1001" with text "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a ". This issue is observed when certain Configuration service provider (CSP) policies are in place which affect the Bluetooth A2dp profile. It can be observed from one of two scenarios:

  • ​ During the restart at the end of the update installation process, if the Windows client device was previously paired with mobile phones or with other audio devices via Bluetooth.
  • ​After updates are installed, at the moment users pair their updated Windows client device with a new mobile phone or audio device via Bluetooth.

This update might show in Windows Update history section of the settings app as "Failed to install on <date> - 0x800f0845" after it has been rolled back due to starting up to an error after installation.

CSP policies are not common outside of enterprise environments, for which this issue is not common for home users and personal devices.

Workaround: To mitigate this issue, IT administrators using Intune or other tools can modify the Windows registry before installing this update following the steps below:

  1. ​Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Bluetooth\ 
  2. ​Add the following registry entry: {0000110a-0000-1000-8000-00805f9b34fb} and {0000110b-0000-1000-8000-00805f9b34fb} to the ServicesAllowedList value

Note: If you have already installed the update and the blue screen error message shows up during the device's restart, please launch Windows in Safe mode to add the registry entry.

Important: This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows.

Resolution: This issue was resolved in updates released March 22, 2022 ( KB5011543) and later. We recommend you install the latest security update for your device. It contains important improvements and issues resolutions, including this one. If you install an update released March 22, 2022 ( KB5011543) 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 22, 2022, you can resolve this issue using KIR. This KIR will not propagate to devices automatically. Devices that have installed an affected update and encountered this issue can resolve it by installing and configuring a special Group Policy which can be downloaded here. To configure the special Group Policy use the following steps:

  1. ​If the KIR Group Policy has not been installed, install it from the download here.
  2. ​Open Group Policy Editor, navigate to either Local Computer Policy or the Domain policy on your domain controller then: Administrative Templates -> KB5009596 Issue 001 Rollback -> Windows 10, version 2004 20H2 and 21H1
  3. ​Set it to, "Disabled".
  4. ​Restart the affected device. Note: If you are setting this on a domain controller, you will need to wait for the Group Policy to propagate and then restart the affected devices. You should not need to restart the domain controller after installing this KIR Group Policy.
  5. ​Allow Group Policy to refresh on affected devices before installing the affected Windows update.

For more information on deployment, please see How to use Group Policy to deploy a Known Issue Rollback.

Affected platforms:

  • ​Client: Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: none

February 2022

Files might persist after resetting a Windows device

StatusOriginating updateHistory
Resolved KB5011487OS Build 19043.1288
KB5006670
2021-10-12
Resolved: 2022-03-08, 10:00 PT
Opened: 2022-02-24, 17:28 PT

When attempting to reset a Windows device with apps which have folders with reparse data, such as OneDrive or OneDrive for Business, files which have been downloaded or synced locally from OneDrive might not be deleted when selecting the “Remove everything” option. This issue might be encountered when attempting a manual reset initiated within Windows or a remote reset. Remote resets might be initiated from Mobile Device Management (MDM) or other management applications, such as Microsoft Intune or third-party tools. OneDrive files which are “cloud only” or have not been downloaded or opened on the device are not affected and will not persist, as the files are not downloaded or synced locally. Note: Some device manufacturers and some documentation might call the feature to reset your device, "Push Button Reset", "PBR", "Reset This PC", "Reset PC", or "Fresh Start".

Workaround: To mitigate this issue, you can do the following:

Resolution: This issue was resolved in KB5011487. Some devices might take up to 7 days after the installation of KB5011487 to resolve the issue and prevent files from persisting after reset. For immediate resolution, you can manually trigger Windows Update Troubleshooter using the instructions in Windows Update Troubleshooter. If you are part of an organization that manages devices or prepared OS images for deployment, you can also resolve this issue by applying a compatibility update for installing and recovering Windows, which makes improvements to the "safe operating system" (SafeOS) that is used to update the Windows recovery environment (WinRE). You can deploy these updates using the instructions in, "Add an update package to Windows RE" using KB5012414 for Windows 11, version 21H2 and KB5012419 for Windows 10, version 21H2, Windows 10, version 21H1, and Windows 10, version 20H2. 

Important: Devices which have already been reset and OneDrive files have persisted will require the workaround above or another reset after applying one of the resolutions above. 

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2

January 2022

The text cursor in some apps might move unexpectedly when using a Japanese IME

StatusOriginating updateHistory
Resolved KB5009543OS Build 19043.1387
KB5007253
2021-11-22
Resolved: 2022-01-11, 10:00 PT
Opened: 2022-01-04, 17:29 PT

After installing KB5007253, text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly in apps that use the multibyte character set (MBCS). This issue affects both the Microsoft Japanese IME and third-party Japanese IMEs.

Resolution: This issue was resolved in updates released January 11, 2022 ( KB5009543) and later. We recommend you install the latest security update for your device. Currently, the latest security update was released on February 8, 2022 and is the recommended option. It contains important improvements and issues resolutions, including this one. If you install an update released January 11, 2022 ( KB5009543) 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 January 11, 2022, you can resolve this issue using KIR. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy (preferred). Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy:

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: Windows Server 2022

Outlook search might not locate recent emails

StatusOriginating updateHistory
Resolved KB5010342OS Build 19043.1387
KB5007253
2021-11-22
Resolved: 2022-02-08, 10:00 PT
Opened: 2022-01-19, 15:40 PT

Recent emails might not appear in search results on Outlook desktop app on Windows 11. This issue is related to emails which have been stored locally in a PST or OST files. It might affect POP and IMAP accounts, as well as Microsoft Exchange and Microsoft 365 hosted accounts. If the default search in the Outlook app is set to server search, the issue will only affect the advanced search.

Workaround: To mitigate the issue, you can disable Windows Desktop Search which will cause Outlook to use its built-in search. For instructions, see Outlook Search not showing recent emails after Windows update KB5008212.

Resolution: This issue was resolved in KB5010342, released February 8, 2022. If you install an update released February 8, 2022 ( KB5010342) 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 February 8, 2022, you can resolve this issue using KIR. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy for KIR:

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • ​Server: Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019

Certain IPSEC connections might fail

StatusOriginating updateHistory
Resolved KB5010793OS Build 19043.1466
KB5009543
2022-01-11
Resolved: 2022-01-17, 14:00 PT
Opened: 2022-01-13, 11:05 PT

After installing KB5009543, IP Security (IPSEC) connections which contain a Vendor ID might fail. VPN connections using Layer 2 Tunneling Protocol (L2TP) or IP security Internet Key Exchange (IPSEC IKE) might also be affected.

Workaround: To mitigate the issue for some VPNs, you can disable Vendor ID within the server-side settings. Note: Not all VPN servers have the option to disable Vendor ID from being used.

Resolution: This issue was resolved in the out-of-band update KB5010793. It is a cumulative update, so you do not need to apply any previous update before installing it. If you would like to install the update, you will need to Check for updates and select "Optional updates" and then select KB5010793. To get the standalone package for KB5010793, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5010793 will not install automatically.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1909; 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 2019; Windows Server 2016