Windows 11, version 21H2 known issues and notifications

Find information on known issues and the status of the rollout for Windows 11, version 21H2. 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.

The Windows release health hub is always evolving. Take our short survey and let us know how we can improve.

Current status as of May 17, 2022 (PT)

Windows 11 is designated for broad deployment.

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. Note that you also need to be running Windows 10, version 2004 or later, and have no safeguard holds applied to your device. We encourage the use of a Microsoft Account (MSA) to get the most out of your Windows 11 experience. 

For more information on the Windows 11 upgrade experience, watch our video, Windows 11 Upgrade Experience.

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
Sign in failures and other issues related to Kerberos authentication
After installing updates released November 2022, you might have Kerberos authentication issues.
OS Build 22000.1219
KB5019961
2022-11-08
Resolved
2022-11-18
16:22 PT
Direct Access might be unable to reconnect after your device has connectivity issues
This issue might happen after losing network connectivity or transitioning between Wi-Fi networks or access points.
OS Build 22000.1165
KB5018483
2022-10-25
Resolved
2022-11-13
15:34 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
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
KB5012170
2022-08-09
Investigating
2022-10-18
10:04 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

November 2022

Sign in failures and other issues related to Kerberos authentication

StatusOriginating updateHistory
ResolvedOS Build 22000.1219
KB5019961
2022-11-08
Resolved: 2022-11-18, 16:22 PT
Opened: 2022-11-13, 15:16 PT

Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1.

After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:

When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1":

While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.

Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.

Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.

Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them.

To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically.

Cumulative updates:

Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

Standalone Updates:

Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

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 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Direct Access might be unable to reconnect after your device has connectivity issues

StatusOriginating updateHistory
ResolvedOS Build 22000.1165
KB5018483
2022-10-25
Resolved: 2022-11-13, 15:34 PT
Opened: 2022-11-13, 14:49 PT

After installing KB5018483 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN).

Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected.

Workaround: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device.

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 can be resolved 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:

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

October 2022

Domain join processes may fail with error "0xaac (2732)"

StatusOriginating updateHistory
ConfirmedOS 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

Update might fail to install and you might receive a 0x800f0922 error

StatusOriginating updateHistory
InvestigatingOS Build 22000.850
KB5012170
2022-08-09
Last updated: 2022-10-18, 10:04 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.

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

StatusOriginating updateHistory
ConfirmedOS 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

StatusOriginating updateHistory
Mitigated ExternalN/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