Windows 10, version 21H1

Find information on known issues and the status of the rollout for Windows 10, version 21H1. 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 December 13, 2022

As of December 13, 2022, all editions of Windows 10, version 21H1 have reached end of servicing. The December 2022 security update, released on December 13, is the last update available for this version. Devices running this version will no longer receive monthly security and preview updates containing protections from the latest security threats.

To help keep you protected and productive, Windows Update will automatically initiate a feature update to Windows 10, version 22H2 for consumer devices and non-managed business devices when they are nearing or have reached end of servicing. For this automatic installation, you can choose a convenient time for your device to restart and complete update. You can also opt to upgrade eligible devices to Windows 11.

For detailed information, see the entry for Windows 10, version 21H1 end of servicing at learn.microsoft.com lifecycle page, and Reminder: End of servicing for Windows 10, version 21H1 at Windows IT Pro blog. For information about servicing timelines and lifecycle, see Windows 10 release informationWindows 11 release information, and Lifecycle FAQ - Windows.

Note: This page will be retired on January 13, 2023.

    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
    Database connections using Microsoft ODBC SQL Server driver might fail.
    Apps using ODBC connections might fail to connect to databases.
    OS Build 19043.2251
    KB5019959
    2022-11-08
    Mitigated
    2023-01-05
    16:46 PT
    You might receive an error (0xc000021a) with a blue screen
    Some Windows devices might start up to an error.
    OS Build 19043.2364
    KB5021233
    2022-12-13
    Mitigated
    2022-12-21
    14:41 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.
    OS Build 19043.2193
    KB5018482
    2022-10-25
    Resolved
    KB5021233
    2022-12-13
    10:00 PT
    Taskbar elements might flicker and causes device instability
    This issue is resolved using Known Issue Rollback (KIR)
    OS Build 19043.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 19043.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 19043.2130
    KB5018410
    2022-10-11
    Confirmed
    2022-10-27
    16:57 PT

    Issue details

    December 2022

    Database connections using Microsoft ODBC SQL Server driver might fail.

    StatusOriginating updateHistory
    MitigatedOS Build 19043.2251
    KB5019959
    2022-11-08
    Last updated: 2023-01-05, 16:46 PT
    Opened: 2022-12-05, 15:45 PT

    After installing KB5019959, apps which use ODBC connections utilizing the Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might fail to connect. You might receive an error within the app or you might receive an error from SQL Server, such as "The EMS System encountered a problem" with "Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream" or "Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server". Note for developers: Apps affected by this issue might fail to fetch data, for example when using the SQLFetch function. This issue might occur when calling SQLBindCol function before SQLFetch or calling SQLGetData function after SQLFetch and when a value of 0 (zero) is given for the ‘BufferLength’ argument for fixed datatypes larger than 4 bytes (such as SQL_C_FLOAT).

    If you are unsure if you are using any affected apps, open any apps which use a database and then open Command Prompt (select Start then type command prompt and select it) and type the following command:

    tasklist /m sqlsrv32.dll
    

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

    • ​If your app is already using or able to use Data Source Name (DSN) to select ODBC connections, install Microsoft ODBC Driver 17 for SQL Server and select it for use with your app using DSN. Note: We recommend the latest version of Microsoft ODBC Driver 17 for SQL Server, as it is more compatible with apps currently using the legacy Microsoft ODBC SQL Server Driver (sqlsrv32.dll) than Microsoft ODBC Driver 18 for SQL Server.
    • ​If your app is unable to use DSN, the app will need to be modified to allow for DSN or to use a newer ODBC driver than Microsoft ODBC SQL Server Driver (sqlsrv32.dll).

    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 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

    You might receive an error (0xc000021a) with a blue screen

    StatusOriginating updateHistory
    MitigatedOS Build 19043.2364
    KB5021233
    2022-12-13
    Last updated: 2022-12-21, 14:41 PT
    Opened: 2022-12-17, 15:18 PT

    After installing KB5021233, some Windows devices might start up to an error (0xc000021a) with a blue screen. Technical note: After installing KB5021233, there might be a mismatch between the file versions of hidparse.sys in c:/windows/system32 and c:/windows/system32/drivers (assuming Windows is installed to your C: drive), which might cause signature validation to fail when cleanup occurs.

    Workaround: To mitigate this issue on devices already experiencing it, you will need to use Windows Recovery Environment (WinRE) with the following steps:

    1. ​You will need to enter Windows Recovery Environment. If your device has not automatically started up into WinRE, please see Entry points into WinRE.
    2. ​Select the Troubleshoot button.
    3. ​Select the "Start recovery, troubleshooting, and diagnostic tools" button.
    4. ​Select the "Advanced Options" button.
    5. ​Select the "Command Prompt" button and wait for your device to restart, if needed.
    6. ​Your device should restart to a Command Prompt window. You might need to sign into your device with your password before getting to the Command Prompt window.
    7. ​Run the following command (Important: If Windows is not installed to C:\windows you will need to modify the command to your environment): xcopy C:\windows\system32\drivers\hidparse.sys C:\windows\system32\hidparse.sys
    8. ​Once the previous command completes, type: exit
    9. ​Select the "Continue" button.
    10. ​Windows should now start up as expected.

    Important: It is not recommended to follow any other workaround than those recommended above. We do not recommend deleting the hidparse.sys from your Windows\System32 folder.

    Next steps: We are working on a resolution and will provide an update 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

    Taskbar elements might flicker and causes device instability

    StatusOriginating updateHistory
    InvestigatingOS Build 19043.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

    November 2022

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

    StatusOriginating updateHistory
    Resolved KB5021233OS Build 19043.2193
    KB5018482
    2022-10-25
    Resolved: 2022-12-13, 10:00 PT
    Opened: 2022-11-13, 14:49 PT

    After installing KB5018482 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: You can mitigate this issue by restarting your Windows device.

    Resolution: This issue was resolved in updates released December 13, 2022 ( KB5021233) 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 December 13, 2022 ( KB5021233) 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 December 13, 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 -> <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 19043.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 19043.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