Windows 10, version 20H2 and Windows Server, version 20H2

Find information on known issues and the status of the rollout for Windows 10, version 20H2 and Windows Server, version 20H2. 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 May 10, 2022

As of May 10, 2022, the Home and Pro editions of Windows 10, version 20H2 have reached end of servicing. The May 2022 security update, released on May 10, is the last update available for these versions. After that date, devices running these editions will no longer receive monthly security and quality updates containing protections from the latest security threats. Education, Enterprise, and IoT Enterprise editions of Windows 10, version 20H2 will reach end of servicing May 9, 2023.
 
We recommend that you update your devices to the latest version of Windows 10, or upgrade eligible devices to Windows 11. For information about servicing timelines and lifecycle, see Windows 10 release informationWindows 11 release information, and Lifecycle FAQ - Windows.

    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
    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 19042.1706
    KB5013942
    2022-05-10
    Resolved
    2022-05-19
    19:24 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 19042.1682
    KB5011831
    2022-04-25
    Resolved
    KB5015020
    2022-05-19
    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 19042.1682
    KB5011831
    2022-04-25
    Resolved
    2022-05-10
    15:49 PT

    Issue details

    May 2022

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

    StatusOriginating updateHistory
    ResolvedOS Build 19042.1706
    KB5013942
    2022-05-10
    Resolved: 2022-05-19, 19:24 PT
    Opened: 2022-05-11, 18:38 PT

    After installing updates released May 10, 2022 on your domain controllers, you might see 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 Domain Controllers in your environment. There is no action needed on the client side to resolve this authentication issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. 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.

    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.

    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

    Microsoft Store apps might fail to install on some Windows devices

    StatusOriginating updateHistory
    Resolved KB5015020OS Build 19042.1682
    KB5011831
    2022-04-25
    Resolved: 2022-05-19, 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.

    Resolution: This issue was resolved in the out-of-band update KB5015020. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB5015020, search for it 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 CatalogNote KB5015020 is not available from Windows Update and will not install automatically.

    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
    ResolvedOS Build 19042.1682
    KB5011831
    2022-04-25
    Resolved: 2022-05-10, 15:49 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 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 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