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
    Outlook search might not locate recent emails
    Searches on Outlook desktop app might fail when emails are stored locally in PST or OST files
    N/A

    Mitigated
    2022-01-19
    15:56 PT
    Certain IPSEC connections might fail
    Some VPN clients using IPSEC or Layer 2 Tunneling Protocol (L2TP) might have issues connecting.
    OS Build 22000.434
    KB5009566
    2022-01-11
    Resolved
    KB5010795
    2022-01-17
    14:00 PT
    The text cursor in some apps might move unexpectedly when using a Japanese IME
    Text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly.
    OS Build 22000.348
    KB5007262
    2021-11-22
    Resolved
    2022-01-04
    17:58 PT
    Applications using Win32 APIs to render colors might not work as expected
    This issue could occur for one of several possible reasons on your device
    N/A

    Investigating
    2021-12-24
    11:31 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 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

    January 2022

    Outlook search might not locate recent emails

    StatusOriginating updateHistory
    MitigatedN/A

    Last updated: 2022-01-19, 15:56 PT
    Opened: 2022-01-19, 15:40 PT
    Recent emails might not appear in search results on Outlook desktop app on Windows 11. This issue is related to emails which have been stored locally in a PST or OST files. It might affect POP and IMAP accounts, as well as Microsoft Exchange and Microsoft 365 hosted accounts. If the default search in the Outlook app is set to server search, the issue will only affect the advanced search.
     
    Workaround: To mitigate the issue, you can disable Windows Desktop Search which will cause Outlook to use its built-in search. For instructions, see Outlook Search not showing recent emails after Windows update KB5008212.

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

    Certain IPSEC connections might fail

    StatusOriginating updateHistory
    Resolved KB5010795OS Build 22000.434
    KB5009566
    2022-01-11
    Resolved: 2022-01-17, 14:00 PT
    Opened: 2022-01-13, 11:05 PT
    After installing KB5009566, IP Security (IPSEC) connections which contain a Vendor ID might fail. VPN connections using Layer 2 Tunneling Protocol (L2TP) or IP security Internet Key Exchange (IPSEC IKE) might also be affected.

    Workaround: To mitigate the issue for some VPNs, you can disable Vendor ID within the server-side settings. Note: Not all VPN servers have the option to disable Vendor ID from being used.

    Resolution: This issue was resolved in the out-of-band update KB5010795. 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, you will need to Check for updates and select "Optional updates" and then select KB5010795. To get the standalone package for KB5010795, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5010795 will not install automatically.

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

    The text cursor in some apps might move unexpectedly when using a Japanese IME

    StatusOriginating updateHistory
    ResolvedOS Build 22000.348
    KB5007262
    2021-11-22
    Resolved: 2022-01-04, 17:58 PT
    Opened: 2022-01-04, 17:29 PT
    After installing KB5007262, text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly in apps that use the multibyte character set (MBCS). This issue affects both the Microsoft Japanese IME and third-party Japanese IMEs.

    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, it can be resolved by installing and configuring a special Group Policy (preferred). Important Verify that you are using the correct Group Policy for your version of Windows.

    Group Policy:
    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • Server: Windows Server 2022

    December 2021

    Applications using Win32 APIs to render colors might not work as expected

    StatusOriginating updateHistory
    InvestigatingN/A

    Last updated: 2021-12-24, 11:31 PT
    Opened: 2021-12-24, 11:15 PT
    After installing Windows 11, some image editing programs might not render colors correctly on certain HDR displays. This is frequently observed with white colors, which could display in bright yellow or other colors. 

    This issue occurs when certain color-rendering Win32 APIs return unexpected information or errors under specific conditions. Not all color profile management programs are affected, and color profile options available in the Windows 11 Settings page, including Microsoft Color Control Panel, are expected to function correctly.

    Next steps: We are working on a resolution and estimate a solution will be available in late January.

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

    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

    October 2021

    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.”