Resolved issues in Windows 10, version 22H2
Find information on recently resolved issues for Windows 10, version 22H2. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). For immediate help with Windows update issues, use Get Help in Windows or go to support.microsoft.com. Follow @WindowsUpdate on Twitter for Windows release health updates.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| 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 |
| Application shortcuts might not work from the Start menu or other locations Errors might be observed when trying to run exe files. Changes to Microsoft Defender can help. | N/A | Resolved | 2023-01-18 19:28 PT |
| Database connections using Microsoft ODBC SQL Server driver might fail. Apps using ODBC connections might fail to connect to databases. | OS Build 19045.2251 KB5019959 2022-11-08 | Resolved KB5022282 | 2023-01-10 10:00 PT |
| You might receive an error (0xc000021a) with a blue screen Some Windows devices might start up to an error. | OS Build 19045.2364 KB5021233 2022-12-13 | Resolved KB5022282 | 2023-01-10 10:00 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 19045.2193 KB5018482 2022-10-25 | Resolved KB5021233 | 2022-12-13 10:00 PT |
| Sign in failures and other issues related to Kerberos authentication After installing updates released November 2022, you might have Kerberos authentication issues. | OS Build 19045.2251 KB5019959 2022-11-08 | Resolved | 2022-11-18 16:22 PT |
| Your desktop or taskbar might momentarily disappear or might become unresponsive You might experience an error in which the desktop or taskbar disappearing then reappearing. | N/A | Resolved KB5021233 | 2022-12-13 10:00 PT |
| Microsoft OneDrive app might unexpectedly close You might be unable to signout or unlink your OneDrive account and sites or folders from Microsoft Teams and SharePoint. | OS Build 19045.2130 KB5018410 2022-10-11 | Resolved KB5020953 | 2022-10-28 14:00 PT |
| Possible issues caused by Daylight Savings Time change in Jordan Jordanian government announced a Daylight Saving Time (DST) change for winter 2022. | N/A | Resolved KB5018482 | 2022-10-25 14:00 PT |
Issue details
February 2023
Windows 11 upgrades were offered to ineligible devices
| Status | Originating update | History | Resolved | N/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
January 2023
Application shortcuts might not work from the Start menu or other locations
| Status | Originating update | History | Resolved | N/A | Resolved: 2023-01-18, 19:28 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:
- Using Intune: Enable attack surface reduction rules | Defender for Endpoint: Microsoft Endpoint Manager
- Using Group Policy: Enable attack surface reduction rules | Defender for Endpoint: Group Policy
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. For additional information and help recovering missing shortcuts, see Recovering from Attack Surface Reduction rule shortcut deletions (updated on January 17, 2023 to include additional guidance and scripts to help with recovery).
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:\windows\system32\drivers\hidparse.sys C:\windows\system32\hidparse.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 Windows\System32 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
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 -> <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:
- Download for Windows 11, version 22H2 - KB5018427 221029_091533 Known Issue Rollback
- Download for Windows 11, version 21H2 - KB5018483 220927_043051 Known Issue Rollback
- Download for Windows Server 2022 - KB5018485 220927_043049 Known Issue Rollback
- Download for Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2 - KB5018482 220927_043047 Known Issue Rollback
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
Sign in failures and other issues related to Kerberos authentication
| Status | Originating update | History | Resolved | OS Build 19045.2251 KB5019959 2022-11-08 | Resolved: 2022-11-18, 16:22 PT Opened: 2022-11-13, 15:16 PT |
|---|
Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1.
After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:
- Domain user sign in might fail. This also might affect Active Directory Federation Services (AD FS) authentication.
- Group Managed Service Accounts (gMSA) used for services such as Internet Information Services (IIS Web Server) might fail to authenticate.
- Remote Desktop connections using domain users might fail to connect.
- You might be unable to access shared folders on workstations and file shares on servers.
- Printing that requires domain user authentication might fail.
When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1":
While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.
Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.
Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.
Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them.
To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically.
Cumulative updates:
Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
Standalone Updates:
- Windows Server 2012 R2: KB5021653
- Windows Server 2012: KB5021652
- Windows Server 2008 R2 SP1: KB5021651 (released November 18, 2022)
- Windows Server 2008 SP2: KB5021657
Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
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
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 -> <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:
- Download for Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2 - KB5016688 220820_03051 Known Issue Rollback
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
- Server: None
October 2022
Microsoft OneDrive app might unexpectedly close
| Status | Originating update | History | Resolved KB5020953 | OS Build 19045.2130 KB5018410 2022-10-11 | Resolved: 2022-10-28, 14:00 PT Opened: 2022-10-27, 11:54 PT |
|---|
After installing KB5018410 or later updates, OneDrive might unexpectedly close, and you might receive an error when attempting to do the following:
- Sign out or unlink your account in the Microsoft OneDrive sync app.
- Unlink sites or folders from syncing to your device from Microsoft SharePoint or Microsoft Teams sites.
- Uninstalling the OneDrive sync app might fail.
Note: These issues might affect both OneDrive and OneDrive for Business.
Resolution: This issue was resolved in the out-of-band update KB5020953. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB5020953, search for it in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note KB5020953 is not available from Windows Update and will not install automatically.
Affected platforms:
- Client: Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
- Server: None
Possible issues caused by Daylight Savings Time change in Jordan
| Status | Originating update | History | Resolved KB5018482 | N/A | Resolved: 2022-10-25, 14:00 PT Opened: 2022-10-21, 14:34 PT |
|---|
On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone.
The impact of this change is as follows:
- Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone.
- The Jordan time zone will permanently shift to the UTC + 3 time zone.
Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later:
- 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 Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device.
Workaround: You can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022, if an update is not available to resolve this issue for your version of Windows:
- 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”.
Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly.
Resolution: This issue was resolved in KB5018482. Note: KB5018482 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.
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; 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
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.