Resolved issues in Windows 11, version 22H2

See a list of known issues that have been resolved for Windows 11, version 22H2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate resolved
Changing IME input modes might cause applications to become unresponsive
Keyboard shortcuts might cause a limited set of applications to stop responding
N/A

Resolved
KB5020044
2022-11-29
10:00 PT
Audio might be out of Sync when capturing video via Xbox Game Bar
The Xbox Game Bar app might have issues in which the audio is out of sync when capturing gameplay.
N/A

Resolved
KB5018496
2022-10-25
14:00 PT
Some installed printers might only allow default settings
Some printers might not have all features available, such as color, 2-sided printing, or high res.
N/A

Resolved
2022-11-18
17:24 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 22621.819
KB5019980
2022-11-08
Resolved
2022-11-18
16:22 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 or access points.
OS Build 22621.675
KB5019509
2022-10-18
Resolved
2022-11-13
15:34 PT
SSL/TLS handshake might fail
We have received reports that some types of SSL and TLS connections might have handshake failures.
OS Build 22621.674
KB5018427
2022-10-11
Resolved
KB5018496
2022-10-25
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
KB5018496
2022-10-25
14:00 PT
Copying files/shortcuts using Group Policy Preferences might not work as expected
Files or shortcuts might not copy or copy as zero-byte files when using Group Policy Preferences on client devices.
N/A

Resolved
KB5018427
2022-10-11
10:00 PT
Signing in using Windows Hello might not work after upgrade
Windows Hello using face, fingerprint or PIN might be affected.
N/A

Resolved
KB5017389
2022-09-30
14:00 PT

Issue details

November 2022

Changing IME input modes might cause applications to become unresponsive

StatusOriginating updateHistory
Resolved KB5020044N/A

Resolved: 2022-11-29, 10:00 PT
Opened: 2022-11-18, 14:07 PT

After installing Windows 11, version 22H2 (also called Windows 11 2022 Update), certain applications may become unresponsive when keyboard shortcuts are used to turn on/off or change IME (Input Method Editor) input modes.

Examples of actions that can cause this issue:

  • ​For Japanese:
    • ​Using the Hankaku/Zenkaku (半角 / 全角) key on a Japanese keyboard
    • ​Using the default keyboard shortcut: holding down the Alt key and pressing ~ (tilde)
  • ​For Chinese:
    • ​Using the default keyboard shortcut: holding down the Control key and pressing Space
  • ​For Korean:
    • ​Using the default keyboard shortcut: pressing down the right Alt key

It is possible this issue will occur silently, and not result in the display of any error messages.

This issue is observed for applications which load certain components of the Text Services Framework (TSF). Only some applications do this, not all. Applications which don't load these components should not experience this issue, and are expected to function normally when keyboard shortcuts are used.

Workaround: Changing input mode by clicking the IME mode icon in the taskbar should not trigger this issue. This issue occurs only when using keyboard shortcuts.

Resolution: This issue was resolved in updates released November 29, 2022 ( KB5020044) and later. We recommend you install the latest security update for your device.

Affected platforms:

  • ​Client: Windows 11, version 22H2

Audio might be out of Sync when capturing video via Xbox Game Bar

StatusOriginating updateHistory
Resolved KB5018496N/A

Resolved: 2022-10-25, 14:00 PT
Opened: 2022-11-03, 18:31 PT

The Xbox Game Bar app might have issues in which the audio is out of sync when capturing gameplay to a video file. You are more likely to encounter this issue when using the "Record last 30 seconds" feature when “Record in the background while I’m playing game” is enabled in Xbox Game Bar. Developer Note: Apps which capture or process video files using the same underlying Windows libraries or APIs as Xbox Game Bar might also be affected by this issue.

To safeguard your upgrade experience, we have applied a compatibility hold on devices which have previously used the capture feature in the Xbox Game Bar app from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 41584256. 

Resolution: This issue was resolved in  KB5018496 and the safeguard hold has been removed as of November 10, 2022. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 22H2 is offered.

Affected platforms:

  • ​Client: Windows 11, version 22H2
  • ​Server: None

Sign in failures and other issues related to Kerberos authentication

StatusOriginating updateHistory
ResolvedOS Build 22621.819
KB5019980
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:

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:

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

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

StatusOriginating updateHistory
ResolvedOS Build 22621.675
KB5019509
2022-10-18
Resolved: 2022-11-13, 15:34 PT
Opened: 2022-11-13, 14:49 PT

After installing KB5019509 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: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that 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>.

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

SSL/TLS handshake might fail

StatusOriginating updateHistory
Resolved KB5018496OS Build 22621.674
KB5018427
2022-10-11
Resolved: 2022-10-25, 14:00 PT
Opened: 2022-10-11, 19:31 PT

Microsoft has received reports that after installing KB5018427, some types of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) connections might have handshake failures. Note for developers: Affected connections are likely to be sending multiple frames within a single input buffer, specifically one or more complete records with a partial record that is less than 5 bytes all sent in a single buffer. When this issue is encountered, your app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails.

