Resolved issues in Windows Server 2022

See a list of known issues that have been resolved for Windows Server 2022 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
The September 2022 preview release is listed in Windows Server Update Services
Preview updates are generally made available from the Microsoft Update Catalog and Windows Updates.
N/A

Resolved
KB5018421
2022-10-11
10: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
KB5018485
2022-10-25
14:00 PT
SSL/TLS handshake might fail
We have received reports that some types of SSL and TLS connections might have handshake failures.
OS Build 20348.1129
KB5018421
2022-10-11
Resolved
KB5020436
2022-10-17
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.
OS Build 20348.1006
KB5017316
2022-09-13
Resolved
KB5018421
2022-10-11
10:00 PT
Possible issues caused by new Daylight Savings Time in Chile
Chilean government announced a Daylight Saving Time (DST) change for 2022.
N/A

Resolved
KB5017381
2022-09-20
10:00 PT
IE mode tabs in Microsoft Edge might stop responding
When a site is viewed in IE mode in Edge and the site uses certain calls, all IE mode tabs might stop responding.
OS Build 20348.740
KB5014021
2022-05-24
Resolved
KB5016693
2022-08-16
14:00 PT
PowerShell Desired State Configuration resources might fail to apply successfully
DSC resources in environments which require the PSCredential property might fail.
OS Build 20348.768
KB5014678
2022-06-14
Resolved
KB5015827
2022-07-12
10:00 PT
Unable to connect to internet when using Wi-Fi hotspot feature
After installing updates released June 14, 2022, you might have issues using Wi-Fi hotspot on Windows device.
OS Build 20348.768
KB5014678
2022-06-14
Resolved
KB5014665
2022-06-23
14:00 PT
RRAS Servers can lose connectivity if NAT is enabled on the public interface
Devices which connect to the server can also fail to connect to the internet
OS Build 20348.768
KB5014678
2022-06-14
Resolved
KB5014665
2022-06-23
14:00 PT
You might see authentication failures on the server or client for services
Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, and other services might fail.
OS Build 20348.707
KB5013944
2022-05-10
Resolved
KB5015013
2022-05-19
14:00 PT

Issue details

October 2022

Possible issues caused by Daylight Savings Time change in Jordan

StatusOriginating updateHistory
Resolved KB5018485N/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 KB5018485. Note: KB5018485 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

SSL/TLS handshake might fail

StatusOriginating updateHistory
Resolved KB5020436OS Build 20348.1129
KB5018421
2022-10-11
Resolved: 2022-10-17, 14:00 PT
Opened: 2022-10-11, 19:31 PT

Microsoft has received reports that after installing KB5018421, 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 the out-of-band update KB5020436. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB5020436, 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 KB5020436 is not available from Windows Update and will not install automatically.

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

September 2022

The September 2022 preview release is listed in Windows Server Update Services

StatusOriginating updateHistory
Resolved KB5018421N/A

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

IT administrators who utilize Windows Server Update Services (WSUS) might notice that the Windows September 2022 preview update, known as the 'C' release, is listed among the updates available from WSUS. This listing is an error. Preview updates are generally available for manual importing via the Microsoft Update Catalog and Windows Updates.

This issue might also affect the installation of the September 2022 Cumulative Update Preview for .NET Framework, which is also generally available via Windows Update and Microsoft Update Catalog. For more information on .NET Framework September 2022 Cumulative Update Preview updates, see the KB articles listed on the .NET blog for the September 2022 Cumulative Update Preview.

Home users of Windows are unlikely to experience this issue. WSUS is commonly utilized by technology administrators to deploy Microsoft product updates in managed environments. 

Workaround: The Windows September 2022 preview release was made available via Microsoft Update Catalog. We recommend IT administrators to use this release channel moving forward.

Please note: In environments where WSUS is configured to auto-approve updates and also auto-decline superseded content, the Windows September 2022 Security update may subsequently be auto-declined and auto-expired from the client view. If this occurs, see the guidance for reinstating declined updates. Then run an update synchronization within Microsoft Endpoint Configuration Manager, or update management environments. Environments configured to only take security updates should not reflect these symptoms.

Resolution: The Windows September 2022 preview release was removed from WSUS. We recommend IT administrators use the Microsoft Update Catalog to download and install updates in their environments. As always, we recommend the installation of the latest Windows security updates for all devices (the October 2022 security monthly release, KB5018421, or later).

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 11, version 21H1; Windows 10, version 20H2; Windows 10, version 1809
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809

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

StatusOriginating updateHistory
Resolved KB5018421OS Build 20348.1006
KB5017316
2022-09-13
Resolved: 2022-10-11, 10:00 PT
Opened: 2022-09-22, 15:23 PT

After installing KB5017316, 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 KB5018421. Installation of KB5018421 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

Possible issues caused by new Daylight Savings Time in Chile

StatusOriginating updateHistory
Resolved KB5017381N/A

Resolved: 2022-09-20, 10:00 PT
Opened: 2022-09-02, 13:17 PT

Starting at 12:00 a.m. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by Chilean government about a Daylight Saving Time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

  • ​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 Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

Workaround: This issue is now resolved in KB5017381 but you should undo the workaround, if it is still being used.

You can mitigate this issue on devices in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:

  • ​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”.

