Windows Server 2022

Find information on known issues and the status of the rollout for Windows Server 2022. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

Current status as of September 1, 2021
Windows Server 2022 is now available. If you are a Volume License customer, check the Volume Licensing Service Center. To download a free 180-day evaluation, visit the Microsoft Evaluation Center.

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast updated
Microsoft Defender for Endpoint might fail to start or run.
Microsoft Defender for Endpoint might fail to run on devices with a Windows Server Core installation.
OS Build 20348.350
KB5007205
2021-11-09
Confirmed
2021-11-24
13:32 PT
Connections to printers shared via print server might encounter errors
This issue is observed when print clients try to connect to a remote printer shared on a print server
OS Build 20348.288
KB5006699
2021-10-12
Resolved
KB5007254
2021-11-22
14:00 PT
Microsoft Installer might have issues updating or repairing apps
Affected apps might fail to open after an update or repair has been attempted.
OS Build 20348.350
KB5007205
2021-11-09
Resolved
KB5007254
2021-11-22
14:00 PT
Smartcard authentication might fail when attempting to connect using Remote Desktop
Devices attempting to make Remote Desktop connections to devices in untrusted domains might be unable to connect.
OS Build 20348.261
KB5005619
2021-09-27
Resolved
2021-11-22
13:13 PT
UI elements and drawing within some apps may not work as expected
Some apps using GDI+ might have issues with scaling within the app or when used on high DPI or resolution displays.
OS Build 20348.288
KB5006699
2021-10-12
Resolved
KB5007205
2021-11-09
10:00 PT
Receiving a prompt for administrative credentials every time you attempt to print
This issue affects devices in environments in which the print server and print client are in different times zones.
OS Build 20348.230
KB5005575
2021-09-14
Resolved
KB5006745
2021-10-26
10:00 PT
Custom printing properties might not be correctly provided to print server clients
This issue will not cause printing operations to fail, but clients might print with default settings only
OS Build 20348.261
KB5005619
2021-09-27
Resolved
KB5006745
2021-10-26
10:00 PT
Installation of printers via Internet Printing Protocol (IPP) might not succeed
Affects organizations that share an IPP printer using printer connections
OS Build 20348.230
KB5005575
2021-09-14
Resolved
KB5006745
2021-10-26
10:00 PT

Issue details

November 2021

Microsoft Defender for Endpoint might fail to start or run.

StatusOriginating updateHistory
ConfirmedOS Build 20348.350
KB5007205
2021-11-09
Last updated: 2021-11-24, 13:32 PT
Opened: 2021-11-24, 13:32 PT
After installing KB5007205 or later updates, Microsoft Defender for Endpoint might fail to start or run on devices with a Windows Server Core installation. Note: This issue does not affect Microsoft Defender for Endpoint on Windows 10.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Affected platforms:
  • Client: None
  • Server: Windows Server 2022; Windows Server 2019

Microsoft Installer might have issues updating or repairing apps

StatusOriginating updateHistory
Resolved KB5007254OS Build 20348.350
KB5007205
2021-11-09
Resolved: 2021-11-22, 14:00 PT
Opened: 2021-11-18, 10:34 PT
After installing KB5007205 or later updates, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted.

Workaround: To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app.

Resolution: This issue was resolved in KB5007254. This update should prevent the issue from occurring again, but you might need to reinstall affected apps, if they will not open.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; 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 2004; 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

UI elements and drawing within some apps may not work as expected

StatusOriginating updateHistory
Resolved KB5007205OS Build 20348.288
KB5006699
2021-10-12
Resolved: 2021-11-09, 10:00 PT
Opened: 2021-11-05, 17:58 PT
After installing KB5006699 or a later update, certain apps might have unexpected results when rendering some user interface elements or when drawing within the app. You might encounter this issue with apps that use GDI+ and set a zero (0) width pen object on displays with high dots per inch (DPI) or resolution, or if the app is using scaling.

Resolution: This issue was resolved in KB5007205.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; 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 2004; 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

October 2021

Connections to printers shared via print server might encounter errors

StatusOriginating updateHistory
Resolved KB5007254OS Build 20348.288
KB5006699
2021-10-12
Resolved: 2021-11-22, 14:00 PT
Opened: 2021-10-29, 11:15 PT
After installation of KB5006699, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
  • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
  • 0x0000007c (ERROR_INVALID_LEVEL)
  • 0x00000709 (ERROR_INVALID_PRINTER_NAME)
Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
 
Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
 
  • Print clients must have installed a Windows update released on or after January 2021 before the print server has installed KB5006699.
Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
  • Default start port: 49152
  • Default end port: 65535
  • Port Range: 16384 ports
Please refer to these articles for further guidance:
You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect.
 
Resolution: This issue was resolved in KB5007254.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; 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 2004; 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

Smartcard authentication might fail when attempting to connect using Remote Desktop

StatusOriginating updateHistory
ResolvedOS Build 20348.261
KB5005619
2021-09-27
Resolved: 2021-11-22, 13:13 PT
Opened: 2021-10-15, 17:20 PT
After installing KB5005619 or later updates, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004
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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.

Group Policy installation files:
Important Verify that you are using the correct Group Policy for your version of Windows.

Receiving a prompt for administrative credentials every time you attempt to print

StatusOriginating updateHistory
Resolved KB5006745OS Build 20348.230
KB5005575
2021-09-14
Resolved: 2021-10-26, 10:00 PT
Opened: 2021-10-15, 17:21 PT
After installing KB5005575 or later updates, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones.

Note: The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

Resolution: This issue has been resolved in KB5006745. If after installing KB5006745 you still receive the prompt every time you print, see Q1 in the "Frequently ask questions" section of KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481).

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; 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 2004; 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

Custom printing properties might not be correctly provided to print server clients

StatusOriginating updateHistory
Resolved KB5006745OS Build 20348.261
KB5005619
2021-09-27
Resolved: 2021-10-26, 10:00 PT
Opened: 2021-10-14, 18:15 PT
After installing KB5005619 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only.

This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who have previously received the settings package prior to the installation of KB5005619 are unaffected. Servers which use default print settings and have no custom settings to provide to clients are unaffected.

Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Additionally, clients can still be modified manually to adopt desired printer settings.

Resolution: This issue has been resolved in KB5006745.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

Installation of printers via Internet Printing Protocol (IPP) might not succeed

StatusOriginating updateHistory
Resolved KB5006745OS Build 20348.230
KB5005575
2021-09-14
Resolved: 2021-10-26, 10:00 PT
Opened: 2021-10-13, 12:32 PT
After installing KB5005575, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005575 are unaffected and print operations to that printer will succeed as usual.

Note: IPP is not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

Resolution: This issue has been resolved in KB5006745.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1809; Windows 11, version 21H2; Windows 10, version 1909
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1809; Windows Server 2022; Windows Server, version 1909