Resolved issues in Windows 11, version 22H2

Find information on recently resolved issues for Windows 11, 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

SummaryOriginating updateStatusDate resolved
Connections may fail when using Remote Desktop Connection Brokers
Remote Desktop Services collection, RemoteApp, and Desktop Connections are affected
N/A

Resolved
KB5022360
2023-01-26
14:00 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 22621.819
KB5019980
2022-11-08
Resolved
KB5022303
2023-01-10
10:00 PT
Conversion of text in certain languages might not work as expected
Impacted languages include Japanese, Korean, and Chinese
N/A

Resolved
KB5022360
2023-01-26
14:00 PT
Provisioning packages might not work as expected
Windows might only be partially configured, and the Out Of Box Experience might not finish.
N/A

Resolved
KB5020044
2023-01-06
16:58 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 22621.675
KB5019509
2022-10-18
Resolved
KB5021255
2022-12-13
10:00 PT
Lower than expected performance in some games
Some games and apps might inadvertently enable GPU performance debugging features.
N/A

Resolved
KB5020044
2022-11-29
10:00 PT
Task Manager might not display in expected colors
Task Manager should function as expected but some parts of the UI might not be readable.
OS Build 22621.900
KB5020044
2022-11-29
Resolved
KB5021255
2022-12-13
10:00 PT
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
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

January 2023

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

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

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

Conversion of text in certain languages might not work as expected

StatusOriginating updateHistory
Resolved KB5022360N/A

Resolved: 2023-01-26, 14:00 PT
Opened: 2023-01-06, 16:49 PT

When typing in languages that use multibyte character sets - such as Japanese, Korean, and Chinese - operations to convert characters might not function correctly. Text conversion occurs when a series of characters is transformed into different characters by means of user selection. This commonly involves additional Prediction candidate and Conversion candidate windows, which appear near the cursor position while typing.

Symptoms observed can include: 

  1. ​An incorrect range of characters is automatically selected for conversion, resulting in the conversion candidate window displaying unexpected options.
  2. ​The cursor might move to an unexpected position, resulting in the selection of the wrong sequence of characters for conversion. This can cause symptom 1.

Resolution: This issue was resolved in KB5022360.

Affected platforms:

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

December 2022

Database connections using Microsoft ODBC SQL Server driver might fail.

StatusOriginating updateHistory
Resolved KB5022303OS Build 22621.819
KB5019980
2022-11-08
Resolved: 2023-01-10, 10:00 PT
Opened: 2022-12-05, 15:45 PT

After installing KB5019980, 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 KB5022303. 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

November 2022

Connections may fail when using Remote Desktop Connection Brokers

StatusOriginating updateHistory
Resolved KB5022360N/A

Resolved: 2023-01-26, 14:00 PT
Opened: 2022-11-22, 10:47 PT

After installing Windows 11, version 22H2 (also called Windows 11 2022 Update), the Windows Remote Desktop application might stop responding when connecting via a Remote Desktop gateway or Remote Desktop Connection Broker. An example of this connection scenario is when connecting to a Remote Desktop Services collection. RemoteApp and Desktop Connections are ways in which this connection is accomplished.

Home users of Windows are unlikely to experience this issue, as the connection process described here is not the default used by the Windows Remote Desktop app.

This issue can be observed when the client is at the "Loading virtual machine" or "Configuring remote connection" steps, and might occur regardless of the OS version installed on the remote computer. In some cases, the error message "Your Remote Desktop Services session has ended" can appear. If the application becomes unresponsive, it might need to be terminated using Windows Task Manager. See the Workaround section for guidance.

Workaround:

If the Remote Desktop application becomes unresponsive, Windows Task Manager can be used to terminate it.

  • ​Press and hold the Ctrl, Shift, and Esc keys on your keyboard.
  • ​Select Processes from the left-hand side menu
  • ​In the list that appears, find the process mstsc.exe
  • ​Right-click on the process name and select End task

Devices that have encountered this issue can resolve it by configuring a special Group Policy. 

Warning: Remote Desktop sessions which connect over WAN (wide-area network) might experience poor performance following the application of the below workaround. Setting this policy also disables UDP (User Datagram Protocol) for all Remote Desktop connections made from the device. We strongly recommend that this Group Policy change is reverted once this issue is resolved in a future Windows update.
  • ​Open the appropriate Group Policy editor.
    • ​For managed devices (common for enterprises and organizations), open the Group Policy Management Console and create or edit a policy that targets your clients
    • ​For unmanaged devices (common for home users), open the Group Policy Editor. This can be accomplished by opening the Start Menu and typing group policy. Select Edit group policy from the results
  • ​Using the right-side panel, browse to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client
  • ​From the left-side panel, double-click the policy setting Turn Off UDP On Client and set it to Enabled
  • ​Select OK and restart your device(s) to apply the policy setting

Resolution: This issue was resolved in KB5022360.

Affected platforms:

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

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

StatusOriginating updateHistory
Resolved KB5021255OS Build 22621.675
KB5019509
2022-10-18
Resolved: 2022-12-13, 10:00 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: You can mitigate this issue by restarting your Windows device.

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

Lower than expected performance in some games

StatusOriginating updateHistory
Resolved KB5020044N/A

Resolved: 2022-11-29, 10:00 PT
Opened: 2022-11-10, 17:41 PT

Some games and apps might experience lower than expected performance or stuttering on Windows 11, version 22H2. Affected games and apps are inadvertently enabling GPU performance debugging features not meant to be used by consumers.

To safeguard your upgrade experience, we have applied a compatibility hold on devices affected by this issue from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard IDs are 41766570 and 41990091.

Workaround: If you are already on Windows 11, version 22H2 and are experiencing this issue, you might be able to resolve it by updating your games and gaming related apps to the latest version available. If you are unsure how to update the games and apps you have installed, you will need to consult the developer of those games and apps but most will update automatically through the store they were purchased from or directly when opening them.

Resolution: This issue was resolved in  KB5020044 and the safeguard hold has been removed as of December 14, 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

Task Manager might not display in expected colors

StatusOriginating updateHistory
Resolved KB5021255OS Build 22621.900
KB5020044
2022-11-29
Resolved: 2022-12-13, 10:00 PT
Opened: 2022-11-30, 12:29 PT

After installing KB5020044, Task Manager might display certain elements in the user interface (UI) in unexpected colors. On affected devices, Task Manager should function as expected but some parts of the UI might not be readable. You might be affected by this issue if you have "Choose your mode" set to "Custom", in the Personalization -> colors section of Settings. If you are using Dark or Light for the "Choose your mode" setting, you should not be affected by this issue.

Workaround: To mitigate this issue, you can set the "Choose your mode" setting to either Dark or Light until this issue is resolved. To do this, right click or long press on the desktop, select "Personalize", select "Colors", and then select either "Dark" or "Light" for "Choose your mode".

Resolution: This issue was resolved in KB5021255.

Affected platforms:

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

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

October 2022

Provisioning packages might not work as expected

StatusOriginating updateHistory
Resolved KB5020044N/A

Resolved: 2023-01-06, 16:58 PT
Opened: 2022-10-05, 14:17 PT

Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note: Provisioning Windows devices using Windows Autopilot is not affected by this issue.

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

Workaround: If you can provision the Windows device before upgrading to Windows 11, version 22H2, this will prevent the issue.

Resolution: This issue was resolved in KB5020044.

Important: If you are using provisioning packages, please see Some apps might not be installed when using provisioning packages.

Affected platforms:

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

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

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.