Windows 10, version 20H2 and Windows Server, version 20H2

Find information on known issues and the status of the rollout for Windows 10, version 20H2 and Windows Server, version 20H2. 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 May 18, 2021
Windows 10, version 20H2 is designated for broad deployment. The recommended servicing status is Semi-Annual Channel.

    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
    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 19042.1288
    KB5006670
    2021-10-12
    Resolved
    KB5007253
    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 19042.1348
    KB5007186
    2021-11-09
    Resolved
    KB5007253
    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 19042.1266
    KB5005611
    2021-09-30
    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 19042.1288
    KB5006670
    2021-10-12
    Resolved
    KB5007186
    2021-11-09
    10:00 PT

    Issue details

    November 2021

    Microsoft Installer might have issues updating or repairing apps

    StatusOriginating updateHistory
    Resolved KB5007253OS Build 19042.1348
    KB5007186
    2021-11-09
    Resolved: 2021-11-22, 14:00 PT
    Opened: 2021-11-18, 10:34 PT
    After installing KB5007186 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 KB5007253. 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 KB5007186OS Build 19042.1288
    KB5006670
    2021-10-12
    Resolved: 2021-11-09, 10:00 PT
    Opened: 2021-11-05, 17:58 PT
    After installing KB5006670 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 KB5007186.

    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 KB5007253OS Build 19042.1288
    KB5006670
    2021-10-12
    Resolved: 2021-11-22, 14:00 PT
    Opened: 2021-10-29, 11:15 PT
    After installation of KB5006670, 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 KB5006670.
    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 KB5007253.

    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 19042.1266
    KB5005611
    2021-09-30
    Resolved: 2021-11-22, 13:13 PT
    Opened: 2021-10-15, 17:20 PT
    After installing KB5005611 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.