If you are experiencing issues, please use feedback hub to file a report following the below steps:

  1. ​Launch Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F
  2. ​Fill in the "Summarize your feedback" and "Explain in more detail" boxes, then click Next.
  3. ​Under the "Choose a category" section, ensure the "Problem" button, "Devices and Drivers" category, and "Print" subcategory are all selected. Click Next.
  4. ​Under the "Find similar feedback" section, select the "Make new bug" radio button and click Next.
  5. ​Under the "Add more details" section, supply any relevant detail (Note this is not critical to addressing your issue).
  6. ​Expand the "Recreate my problem" box and press "Start recording". Reproduce the issue on your device.
  7. ​Press "Stop recording" once finished. Click the "Submit" button.

For additional information, see Send feedback to Microsoft with the Feedback Hub app.

Resolution: This issue was resolved in KB5018496. Note: KB5018496 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 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

Possible issues caused by Daylight Savings Time change in Jordan

StatusOriginating updateHistory
Resolved KB5018496N/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: 

  1. ​Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone. 
  2. ​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 KB5018496. Note: KB5018496 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

Signing in using Windows Hello might not work after upgrade

StatusOriginating updateHistory
Resolved KB5017389N/A

Resolved: 2022-09-30, 14:00 PT
Opened: 2022-10-10, 14:36 PT

Signing in using Windows Hello might not work as expected after upgrading to Windows 11, version 22H2 on devices using Windows Hello Enhanced Sign-in Security. Windows Hello using face, fingerprint or PIN might be affected. This issue might be encountered on devices which already have Windows Hello when upgrading but should not happen on devices which enable Windows Hello after upgrading or installing Windows 11, version 22H2.

To safeguard your upgrade experience, we have applied a compatibility hold on devices using Windows Hello Enhanced Sign-in Security from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 40667045. 

Workaround: If you upgraded to Windows 11, version 22H2 and are unable to sign-in using Windows Hello, you can sign-in using the password for your user.

Resolution: This issue was resolved in KB5017389. The safeguard hold is estimated to be removed in mid-October 2022.

Note We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. 

Affected platforms:

  • ​Client: Windows 11, version 22H2
  • ​Server: None

September 2022

Some installed printers might only allow default settings

StatusOriginating updateHistory
ResolvedN/A

Resolved: 2022-11-18, 17:24 PT
Opened: 2022-09-29, 17:41 PT

Microsoft has found an issue when an installed printer uses Microsoft IPP Class Driver or Universal Print Class Driver and is installed on a Windows device with connectivity issues to the printer. Windows needs connectivity to the printer to identify all the features of the printer. Without connectivity, the printer is set up with default settings and in some scenarios might not get updated once connectivity to the printer is restored. You might be affected by this issue if your printer is unable to use printer specific features such as color, two-sided/duplex printing, paper size or type settings, or resolutions higher than 300x300dpi. Currently, installed printers in this state will carry this issue forward when upgraded to Windows 11, version 22H2. 

To safeguard your upgrade experience, we have applied a compatibility hold on Windows devices with printers using Microsoft IPP Class Driver or Universal Print Class Driver from being offered Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 41332279. 

Workaround: If you have an affected installed printer, you can use the below workarounds or wait for your device to be mitigated automatically. A troubleshooter has been released which will automatically download and resolve this issue on affected devices. Restarting your device and checking for updates might help the troubleshooter apply sooner. For more information, see keeping your device running smoothly with recommended troubleshooting.

To mitigate the safeguard manually and allow your Windows device to upgrade to Windows 11, version 22H2, you can remove or remove and reinstall any printers using Microsoft IPP Class Driver or Universal Print Class Driver which you have installed. Once you have removed any affected installed printers, you should be able to upgrade to Windows 11, version 22H2. For instructions on how to remove and reinstall printers, please see Download printer drivers in Windows.

Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Restarting your device and checking for updates might help it to offer sooner. 

Resolution: This issue was resolved, and the safeguard hold has been removed as of November 10, 2022. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 22H2 is offered. 

Important Notes:

  • November 10, 2022: Any printer still affected by this issue should now get resolved automatically during upgrade to Windows 11, version 22H2.
  • October 21, 2022: A troubleshooter has been released which will automatically download and resolve this issue on affected devices running Windows 11, version 22H2. Once the issue with the installed printer is resolved, the safeguard should be removed and you should be able to upgrade to Windows 11, version 22H2. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Restarting your device and checking for updates might help the troubleshooter apply sooner. For more information, see keeping your device running smoothly with recommended troubleshooting.
  • October 7, 2022: This safeguard hold has been updated to only safeguard Windows devices with printers using Microsoft IPP Class Driver or Universal Print Class Driver which currently only allow default settings. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Restarting your device and checking for updates might help it to offer sooner.

Affected platforms: 

  • ​Client: Windows 11, version 22H2

Copying files/shortcuts using Group Policy Preferences might not work as expected

StatusOriginating updateHistory
Resolved KB5018427N/A

Resolved: 2022-10-11, 10:00 PT
Opened: 2022-09-22, 15:23 PT

After installing , file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration -> Preferences -> Windows Settings in Group Policy Editor.

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

  • ​Uncheck the "Run in logged-on user's security context (user policy option)". Note: This might not mitigate the issue for items using a wildcard (*).
  • ​Within the affected Group Policy, change "Action" from "Replace" to "Update".
  • ​If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotes) from the destination might allow the copy to be successful.

Resolution: This issue was resolved in KB5018427. Installation of KB5018427 prevents and resolves this issue but if any workaround was used to mitigate this issue, it will need to be changed back to your original configuration.

Affected platforms:

  • ​Client: Windows 11, 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
  • ​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