Windows 11 known issues and notifications

Find information on known issues and the status of the rollout for Windows 11. 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 17, 2022 (PT)

Windows 11 is designated for broad deployment.

If you are using Windows 10, you can determine if your device is eligible for the upgrade using the PC Health Check app or checking Windows 11 specs, features, and computer requirements. Note that you also need to be running Windows 10, version 2004 or later, and have no safeguard holds applied to your device. We encourage the use of a Microsoft Account (MSA) to get the most out of your Windows 11 experience. 

For more information on the Windows 11 upgrade experience, watch our video, Windows 11 Upgrade Experience.

    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 22000.708
    KB5014019
    2022-05-24
    Resolved
    2022-06-24
    19:42 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 22000.739
    KB5014697
    2022-06-14
    Resolved
    KB5014668
    2022-06-23
    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 22000.739
    KB5014697
    2022-06-14
    Resolved
    KB5016138
    2022-06-20
    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 22000.675
    KB5013943
    2022-05-10
    Resolved
    2022-05-27
    14:24 PT
    Some .NET Framework 3.5 apps might have issues
    Apps using optional components such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) might fail.
    OS Build 22000.652
    KB5012643
    2022-04-25
    Mitigated
    2022-05-10
    16:57 PT
    Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
    Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen.
    N/A

    Mitigated External
    2021-11-15
    18:20 PT

    Issue details

    June 2022

    IE mode tabs in Microsoft Edge might stop responding

    StatusOriginating updateHistory
    ResolvedOS Build 22000.708
    KB5014019
    2022-05-24
    Resolved: 2022-06-24, 19:42 PT
    Opened: 2022-06-24, 19:21 PT

    After installing KB5014019 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

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

    StatusOriginating updateHistory
    Resolved KB5014668OS Build 22000.739
    KB5014697
    2022-06-14
    Resolved: 2022-06-23, 14:00 PT
    Opened: 2022-06-16, 14:12 PT

    After installing KB5014697, 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.

    Resolution: This issue was resolved in KB5014668.

    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

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

    StatusOriginating updateHistory
    Resolved KB5016138OS Build 22000.739
    KB5014697
    2022-06-14
    Resolved: 2022-06-20, 14:00 PT
    Opened: 2022-06-17, 09:56 PT

    After installing KB5014697 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 KB5016138, 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 KB5016138, 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

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

    StatusOriginating updateHistory
    ResolvedOS Build 22000.675
    KB5013943
    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

    Some .NET Framework 3.5 apps might have issues

    StatusOriginating updateHistory
    MitigatedOS Build 22000.652
    KB5012643
    2022-04-25
    Last updated: 2022-05-10, 16:57 PT
    Opened: 2022-05-03, 13:20 PT

    After installing KB5012643, some .NET Framework 3.5 apps might have issues or might fail to open. Affected apps are using certain optional components in .NET Framework 3.5, such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) components.

    Workaround: You can mitigate this issue by re-enabling .NET Framework 3.5 and the Windows Communication Foundation in Windows Features. For instructions, please see Enable the .NET Framework 3.5 in Control Panel. Advanced users or IT admins can do this programmatically using an elevated Command Prompt (run as administrator) and running the following commands:

    dism /online /enable-feature /featurename:netfx3 /all
    dism /online /enable-feature /featurename:WCF-HTTP-Activation
    dism /online /enable-feature /featurename:WCF-NonHTTP-Activation
    

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 21H2
    • ​Server: None

    November 2021

    Compatibility issues with Intel Smart Sound Technology drivers and Windows 11

    StatusOriginating updateHistory
    Mitigated ExternalN/A

    Last updated: 2021-11-15, 18:20 PT
    Opened: 2021-11-15, 16:40 PT

    Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) and Windows 11. Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. The affected driver will be named Intel® Smart Sound Technology (Intel® SST) Audio Controller under System Devices in Device Manager and have the file name IntcAudioBus.sys and a file version of 10.29.0.5152 and earlier or 10.30.0.5152 and earlier.

    To safeguard your upgrade experience, we have applied a compatibility hold on devices with affected Intel SST drivers from being offered Windows 11. If your organization is using Update Compliance, the safeguard ID is 36899911.

    Workaround: To mitigate the safeguard, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. This issue is resolved by updating the Intel® Smart Sound Technology drivers to a version 10.30.00.5714 and later or 10.29.00.5714 and later. Important: Later versions refer to just the last part of the version number. For addressing this issue, 10.30.x versions are not newer than 10.29.x versions. Once you have updated to a compatible version of the Intel® Smart Sound Technology drivers, you should be able to upgrade to Windows 11. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered.

    Next Steps: If you encounter this safeguard hold and an updated driver is not yet available, you will need to contact your device manufacturer (OEM) for more information.

    Note We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. 

    Affected platforms:

    • ​Client: Windows 11, version 21H2