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.
Windows 10, version 21H1 is now available Windows 10, version 21H1 is now available
Find out how to get the update >
IT tools for Windows 10, version 21H1 IT tools for Windows 10, version 21H1
Explore the latest tools and resources to support your rollout >

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
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
2021-09-24
11:22 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
Automatic input of Furigana might not work as expected
In certain circumstances, the automatic Furigana input/conversion feature may not work as expected in apps.
N/A

Resolved
KB5005101
2021-09-01
14:00 PT

Issue details

September 2021

Apps might fail to open, close unexpectedly or become unresponsive

StatusOriginating updateHistory
ResolvedOS Build 19041.1202
KB5005101
2021-09-01
Resolved: 2021-09-24, 11:22 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 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 (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.

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


Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. 

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.

December 2020

Automatic input of Furigana might not work as expected

StatusOriginating updateHistory
Resolved KB5005101N/A

Resolved: 2021-09-01, 14:00 PT
Opened: 2020-12-03, 12:29 PT
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allow the input of Furigana characters, you might not get the correct Furigana characters and might need to enter them manually. Note for developers: Affected apps are using the ImmGetCompositionString function.

Workaround: To mitigate this issue, please follow the instructions in Revert to a previous version of an IME (Input Method Editor).

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
Resolution: This issue was resolved in KB5005101. If you have used the above mitigation, you will need to change your IME back to the latest version of Microsoft Japanese IME.