We know the important role your PC plays every day for hybrid work, learning, entertainment and gaming, and we are committed to supporting our customers using Windows 10. Today, we are announcing the availability of the Windows 10 2022 Update (also known as Windows 10, version 22H2). Based on customer feedback we are providing a limited scope of new features and functionality delivered via a familiar, fast and reliable update experience. Version 22H2 will continue the recent Windows 10 feature update trend of being delivered in an optimized way using servicing technology. Show
A scoped and streamlined updateWindows 10, version 22H2 is a scoped release focused on quality improvements to the overall Windows experience in existing feature areas such as quality, productivity and security. We will deliver the 2022 Update using servicing technology (like that used for the monthly update process) to meet our customers’ needs based on feedback. For consumer or commercial users with devices running version 20H2 or later, the 2022 Update will have a fast installation experience. Home and Pro editions of the 2022 Update will receive 18 months of servicing, and Enterprise and Education editions will have 30 months of servicing. More information can be found on the Microsoft Lifecycle Policy site and we will continue to support at least one version of Windows 10 through Oct. 14, 2025. How to get the Windows 10 2022 UpdateThe 2022 Update is available to users with devices running Windows 10, version 20H2 or later who are interested in the latest features and are ready to install this release on their device. If you would like to install the new release, open your Windows Update settings (Settings > Update & Security > Windows Update) and select Check for updates. Eligible devices may also be offered the option to choose to upgrade to Windows 11. If the update appears, you can simply select Download and install to get started. Once the download is complete and the feature update is ready to install, we’ll notify you so that you can pick a convenient time to finish the installation and reboot your device, ensuring that the update does not disrupt your activities. To learn more about the status of the 2022 Update rollout, known issues and new information, visit Windows release health. Information for commercial customersWe recommend that commercial organizations begin targeted deployments to validate that their apps, devices and infrastructure work as expected with the new release. Version 22H2 is now available through Windows Server Update Services (including Configuration Manager), Windows Update for Business and the Volume Licensing Service Center (VLSC)[1]. You can find more information on IT tools to support version 22H2 in the Windows IT Pro Blog. Staying protected and productiveI have consistently noted that being on the latest version of Windows provides you with the latest features, security improvements and control. We recommend that you update your devices to the latest version of Windows 10 or upgrade eligible devices to Windows 11. As a reminder, all editions of Windows 10, version 21H1 will reach the end of servicing on Dec. 13, 2022, and we will start initiating updates to the 2022 Update for these devices later this month[2]. Enterprise and Education editions of Windows 10, version 20H2 will reach end of servicing on May 9, 2023. After these dates, devices running versions 20H2 and 21H1 will no longer receive monthly security and quality updates containing protections from the latest security threats. We will closely monitor both the Windows 10 2022 Update and the Windows 11 upgrade experiences and share timely information on their rollout status and known issues (open and resolved) across both feature and monthly updates via the Windows release health hub and @WindowsUpdate. Please continue to tell us about your experience by providing comments or suggestions via Feedback Hub. Note: [2] Devices running Home and Pro (non-domain joined) editions of Windows 10, version 21H1 Editor’s note: Oct. 18, 2022 – The paragraph above about the scope of the update was changed following initial publication. Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Windows 10, version 21H1
In this articleFind 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. Note: This page will be retired on January 13, 2023. Known issuesThis table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
Issue detailsDecember 2022You might receive an error (0xc000021a) with a blue screen
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:
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:
Taskbar elements might flicker and causes device instability
After installing updates released September 20, 2022 or later, taskbar elements might flicker and cause system instability. Symptoms might include:
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:
Database connections using Microsoft ODBC SQL Server driver might fail.
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". 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 Next steps: We are working on a resolution and will provide an update in an upcoming release. Affected platforms:
November 2022Direct Access might be unable to reconnect after your device has connectivity issues
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:
October 2022Domain join processes may fail with error "0xaac (2732)"
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:
August 2022KB5012170 might fail to install and you might receive a 0x800f0922 error
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:
Additional resourcesAdditional resourcesIn this article |