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
    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
    Copying files/shortcuts using Group Policy Preferences might not work as expected
    Files or shortcuts might not copy or copy as zero-byte files when using Group Policy Preferences on client devices.
    OS Build 22000.978
    KB5017328
    2022-09-13
    Confirmed
    2022-09-22
    16:49 PT
    The September 2022 preview release is listed in Windows Server Update Services
    Preview updates are generally made available from the Microsoft Update Catalog and Windows Updates.
    N/A

    Confirmed
    2022-09-22
    14:31 PT
    Possible issues caused by new Daylight Savings Time in Chile
    Chilean government announced a Daylight Saving Time (DST) change for 2022.
    N/A

    Resolved
    KB5017383
    2022-09-20
    10:00 PT
    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
    KB5014668
    2022-06-23
    Resolved
    KB5017383
    2022-09-20
    10:00 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-09-20
    10:06 PT
    Voice typing might fail to open
    When using Windows key + h to open voice typing, you might receive an error.
    N/A

    Resolved
    2022-09-13
    16:52 PT
    Unable to sign in after adding a new Microsoft Account user in Windows
    A newly added Microsoft account user might be unable to sign in after restarting or logging off.
    OS Build 22000.918
    KB5016691
    2022-08-25
    Resolved
    2022-09-07
    13:56 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

    September 2022

    Copying files/shortcuts using Group Policy Preferences might not work as expected

    StatusOriginating updateHistory
    ConfirmedOS Build 22000.978
    KB5017328
    2022-09-13
    Last updated: 2022-09-22, 16:49 PT
    Opened: 2022-09-22, 15:23 PT

    After installing KB5017328, file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration -> Preferences -> Windows Settings in Group Policy Editor.

    Workaround: To mitigate this issue, you can do ONE of the following:

    • ​Uncheck the "Run in logged-on user's security context (user policy option)". Note: This might not mitigate the issue for items using a wildcard (*).
    • ​Within the affected Group Policy, change "Action" from "Replace" to "Update".
    • ​If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotes) from the destination might allow the copy to be successful.

    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 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 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    The September 2022 preview release is listed in Windows Server Update Services

    StatusOriginating updateHistory
    ConfirmedN/A

    Last updated: 2022-09-22, 14:31 PT
    Opened: 2022-09-22, 10:51 PT

    IT administrators who utilize Windows Server Update Services (WSUS) might notice that the Windows September 2022 preview update, known as the 'C' release, is listed among the updates available from WSUS. This listing is an error. Preview updates are generally available for manual importing via the Microsoft Update Catalog and Windows Updates.

    This issue might also affect the installation of the September 2022 Cumulative Update Preview for .NET Framework, which is also generally available via Windows Update and Microsoft Update Catalog. For more information on .NET Framework September 2022 Cumulative Update Preview updates, see the KB articles listed on the .NET blog for the September 2022 Cumulative Update Preview.

    Home users of Windows are unlikely to experience this issue. WSUS is commonly utilized by technology administrators to deploy Microsoft product updates in managed environments. 

    Workaround: The Windows September 2022 preview release was made available via Microsoft Update Catalog. We recommend IT administrators to use this release channel moving forward.

    Please note: In environments where WSUS is configured to auto-approve updates and also auto-decline superseded content, the Windows September 2022 Security update may subsequently be auto-declined and auto-expired from the client view. If this occurs, see the guidance for reinstating declined updates. Then run an update synchronization within Microsoft Endpoint Configuration Manager, or update management environments. Environments configured to only take security updates should not reflect these symptoms.

    Next steps: The Windows September 2022 preview release is being removed from WSUS and we are working on a resolution to support customers who had imported updates via WSUS inadvertently. We estimate a solution will be available in the coming days.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 11, version 21H1; Windows 10, version 20H2; Windows 10, version 1809
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809

    Possible issues caused by new Daylight Savings Time in Chile

    StatusOriginating updateHistory
    Resolved KB5017383N/A

    Resolved: 2022-09-20, 10:00 PT
    Opened: 2022-09-02, 13:17 PT

    Starting at 12:00 a.m. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by Chilean government about a Daylight Saving Time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

    Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

    • ​Time shown in Windows and apps will not be correct.
    • ​Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.
    • ​Automation using date and time, such as Scheduled tasks, might not run at the expected time.
    • ​Timestamp on transactions, files, and logs will be 60 minutes off.
    • ​Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.
    • ​Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

    Workaround: This issue is now resolved in KB5017383 but you should undo the workaround, if it is still being used.

    You can mitigate this issue on devices in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:

    • ​Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off.
    • ​Go to Control Panel Clock and Region Date and Time Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”.

    To mitigate this issue in the Santiago time zone, after 12:00 a.m. on September 11, 2022, and for those in the Easter Islands time zone, after 10:00 p.m. on September 10, 2022, follow the steps below to re-enable automatic DST adjustments and ensure accurate time switching with future DST transitions. This can be done by doing either of the following:

    • ​Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to On.
    • ​Go to Control Panel Clock and Region Date and Time Change time zone and check the option for “Automatically adjust clock for Daylight Saving Time”.

    Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Chile. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if not done correctly.

    Resolution: This issue was resolved in KB5017383. Note: If the workaround above was used, it should have been undone on September 11, 2022. Installation of KB5017383 will not change the "Automatically adjust clock for Daylight Saving Time" setting.

    Affected platforms:

    • ​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; 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

    Voice typing might fail to open

    StatusOriginating updateHistory
    ResolvedN/A

    Resolved: 2022-09-13, 16:52 PT
    Opened: 2022-09-13, 16:38 PT

    When attempting to open voice typing by using the keyboard shortcut of Windows key + h, you might receive the error "Something went wrong." If this error is received, voice typing will not open.

    Resolution: This issue has been resolved with a server-side change. Voice typing should now open and function as expected.

    Affected platforms:

    • ​Client: Windows 11, version 21H2
    • ​Server: None

    Unable to sign in after adding a new Microsoft Account user in Windows

    StatusOriginating updateHistory
    ResolvedOS Build 22000.918
    KB5016691
    2022-08-25
    Resolved: 2022-09-07, 13:56 PT
    Opened: 2022-09-07, 13:56 PT

    After installing KB5016691 and adding a new Microsoft account user in Windows, you might be unable to sign in for a brief time after the first restart or sign out. The issue only affects the newly added Microsoft account user and only for the first sign in.

    This issue only affects devices after adding a Microsoft account. It does not affect Active Directory domain users accounts or Azure Active Directory accounts.

    Workaround: If you encounter this issue, it will automatically resolve itself after a brief time. You will need to wait for the lock screen to appear again, you should be able to login as expected.

    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 resolve it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> KB5016691 220722_051525 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:

    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 21H2
    • ​Server: None

    August 2022

    XPS documents with non-English language characters might not open

    StatusOriginating updateHistory
    Resolved KB5017383OS Build 22000.778
    KB5014668
    2022-06-23
    Resolved: 2022-09-20, 10:00 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.

    Resolution: This issue was resolved in KB5017383.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • ​Server: Windows Server, version 20H2

    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-09-20, 10:06 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 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

    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