Explore this latest release.
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.
- Windows 11 is now available
- How to get Windows 11
Explore the upgrade experience.
|Summary||Originating update||Status||Last 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 |
|Certain IPSEC connections might fail|
Some VPN clients using IPSEC or Layer 2 Tunneling Protocol (L2TP) might have issues connecting.
|OS Build 22000.434|
|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|
|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 |
|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 |
|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 |
Outlook search might not locate recent emails
|Status||Originating update||History||Mitigated||N/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.
Certain IPSEC connections might fail
|Status||Originating update||History||Resolved KB5010795||OS Build 22000.434|
|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.
The text cursor in some apps might move unexpectedly when using a Japanese IME
|Status||Originating update||History||Resolved||OS Build 22000.348|
|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.
Applications using Win32 APIs to render colors might not work as expected
|Status||Originating update||History||Investigating||N/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.
Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
|Status||Originating update||History||Mitigated External||N/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.
Compatibility issues have been found between Oracle VirtualBox and Windows 11
|Status||Originating update||History||Confirmed||N/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.
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.”