Windows 10, version 21H1

Find information on known issues and the status of the rollout for Windows 10, version 21H1. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

Current status as of November 3, 2021
Windows 10, version 21H1 is designated for broad deployment. As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For more details, see How to get the Windows 10 May 2021 Update

    Known issues

    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusLast updated
    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
    Unable to connect to internet when using Wi-Fi hotspot feature
    After installing updates released June 14, 2022, you might have issues using Wi-Fi hotspot on Windows device.
    OS Build 19043.1766
    KB5014699
    2022-06-14
    Investigating
    2022-06-20
    14:47 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

    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

    Unable to connect to internet when using Wi-Fi hotspot feature

    StatusOriginating updateHistory
    InvestigatingOS Build 19043.1766
    KB5014699
    2022-06-14
    Last updated: 2022-06-20, 14:47 PT
    Opened: 2022-06-16, 14:12 PT

    After installing KB5014699, Windows devices might be unable to use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects.

    Workaround: To mitigate the issue and restore internet access on the host device, you can disable the Wi-Fi hotspot feature. For instructions, please see Use your Windows PC as a mobile hotspot.

    Next steps: We are presently investigating and will provide an update in an upcoming release.

    Affected platforms:

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

    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