Windows 10, version 22H2

Article
01/13/2023
15 minutes to read

Devices currently on Windows 10, version 20H2 or newer will have a fast installation experience because this feature update will install like a monthly update. For more information on how to install Windows 10, version 22H2, read this blog post. If you want to explore moving to Windows 11, see How to get the Windows 11 2022 Update.

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

Issue details

January 2023

Application shortcuts might not work from the Start menu or other locations

Status	Originating update	History
Resolved	N/A	Resolved: 2023-01-13, 13:40 PT Opened: 2023-01-13, 13:40 PT

After installing security intelligence update build 1.381.2140.0 for Microsoft Defender, application shortcuts in the Start menu, pinned to the taskbar, and on the Desktop might be missing or deleted. Additionally, errors might be observed when trying to run executable (.exe) files which have dependencies on shortcut files. Affected devices have the Atack Surface Reduction (ASR) rule “Block Win32 API calls from Office macro” enabled. After installing security intelligence build 1.381.2140.0, detections resulted in the deletion of certain Windows shortcut (.lnk) files that matched the incorrect detection pattern.

Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.

Workaround: Changes to Microsoft Defender can mitigate this issue. The Atack Surface Reduction (ASR) rules in Microsoft Defender are used to regulate software behavior as part of security measures. Changing ASR rules to Audit Mode can help prevent this issue. This can be done through the following options:

Microsoft Office applications can be launched through the Microsoft 365 app launcher. More details on the Microsoft 365 app launcher can be found in Meet the Microsoft 365 app launcher

Next steps: This issue is resolved in security intelligence update build 1.381.2164.0. Installing security intelligence update build 1.381.2164.0 or later should prevent the issue, but it will not restore previously deleted shortcuts. You will need to recreate or restore these shortcuts through other methods.

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; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB
Server: None

December 2022

Database connections using Microsoft ODBC SQL Server driver might fail.

Status	Originating update	History
Resolved KB5022282	OS Build 19045.2251 KB5019959 2022-11-08	Resolved: 2023-01-10, 10:00 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).

Resolution: This issue was resolved in KB5022282. If you have implemented the above workaround, it is recommended to continue using the configuration in the workaround.

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

Status	Originating update	History
Resolved KB5022282	OS Build 19045.2364 KB5021233 2022-12-13	Resolved: 2023-01-10, 10:00 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:

You will need to enter Windows Recovery Environment. If your device has not automatically started up into WinRE, please see Entry points into WinRE.
Select the Troubleshoot button.
Select the “Start recovery, troubleshooting, and diagnostic tools” button.
Select the “Advanced Options” button.
Select the “Command Prompt” button and wait for your device to restart, if needed.
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.
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:windowssystem32drivershidparse.sys C:windowssystem32hidparse.sys
Once the previous command completes, type: exit
Select the “Continue” button.
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 WindowsSystem32 folder.

Resolution: This issue was resolved in KB5022282. This update should prevent the issue from occurring. Windows devices in which this issue has already occurred will still need to follow the workaround above.

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

Status	Originating update	History
Investigating	OS Build 19045.2130 KB5018410 2022-10-11	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

Status	Originating update	History
Resolved KB5021233	OS Build 19045.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 -> .

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

Your desktop or taskbar might momentarily disappear or might become unresponsive

Status	Originating update	History
Resolved KB5021233	N/A	Resolved: 2022-12-13, 10:00 PT Opened: 2022-11-16, 19:36 PT

After installing or later updates, you might experience an error in which the desktop or taskbar might momentarily disappear, or your device might become unresponsive.

Workaround: If you are unable to use the resolution below, 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 a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> .

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:

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

Status	Originating update	History
Confirmed	N/A	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 () 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 19045.1880 KB5012170 2022-12-13	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.

Source