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 November 16, 2021 (PT)

In our first phases of the Windows 11 rollout we are consistently seeing a high rate of positive update experiences and user feedback for eligible devices, identified using our latest generation machine learning model. Based on this data, we are advancing the pace of the rollout faster than we originally announced, and now making the Windows 11 upgrade more broadly available to eligible Windows 10 devices. We recommend that you upgrade your devices to Windows 11 to take advantage of the latest features and advanced protections from security threats. We will continue to train our machine learning model throughout the phased rollout to deliver a smooth upgrade experience. We will also provide status updates as we further increase availability over time.
 
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. If you have an eligible device, open Windows Update Settings and select Check for updates. Once the upgrade is ready for your device, you will see the option to download and install. Eligible Windows 10 devices must be on version 2004 or later, and have installed the Sept. 14, 2021 servicing update or later, to upgrade directly to Windows 11.
 
For more information on the Windows 11 upgrade experience, watch this video.

    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
    Connections to printers shared via print server might encounter errors
    This issue is observed when print clients try to connect to a remote printer shared on a print server
    OS Build 22000.258
    KB5006674
    2021-10-12
    Resolved
    KB5007262
    2021-11-22
    14:00 PT
    Microsoft Installer might have issues updating or repairing apps
    Affected apps might fail to open after an update or repair has been attempted.
    OS Build 22000.318
    KB5007215
    2021-11-09
    Resolved
    KB5007262
    2021-11-22
    14: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
    Compatibility issues with apps using some non-ASCII characters in their registry keys
    Affected apps might be unable to open and might cause other issues or errors in Windows.
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    UI elements and drawing within some apps may not work as expected
    Some apps using GDI+ might have issues with scaling within the app or when used on high DPI or resolution displays.
    OS Build 22000.258
    KB5006674
    2021-10-12
    Resolved
    KB5007215
    2021-11-09
    10:00 PT
    Snipping Tool and some built-in applications might not open or work as expected
    Some built-in Windows apps or features might have issues on some devices.
    N/A

    Resolved
    KB5008295
    2021-11-05
    10:00 PT
    Compatibility issues have been found between Oracle VirtualBox and Windows 11
    You might be unable to start Virtual machines (VMs) and you might receive an error.
    N/A

    Confirmed
    2021-10-06
    17:26 PT

    Issue details

    November 2021

    Microsoft Installer might have issues updating or repairing apps

    StatusOriginating updateHistory
    Resolved KB5007262OS Build 22000.318
    KB5007215
    2021-11-09
    Resolved: 2021-11-22, 14:00 PT
    Opened: 2021-11-18, 10:34 PT
    After installing KB5007215 or later updates, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted.

    Workaround: To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app.

    Resolution: This issue was resolved in KB5007262. This update should prevent the issue from occurring again, but you might need to reinstall affected apps, if they will not open.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; 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 2004; 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

    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

    UI elements and drawing within some apps may not work as expected

    StatusOriginating updateHistory
    Resolved KB5007215OS Build 22000.258
    KB5006674
    2021-10-12
    Resolved: 2021-11-09, 10:00 PT
    Opened: 2021-11-05, 17:58 PT
    After installing KB5006674 or a later update, certain apps might have unexpected results when rendering some user interface elements or when drawing within the app. You might encounter this issue with apps that use GDI+ and set a zero (0) width pen object on displays with high dots per inch (DPI) or resolution, or if the app is using scaling.

    Resolution: This issue was resolved in KB5007215.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; 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 2004; 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

    Snipping Tool and some built-in applications might not open or work as expected

    StatusOriginating updateHistory
    Resolved KB5008295N/A

    Resolved: 2021-11-05, 10:00 PT
    Opened: 2021-11-02, 20:30 PT
    Starting on November 1, 2021, some users might be unable to open or use certain built-in Windows apps or parts of some built-in apps. This is caused by an issue with a Microsoft digital certificate, which expired October 31, 2021.

    The following might be affected:
    • Snipping Tool
    • Accounts page and landing page in the Settings app (S mode only)
    • Start menu (S mode only)
    • Touch Keyboard, Voice Typing, and Emoji Panel
    • Input Method Editor user interface (IME UI)
    • Getting started and Tips
    Workaround: To mitigate the issue with Snipping Tool, use the Print Screen key on your keyboard and paste the screenshot into your document. You can also paste it into Paint to select and copy the section you want.

    Resolution: This issue was resolved in the out-of-band update KB5008295. Devices directly connected to Windows Update and Windows Update for Business should be offered and automatically install KB5008295 to resolve the issues. If you would like to install the update before it is installed automatically, you will need to Check for updates. For instructions on how to Check for updates, please see Update Windows. To get the standalone package for KB5008295, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the docs page on Microsoft Update Catalog for instructions.

    Affected platforms:
    • Client: Windows 11, version 21H2

    October 2021

    Connections to printers shared via print server might encounter errors

    StatusOriginating updateHistory
    Resolved KB5007262OS Build 22000.258
    KB5006674
    2021-10-12
    Resolved: 2021-11-22, 14:00 PT
    Opened: 2021-10-29, 11:15 PT
    After installation of KB5006674, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
    • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
    • 0x0000007c (ERROR_INVALID_LEVEL)
    • 0x00000709 (ERROR_INVALID_PRINTER_NAME)
    Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
     
    Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
     
    • Print clients must have installed a Windows update released on or after January 2021 before the print server has installed KB5006674.
    Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
    • Default start port: 49152
    • Default end port: 65535
    • Port Range: 16384 ports
    Please refer to these articles for further guidance:
    You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect.
     
    Resolution: This issue was resolved in KB5007262.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; 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 2004; 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

    Compatibility issues with apps using some non-ASCII characters in their registry keys

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-04, 12:18 PT
    Compatibility issues have been found between apps using some non-ASCII characters in their registry keys or subkeys and Windows 11. Affected apps might be unable to open and might cause other issues or errors in Windows, including the possibility of receiving an error with a blue screen. Important Affected registry keys with non-ASCII characters might not be able to be repaired.
    To safeguard your upgrade experience, we have applied a compatibility hold on these devices from installing or being offered Windows 11. If your organization is using Update Compliance, the safeguard ID for devices with Cốc Cốc browser is 35891494. The safeguard ID for devices with Aplicação Autenticação.gov is 36632506.

    Affected platforms:
    • Client: Windows 11, version 21H2
    Resolution: This issue was resolved in  KB5006746 and the safeguard hold has been removed as of November 11, 2021. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 21H2 is offered. 

    Compatibility issues have been found between Oracle VirtualBox and Windows 11

    StatusOriginating updateHistory
    ConfirmedN/A

    Last updated: 2021-10-06, 17:26 PT
    Opened: 2021-10-04, 12:18 PT
    Microsoft and Oracle have found a compatibility issue between VirtualBox and Windows 11, when Hyper-V or Windows Hypervisor is installed. You might be unable to start Virtual machines (VMs) and you might receive an error.

    To safeguard your upgrade experience, we have applied a compatibility hold on these devices from installing or being offered Windows 11. If your organization is using Update Compliance, the safeguard ID is 35004082.

    Workaround: To mitigate the safeguard, you will need to remove Hyper-V or Windows Hypervisor until this issue is resolved with an update Oracle plans to release in October 2021. You can check Oracle's progress by monitoring their ticket #20536. If you are no longer using VirtualBox, uninstalling it should also mitigate the safeguard. 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. 

    Affected platforms:
    • Client: Windows 11, version 21H2
    Next steps: Oracle is working on a resolution and is estimated to release a compatible version of VirtualBox in October 2021. 

    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. If you are trying to upgrade to Windows 11, you might encounter an upgrade compatibility hold and receive the message, "VirtualBox. Your PC requires the latest version of this app. Click Learn More for more information on how to update this app.”