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
    XPS documents with non-English language characters might not open
    XPS Viewer might be unable to open files with some non-English languages, including Japanese and Chinese.
    OS Build 22000.778
    KB5014668
    2022-06-23
    Confirmed
    2022-08-08
    17:58 PT
    Start menu might not open
    A small number of devices are unable to open the Start menu after installing updates released June 23, 2022 or later.
    OS Build 22000.778
    KB5014668
    2022-06-23
    Resolved
    2022-07-22
    15:51 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
    Resolved
    2022-07-19
    13:54 PT
    PowerShell Desired State Configuration resources might fail to apply successfully
    DSC resources in environments which require the PSCredential property might fail.
    OS Build 22000.739
    KB5014697
    2022-06-14
    Resolved
    KB5015814
    2022-07-12
    10:00 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

    August 2022

    XPS documents with non-English language characters might not open

    StatusOriginating updateHistory
    ConfirmedOS Build 22000.778
    KB5014668
    2022-06-23
    Last updated: 2022-08-08, 17:58 PT
    Opened: 2022-08-08, 17:58 PT

    After installing KB5014668 or later updates, XPS Viewer might be unable to open XML Paper Specification (XPS) documents in some non-English languages, including some Japanese and Chinese character encodings. This issue affects both XML Paper Specification (XPS) and Open XML Paper Specification (OXPS) files. When encountering this issue, you may receive an error, "This page cannot be displayed" within XPS Viewer or it might stop responding and have high CPU usage with continually increasing memory usage. When the error is encountered, if XPS Viewer is not closed it might reach up to 2.5GB of memory usage before closing unexpectedly.

    This issue does not affect most home users. The XPS Viewer is no longer installed by default as of Windows 10, version 1803 and must be manually installed.

    Next steps: We are working on a resolution 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
    • ​Server: Windows Server, version 20H2

    July 2022

    Start menu might not open

    StatusOriginating updateHistory
    ResolvedOS Build 22000.778
    KB5014668
    2022-06-23
    Resolved: 2022-07-22, 15:51 PT
    Opened: 2022-07-22, 15:33 PT

    After installing KB5014668 or later updates, we have received reports that a small number of devices might be unable to open the Start menu. On affected devices, clicking or selecting the Start button, or using the Windows key on your keyboard might have no effect.

    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 Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> KB5014668 220721_04201 Known Issue Rollback -> Windows 11 (original release). 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
    • ​Server: None

    PowerShell Desired State Configuration resources might fail to apply successfully

    StatusOriginating updateHistory
    Resolved KB5015814OS Build 22000.739
    KB5014697
    2022-06-14
    Resolved: 2022-07-12, 10:00 PT
    Opened: 2022-07-19, 17:55 PT

    After installing updates released June 14, 2022, or later ( KB5014697), PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to: “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”. Note: Environments which use non-encrypted PSCredential properties will not experience the issue.

    DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows.

    Resolution: This issue was resolved in KB5015814.

    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; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2016

    May 2022

    Some .NET Framework 3.5 apps might have issues

    StatusOriginating updateHistory
    ResolvedOS Build 22000.652
    KB5012643
    2022-04-25
    Resolved: 2022-07-19, 13:54 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
    

    Resolution: This issue should be resolved automatically via a Troubleshooter on affected unmanaged devices. If your device is managed by an IT department or with enterprise management tools, you might not get the troubleshooter automatically and might require the above workaround to resolve the issue. For more information on this troubleshooter, please see Windows Update Troubleshooter for repairing .NET Framework components.

    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