Windows 11, version 21H2 known issues and notifications
Find information on known issues and the status of the Windows 11, version 21H2 rollout. For immediate help with Windows update issues, use the Get Help app in Windows or go to support.microsoft.com. Follow @WindowsUpdate on Twitter for Windows release health updates.
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Integrated camera might not work as expected on some Arm-based devices Starting May 23, 2023, some Arm-based devices might be unable to use the integrated webcam due to a driver issue. | N/A | Mitigated External | 2023-05-26 18:48 PT |
| Saving or copying files might intermittently fail You might receive an error or files might intermittently fail to save or copy, especially to network shares. | OS Build 22000.1761 KB5023774 2023-03-28 | Resolved | 2023-05-24 11:05 PT |
| Start menu, Windows Search and UWP apps might have issues opening Affected devices have apps installed which integrate with Windows, Microsoft Office, or Microsoft Outlook. | N/A | Mitigated | 2023-05-18 17:17 PT |
| "Local Security Authority protection is off." with persistent restart Once enabled, your Windows device might persistently notify you that it is vulnerable, and a restart is required. | N/A | Mitigated | 2023-05-16 17:23 PT |
| Third-party UI customization apps might cause Windows to not start up Apps to change behaviors or UI in Windows 11 might cause issues with updates released February 28, 2023 or later. | OS Build 22000.30000 KB5023774 2023-03-28 | Resolved External | 2023-05-09 10:06 PT |
| You might receive an error with apphelp.dll from apps using DirectX After installing KB5019980 or later updates, devices with older Intel graphics drivers might encounter issues. | OS Build 22000.1219 KB5019961 2022-11-08 | Mitigated | 2023-02-24 14:44 PT |
| Devices with locale set to Croatia might not utilize the expected currency This can affect applications which retrieve the device's currency for purchases or other transactions | N/A | Confirmed | 2023-02-23 14:24 PT |
| KB5012170 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 KB5012170 2022-08-09 | Confirmed | 2022-12-14 16:12 PT |
| Domain join processes may fail with error "0xaac (2732)" This might be encountered when an account was created by a different identity than the one used to join the domain | OS Build 22000.1098 KB5018418 2022-10-11 | Confirmed | 2022-10-27 16:57 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 | 2022-09-22 17:52 PT |
| Some devices might start up into BitLocker Recovery Some devices might require BitLocker Recovery key to start up after installing Security update for Secure Boot DBX. | OS Build 22000.850 KB5012170 2022-08-09 | Confirmed | 2022-08-19 19:46 PT |
Issue details
May 2023
Integrated camera might not work as expected on some Arm-based devices
| Status | Originating update | History | Mitigated External | N/A | Last updated: 2023-05-26, 18:48 PT Opened: 2023-05-26, 18:02 PT |
|---|
Windows devices using certain Arm-based processors might have issues using integrated cameras starting on May 23, 2023. When encountering this issue, you might receive an “0xA00F4271<MediaCaptureFailedEvent> (0x80004005)” error when attempting to use the Camera app. Affected devices use these processors: Qualcomm 8cx Gen 1, Qualcomm 8cx Gen 2, Microsoft SQ1, and Microsoft SQ2. Note: This issue does not affect USB cameras or webcams, even when attached to an affected Windows devices.
Workaround: Microsoft is deploying a critical troubleshooter to mitigate this issue on most affected Windows devices. Troubleshooters are applied automatically and can't be run manually. For more information about troubleshooting, see keep your device running smoothly with recommended troubleshooting. To check if the troubleshooter has been applied, look for the following in troubleshooter history:
To mitigate this issue on managed devices where troubleshooters are disabled by your organization or if you want the mitigation before the troubleshooter has run automatically, use the following steps to disable the affected feature of the camera driver. Important: You should apply this workaround only on devices experiencing this issue. Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk:
- Select the Start button and type cmd, then right click or long press on Command Prompt and select Run as administrator.
- Copy and paste the following command and run the command by pressing Enter: reg add "HKLM\SYSTEM\CurrentControlSet\Control\Qualcomm\Camera" /v EnableQCOMFD /t REG_DWORD /d 0 /f
- Restart any app which uses the camera or restart your Windows device.
- The integrated camera should now function as expected.
Note: This workaround might disable some features of the camera or lower the image quality but should allow the camera to function until the issue is resolved by the device manufacturer with an updated camera driver. An updated driver should restore full camera functionality and the workaround should not need to be undone.
Next steps: Microsoft is working with device manufacturers (OEMs) and driver partners to resolve this issue with a driver update and will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2
- Server: None
Saving or copying files might intermittently fail
| Status | Originating update | History | Resolved | OS Build 22000.1761 KB5023774 2023-03-28 | Resolved: 2023-05-24, 11:05 PT Opened: 2023-05-24, 10:32 PT |
|---|
After installing KB5023774 or later updates, you might have intermittent issues saving, or copying, or attaching files using 32-bit apps which are large address aware and using the CopyFile API. Windows devices are more likely to be affected by this issue when using some commercial/enterprise security software which uses extended file attributes. We are not receiving reports that copying files using File Explorer is affected, but CopyFile API used within apps might be affected. Microsoft Office apps such as Microsoft Word or Microsoft Excel are only affected when using 32-bit versions and you might receive the error, "Document not saved." This issue is unlikely to be experienced by consumers using Windows devices in their home or on non-managed comercial device. Note: Apps are not affected by this issue if they are 64-bit or 32-bit and NOT large address aware.
Workaround: To mitigate the issue, you can attempt to save or copy again. Since the issue is intermittent, it is likely to succeed on a subsequent try. Important: If the resolution below does not resolve intermittent save or copy issues in your environment, then you might be experiencing a different issue with similar symptoms.
Resolution: This issue is resolved using Known Issue Rollback (KIR). Enterprise-managed devices that have installed an affected update and have 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 -> <Group Policy name listed below>.
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 - KB5023774 230222_032017 Known Issue Rollback
- Download for Windows 10, version 22H2; Windows 10, version 21H2 - KB5023773 230222_032013 Known Issue Rollback
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 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2
- Server: None
March 2023
"Local Security Authority protection is off." with persistent restart
| Status | Originating update | History | Mitigated | N/A | Last updated: 2023-05-16, 17:23 PT Opened: 2023-03-21, 11:18 PT |
|---|
After installing "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version 1.0.2302.21002)", you might receive a security notification or warning stating that "Local Security protection is off. Your device may be vulnerable." and once protections are enabled, your Windows device might persistently prompt that a restart is required. Important: This issue affects only "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version 1.0.2302.21002)". All other Windows updates released on March 14, 2023 for affected platforms (KB5023706 and KB5023698), do not cause this issue.
Workaround: If you have enabled Local Security Authority (LSA) protection and have restarted your device at least once, you can dismiss warning notifications and ignore any additional notifications prompting for a restart. You can verify that LSA protection is enabled by looking in Event Viewer using the information available here. Important: Currently, we do not recommend any other workaround for this issue.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Updated May 16, 2023: This known issue was previously resolved with an update for Microsoft Defender Antivirus antimalware platform KB5007651 (Version 1.0.2303.27001) but issues were found, and that update is no longer being offered to devices. If you encounter this issue, you will need to use the above workaround until the issue is resolved. If you have installed Version 1.0.2303.27001 and receive an error with a blue screen or if your device restarts when attempting to open some games or apps, you will need to disable Kernel-mode Hardware-enforced Stack Protection. To do this, select the Start button, type Windows Security and select it, select Device Security then select Core Isolation then disable Kernel-mode Hardware-enforced Stack Protection.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: None
February 2023
Third-party UI customization apps might cause Windows to not start up
| Status | Originating update | History | Resolved External | OS Build 22000.30000 KB5023774 2023-03-28 | Last updated: 2023-05-09, 10:06 PT Opened: 2023-02-28, 09:54 PT |
|---|
After installing KB5023774 or later updates, Windows devices with some third-party UI customization apps might not start up. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.
Workaround: We recommend uninstalling any third-party UI customization app before installing KB5023774 to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using.
Resolution: ExplorerPatcher and StartAllBack have released a version which lists this issue as resolved. Note: If you are using any third-party UI customization app and encounter this or any other issues, you will need to contact customer support for the developer of the app you are using.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: None
You might receive an error with apphelp.dll from apps using DirectX
| Status | Originating update | History | Mitigated | OS Build 22000.1219 KB5019961 2022-11-08 | Last updated: 2023-02-24, 14:44 PT Opened: 2023-02-08, 15:49 PT |
|---|
After installing KB5019961 or later updates, you might receive an error with apphelp.dll on Windows devices using Intel graphics drivers with versions 26.20.100.7463 up to 30.0.101.1190. This issue might happen intermittently and affects a small number of enterprise apps which use DirectX or Direct3D to render part or all of their content. Windows devices using updated Intel graphics drivers with a version later than 30.0.101.1190 are not affected by this issue and already have the Intel resolution for this issue installed.
Home users of Windows are unlikely to experience this issue, as the few affected apps are more commonly used in enterprise environments.
Workaround: To mitigate this issue, you can install an Intel graphics driver with a later version than 30.0.101.1190. It is recommended to check your Windows device manufacturer's support for the latest version of the Intel graphics driver for your device. If they do not offer a driver later than 30.0.101.1190, you can check List of Drivers for Intel Graphics for information on how to download and install the latest Intel graphics driver available from Intel directly.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022
Devices with locale set to Croatia might not utilize the expected currency
| Status | Originating update | History | Confirmed | N/A | Last updated: 2023-02-23, 14:24 PT Opened: 2023-02-23, 13:22 PT |
|---|
The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device's currency for purchases or other transactions.
Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.
Workaround: Changing the currency in Windows can help. This can be accomplished via the Windows Control Panel.
- Open the "Windows Region" settings. This can be done in one of the following ways:
- Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
- On your keyboard, press and hold the Windows key, then press the letter R. This will open the "Run" window. Type INTL.CPL into the Open field,
- In the Region settings, choose one of the 2 locales for Croatia:
- Croatian (Bosnia & Herzegovina)
- Croatian (Croatia)
- In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
- Change the currency symbol from "KN" to Euro, "€"
Additional information can be seen here: Currency formatting - Globalization | Microsoft Learn.
Manually changing currency might also be an option in some applications. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Some applications might not allow this manual change. Please view the settings and documentation for your applications.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; 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, version 1809; Windows Server 2019; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
January 2023
Start menu, Windows Search and UWP apps might have issues opening
| Status | Originating update | History | Mitigated | N/A | Last updated: 2023-05-18, 17:17 PT Opened: 2023-01-24, 09:47 PT |
|---|
The Start menu, Windows search, and Universal Windows Platform (UWP) apps might not work as expected or might have issues opening. Affected Windows devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, or Microsoft Outlook or Outlook Calendar. An example of an app affected by this issue is ClickShare. The underlying Issue is not caused by the installation of an update to Windows and might be exposed by an update to an affected app.
Workaround: To mitigate this issue, you can uninstall apps which integrate with Windows, Microsoft Office, Microsoft Outlook or Outlook Calendar. Updates to affected apps or guidance from the developer of the app might also be available. If you are using ClickShare by Barco, please see Symptom: Start Menu and other shell components fail when Apps including Barco's ClickShare access Office APIs and Unresponsive Windows taskbar or user shell folder permissions issues with ClickShare App Calendar integration.
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2
- Server: None
October 2022
Domain join processes may fail with error "0xaac (2732)"
| Status | Originating update | History | Confirmed | OS Build 22000.1098 KB5018418 2022-10-11 | Last updated: 2022-10-27, 16:57 PT Opened: 2022-10-27, 15:53 PT |
|---|
Domain join operations might intentionally fail with error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" and text "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy."
This issue originates with the October 2022 security updates ( KB5018418) which introduced some hardening changes enabled by default for domain join. Please see KB5020276 - Netjoin: Domain join hardening changes to understand the new designed behavior.
Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain.
Home users of Windows are unlikely to experience this issue.
Next steps: Please see KB5020276 to understand the designed behavior. We have added insights to this KB, and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated once those changes have released.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; 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; 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 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
August 2022
KB5012170 might fail to install and you might receive a 0x800f0922 error
| Status | Originating update | History | Confirmed | OS Build 22000.850 KB5012170 2022-08-09 | Last updated: 2022-12-14, 16:12 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.
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.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; 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
Some devices might start up into BitLocker Recovery
| Status | Originating update | History | Confirmed | OS Build 22000.850 KB5012170 2022-08-09 | Last updated: 2022-08-19, 19:46 PT Opened: 2022-08-19, 19:36 PT |
|---|
Some devices might enter BitLocker Recovery on the first or second restart after attempting to install Security update for Secure Boot DBX ( KB5012170), released August 9, 2022. 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: If your device is prompting for a BitLocker Recovery key, you will need to supply it to start up Windows. For more information, see Finding your BitLocker recovery key in Windows.
If you have not installed KB5012170 yet and have BitLocker enabled on your device, follow the instructions below to temporarily suspend BitLocker before installing.
If you have installed KB5012170 and have not yet restarted your device or have only restarted your device once, temporarily suspend BitLocker using the instructions below.
Important: If you have restarted your device two times or more after installing KB5012170, your device is not affected by this issue
To temporarily suspend BitLocker, or to avoid a BitLocker recovery when deploying KB5012170, follow these steps:
1. Run the following command from Administrator command prompt:
Manage-bde -protectors -disable %systemdrive% -rebootcount 2
2. Install the update KB5012170, if not already installed
3. Restart the device.
4. Restart the device again.
5. BitLocker should automatically be enabled after two boots. If you want to manually resume BitLocker to verify that it is enabled, use the following command:
Manage-bde -protectors -Enable %systemdrive%
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Affected platforms:
- Client: Windows 11, version 21H2
- Server: None
November 2021
Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
| Status | Originating update | History | Mitigated External | N/A | Last updated: 2022-09-22, 17:52 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, version 22H2 or Windows 11, version 21H2. If your organization is using Update Compliance, the safeguard IDs are:
- Windows 11, version 21H2: 36899911
- Windows 11, version 22H2: 41291788
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 22H2; Windows 11, version 21H2
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.