Windows 10, version 21H2

  • Article
  • 12 minutes to read

Find information on known issues and the status of the Windows 10, 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.

Current status as of April 15, 2022 (PT)

Windows 10, version 21H2 is designated for broad deployment. As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For more details, see How to get the Windows 10 November 2021 Update.

If you are using Windows 10 and want to move to Windows 11, you can check 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, have no safeguard holds applied to your device, and have a Microsoft Account (MSA) if using Home edition.

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

    Known issues

    See open issues, issues resolved in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

    SummaryOriginating updateStatusLast updated
    Windows 11 upgrades were offered to ineligible devices
    Affected devices were not able to complete the installation process.
    		N/A

    		Resolved
    		2023-02-24
    18:01 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 19044.2251
    KB5019959
    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
    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

    		Investigating
    		2023-01-24
    09:58 PT
    Taskbar elements might flicker and causes device instability
    This issue is resolved using Known Issue Rollback (KIR)
    		OS Build 19044.2075
    KB5017380
    2022-09-20    		Investigating
    		2022-12-16
    10:38 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 19044.1880
    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 19044.2130
    KB5018410
    2022-10-11    		Confirmed
    		2022-10-27
    16:57 PT

    Issue details

    February 2023

    Windows 11 upgrades were offered to ineligible devices

    StatusOriginating updateHistory
    ResolvedN/A

    		Resolved: 2023-02-24, 18:01 PT
    Opened: 2023-02-24, 17:43 PT

    Some hardware ineligible Windows 10 and Windows 11, version 21H2 devices were offered an inaccurate upgrade to Windows 11. These ineligible devices did not meet the minimum requirements to run Window 11. Devices that experienced this issue were not able to complete the upgrade installation process.

    This issue was detected on February 23, 2023, and resolved on the same day.

    Resolution: This issue is resolved. It might take 24 to 48 hours to propagate to all affected devices. Affected users do not need to take any steps.

    Affected platforms:

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

    You might receive an error with apphelp.dll from apps using DirectX

    StatusOriginating updateHistory
    MitigatedOS Build 19044.2251
    KB5019959
    2022-11-08    		Last updated: 2023-02-24, 14:44 PT
    Opened: 2023-02-08, 15:49 PT

    After installing KB5019959 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

    StatusOriginating updateHistory
    ConfirmedN/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.

    1. ​Open the "Windows Region" settings. This can be done in one of the following ways:
      1. ​Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
      2. ​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,
    2. ​In the Region settings, choose one of the 2 locales for Croatia:
      1. ​Croatian (Bosnia & Herzegovina)
      2. ​Croatian (Croatia)
    3. ​In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
    4. ​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

    StatusOriginating updateHistory
    InvestigatingN/A

    		Last updated: 2023-01-24, 09:58 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 presently investigating 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

    December 2022

    Taskbar elements might flicker and causes device instability

    StatusOriginating updateHistory
    InvestigatingOS Build 19044.2075
    KB5017380
    2022-09-20    		Last updated: 2022-12-16, 10:38 PT
    Opened: 2022-12-16, 09:00 PT

    After installing updates released September 20, 2022 or later, taskbar elements might flicker and cause system instability. Symptoms might include: 

    • ​The Weather or News and Interests widget or icons flickers on the Windows taskbar
    • ​The Windows taskbar stops responding
    • ​Windows Explorer stops responding
    • ​Applications including Microsoft Word or Excel might stop responding if they are open when the issue occurs

    Restarting the devices can alleviate the issue in some cases, but possibly not all.

    Resolution: This issue is resolved using Known Issue Rollback (KIR). KIRs are applied to most consumer (home) and non-managed devices without the need for any manual action. Please note that it might take up to 24 hours for the resolution to propagate automatically to these devices. Restarting your Windows device might help the resolution apply to your device faster. 

    Enterprise-managed devices which 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>.

    Group Policy download with Group Policy name:

    Download for Windows 10 version 22H2, 21H2, 21H1, and 20H2 - Windows 10 20H2, 21H1, 21H2 and 22H2 KB5017380 221207_23451 Feature Preview.msi

    We are also working to make a resolution available in an upcoming release.

    Affected platforms:

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

    October 2022

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

    StatusOriginating updateHistory
    ConfirmedOS Build 19044.2130
    KB5018410
    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 ( KB5018410) 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

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

    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.