Explore what's next in security, productivity, and management.
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 and the future of hybrid work
- How to get Windows 11
Explore the upgrade experience.
|Summary||Originating update||Status||Last updated|
|Update might fail to install and you might receive a 0x800f0922 error|
Security update for Secure Boot DBX might fail to install.
|OS Build 22000.850|
|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||2022-08-12 |
|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|
|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|
|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|
|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|
Update might fail to install and you might receive a 0x800f0922 error
|Status||Originating update||History||Investigating||OS Build 22000.850|
|Last updated: 2022-08-12, 17:08 PT
Opened: 2022-08-12, 17:08 PT
When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.
Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.
Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.
Next steps: We are presently investigating and will provide an update in an upcoming release.
- 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
- Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
XPS documents with non-English language characters might not open
|Status||Originating update||History||Confirmed||OS Build 22000.778|
|Last updated: 2022-08-08, 18:08 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.
- Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
- Server: Windows Server, version 20H2
Start menu might not open
|Status||Originating update||History||Resolved KB5016629||OS Build 22000.778|
|Resolved: 2022-08-09, 10:00 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 was resolved in updates released August 9, 2022 ( KB5016629) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released August 9, 2022 ( KB5016629) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before August 9, 2022, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. 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:
- Download for Windows 11, version 21H2 - KB5014668 220721_04201 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
- Client: Windows 11, version 21H2
- Server: None
PowerShell Desired State Configuration resources might fail to apply successfully
|Status||Originating update||History||Resolved KB5015814||OS Build 22000.739|
|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.
- 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
Some .NET Framework 3.5 apps might have issues
|Status||Originating update||History||Resolved||OS Build 22000.652|
|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.
- Client: Windows 11, version 21H2
- Server: None
Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
|Status||Originating update||History||Mitigated External||N/A ||Last updated: 2022-08-12, 17:03 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) on Intel 11th Gen Core processors 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 or 10.30.0.5152. Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10.29.0.5152 or 10.30.0.5152 are affected by this issue.
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.
- Client: Windows 11, version 21H2