To mitigate this issue in the Santiago time zone, after 12:00 a.m. on September 11, 2022, and for those in the Easter Islands time zone, after 10:00 p.m. on September 10, 2022, follow the steps below to re-enable automatic DST adjustments and ensure accurate time switching with future DST transitions. This can be done by doing either of the following:

  • ​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 On.
  • ​Go to Control Panel > Clock and Region > Date and Time > Change time zone and check 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 Chile. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if not done correctly.

Resolution: This issue was resolved in KB5017381. Note: If the workaround above was used, it should have been undone on September 11, 2022. Installation of KB5017381 will not change the "Automatically adjust clock for Daylight Saving Time" setting.

Affected platforms:

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

July 2022

PowerShell Desired State Configuration resources might fail to apply successfully

StatusOriginating updateHistory
Resolved KB5015827OS Build 20348.768
KB5014678
2022-06-14
Resolved: 2022-07-12, 10:00 PT
Opened: 2022-07-19, 17:55 PT

After installing updates released June 14, 2022, or later ( KB5014678), PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to: “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”. Note: Environments which use non-encrypted PSCredential properties will not experience the issue.

DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows.

Resolution: This issue was resolved in KB5015827.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2016

June 2022

IE mode tabs in Microsoft Edge might stop responding

StatusOriginating updateHistory
Resolved KB5016693OS Build 20348.740
KB5014021
2022-05-24
Resolved: 2022-08-16, 14:00 PT
Opened: 2022-06-24, 19:21 PT

After installing KB5014021 and later updates, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box which requires the user to respond before continuing or interacting with other portions of the webpage or app. Developer Note: Sites affected by this issue call window.focus.

Resolution: This issue was resolved in KB5016693.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: Windows Server 2022

Unable to connect to internet when using Wi-Fi hotspot feature

StatusOriginating updateHistory
Resolved KB5014665OS Build 20348.768
KB5014678
2022-06-14
Resolved: 2022-06-23, 14:00 PT
Opened: 2022-06-16, 14:12 PT

After installing KB5014678, Windows devices might be unable to use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects.

Workaround: To mitigate the issue and restore internet access on the host device, you can disable the Wi-Fi hotspot feature. For instructions, please see Use your Windows PC as a mobile hotspot.

Resolution: This issue was resolved in KB5014665.

Affected platforms:

  • ​​Client: 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, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

RRAS Servers can lose connectivity if NAT is enabled on the public interface

StatusOriginating updateHistory
Resolved KB5014665OS Build 20348.768
KB5014678
2022-06-14
Resolved: 2022-06-23, 14:00 PT
Opened: 2022-06-24, 16:48 PT

After installing KB5014678, Windows Servers which are using the Routing and Remote Access Service (RRAS) might be unable to correctly direct internet traffic. Devices which connect to the server might fail to connect to the internet, and servers can lose connection to the internet after a client device connects.

Workaround: This issue is resolved in the latest Windows security update. If it's not possible to install the latest Windows updates on an affected server, the issue can be avoided by temporarily disabling the NAT feature on the RRAS server. For steps and guidance on this, note the ability to uncheck the "Enable NAT on this interface" option described on step 7 of the article Enable and Configure NAT.

Resolution: This issue was resolved in KB5014665, and updates released June 23, 2022 or later. We recommend you install the latest security update for your device.

Affected platforms:

  • ​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

May 2022

You might see authentication failures on the server or client for services

StatusOriginating updateHistory
Resolved KB5015013OS Build 20348.707
KB5013944
2022-05-10
Resolved: 2022-05-19, 14:00 PT
Opened: 2022-05-11, 18:38 PT

Resolution guidance updated May 27, 2022

After installing updates released May 10, 2022 on your domain controllers, you might see machine certificate authentication failures on the server or client for services such as Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, Extensible Authentication Protocol (EAP), and Protected Extensible Authentication Protocol (PEAP). An issue has been found related to how the mapping of certificates to machine accounts is being handled by the domain controller.

Note: Installation of updates released May 10, 2022, on client Windows devices and non-domain controller Windows Servers will not cause this issue. This issue only affects installation of May 10, 2022, updates installed on servers used as domain controllers.

Workaround: The preferred mitigation for this issue is to manually map certificates to a machine account in Active Directory. For instructions, please see Certificate Mapping. Note: The instructions are the same for mapping certificates to user or machine accounts in Active Directory. If the preferred mitigation will not work in your environment, please see KB5014754—Certificate-based authentication changes on Windows domain controllers for other possible mitigations in the SChannel registry key section. Note: Any other mitigation except the preferred mitigations might lower or disable security hardening.

Resolution: This issue was resolved in out-of-band updates released May 19, 2022 for installation on all Domain Controllers in your environment, as well as all intermediary application servers such as Network Policy Servers (NPS), RADIUS, Certification Authority (CA), or web servers which passes the authentication certificate from the client being authenticated to the authenticating DC. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. This includes the removal of the registry key (CertificateMappingMethods = 0x1F) documented in the SChannel registry key section of KB5014754. There is no action needed on the client side to resolve this authentication issue.

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 May 10, 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 May 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 May 10, 2022 to receive the quality updates for May 2022. If you have already installed updates released May 10, 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 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2