Windows 10, version 2004 and Windows Server, version 2004

Find information on known issues and the status of the rollout for Windows 10, version 2004 and Windows Server, version 2004. 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 February 3, 2021
Windows 10, version 2004 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
    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 19041.1266
    KB5005611
    2021-09-30
    Resolved
    2021-10-15
    17:20 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 19041.1237
    KB5005565
    2021-09-14
    Resolved
    KB5006670
    2021-10-12
    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 19041.1266
    KB5005611
    2021-09-30
    Resolved
    KB5006670
    2021-10-12
    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 19041.1237
    KB5005565
    2021-09-14
    Confirmed
    2021-10-14
    19:57 PT
    Apps might fail to open, close unexpectedly or become unresponsive
    Devices using Microsoft Exploit Protection Export Address Filtering (EAF) might have issues with some apps.
    OS Build 19041.1202
    KB5005101
    2021-09-01
    Resolved
    KB5006670
    2021-10-12
    10:00 PT
    Installation of printers might fail when attempted over some network connections
    This issue has been observed in devices which access printers via a print server using HTTP connections
    OS Build 19041.1237
    KB5005565
    2021-09-14
    Resolved
    KB5005611
    2021-09-30
    14:00 PT
    Administrator credentials required every time apps attempt to print
    Certain printers in some environments using Point and Print might prompt for credentials every time when printing.
    OS Build 19041.1165
    KB5005033
    2021-08-10
    Resolved External
    2021-09-16
    18:23 PT

    Issue details

    October 2021

    Smartcard authentication might fail when attempting to connect using Remote Desktop

    StatusOriginating updateHistory
    ResolvedOS Build 19041.1266
    KB5005611
    2021-09-30
    Resolved: 2021-10-15, 17:20 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.

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

    StatusOriginating updateHistory
    Resolved KB5006670OS Build 19041.1237
    KB5005565
    2021-09-14
    Resolved: 2021-10-12, 10:00 PT
    Opened: 2021-10-15, 17:21 PT
    After installing KB5005565 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.

    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
    Resolution: This issue was resolved in KB5006670. If after installing KB5006670 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).

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

    StatusOriginating updateHistory
    Resolved KB5006670OS Build 19041.1266
    KB5005611
    2021-09-30
    Resolved: 2021-10-12, 10:00 PT
    Opened: 2021-10-13, 12:28 PT
    After installing KB5005611 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 KB5005611 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. 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 was resolved in  KB5006670.

    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
    ConfirmedOS Build 19041.1237
    KB5005565
    2021-09-14
    Last updated: 2021-10-14, 19:57 PT
    Opened: 2021-10-13, 12:32 PT
    After installing KB5005565, 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 KB5005565 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.

    Next steps: Microsoft is working on a resolution and targeting its release in a future update.

    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

    Installation of printers might fail when attempted over some network connections

    StatusOriginating updateHistory
    Resolved KB5005611OS Build 19041.1237
    KB5005565
    2021-09-14
    Resolved: 2021-09-30, 14:00 PT
    Opened: 2021-10-13, 12:26 PT
    After installing KB5005565, devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers. Devices which had connected to and installed the printer prior to the installation of KB5005565 are unaffected and operations to that printer will succeed as usual.

    This issue has been observed in devices which access printers via a print server using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download.

    Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. 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. Only the automatic download and installation processes are impacted by this issue.

    Resolution: This issue was resolved in  KB5005611.

    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

    September 2021

    Apps might fail to open, close unexpectedly or become unresponsive

    StatusOriginating updateHistory
    Resolved KB5006670OS Build 19041.1202
    KB5005101
    2021-09-01
    Resolved: 2021-10-12, 10:00 PT
    Opened: 2021-09-24, 11:00 PT
    After installing KB5005101 or a later update on devices using Microsoft Exploit Protection Export Address Filtering (EAF), you might have issues with some applications. You might be experiencing this issue if apps fail to open, fail to open files, or you might receive a white window when attempting to login.

    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 Enterprise LTSC 2019
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019
    Resolution: This issue was resolved in KB5006670, released October 12, 2021. If you install an update released October 12, 2021 ( KB5006670) 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 October 12, 2021, you can resolve this issue using KIR. 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 (preferred) or setting a registry key according to the version of Windows you are using. Important Verify that you are using the correct Group Policy or registry key for your version of Windows.

    Group Policy (preferred):
    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. Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. 

    Registry Key:
    1, Open a Command Prompt window (cmd.exe) with elevated permissions.
    2, Type the following command depending on which Windows version you are using and then press Enter.
    Windows Sever 2022:
    reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2801335948 /t REG_DWORD /d 0 /f
     
    Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1:
    reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2767781516 /t REG_DWORD /d 0 /f
     
    Windows 10, version 1909:
    reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 928713355 /t REG_DWORD /d 0 /f
     
    Windows 10, version 1809, Windows Server 2019:
    reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2371422858 /t REG_DWORD /d 0 /f
    

    3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt:
    Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask


    Administrator credentials required every time apps attempt to print

    StatusOriginating updateHistory
    Resolved ExternalOS Build 19041.1165
    KB5005033
    2021-08-10
    Last updated: 2021-09-16, 18:23 PT
    Opened: 2021-09-16, 18:11 PT
    After installing KB5005033 or a later update, certain printers in some environments using Point and Print might receive a prompt saying, "Do you trust this printer" and requiring administrator credentials to install every time an app attempts to print to a print server or a print client connects to a print server. This is caused by a print driver on the print client and the print server using the same filename, but the server has a newer version of the file. When the print client connects to the print server, it finds a newer driver file and is prompted to update the drivers on the print client, but the file in the package it is offered for installation does not include the later file version.

    Workaround: Verify that you are using the latest drivers for all your printing devices and where possible, use the same version of the print driver on the print client and print server.

    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 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
    Resolution: This issue is resolved externally by adjusting the print drivers in your environment. If updating drivers in your environment does not resolve the issue, please contact support for your printer manufacturer (OEM). For more information, see the Q1/A1 in the "Frequently asked questions" section of KB5005652.