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.

The Windows release health hub is always evolving. Take our short survey and let us know how we can improve.

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
Printing and scanning might fail when these devices use smart-card authentication
Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication.
OS Build 19041.1110
KB5004237
2021-07-13
Confirmed
2021-07-23
15:51 PT
Certain printers unable to print
Most affected printers are receipt or label printers that connect via USB.
OS Build 19041.1081
KB5003690
2021-06-21
Resolved
KB5004237
2021-07-13
10:00 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

Mitigated
2021-05-18
10:21 PT

Issue details

July 2021

Printing and scanning might fail when these devices use smart-card authentication

StatusOriginating updateHistory
ConfirmedOS Build 19041.1110
KB5004237
2021-07-13
Last updated: 2021-07-23, 15:51 PT
Opened: 2021-07-23, 14:36 PT
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication.

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, 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
Next steps: For more information on this issue, please see KB5005408 - Smart-card authentication might cause print and scan failures.

Certain printers unable to print

StatusOriginating updateHistory
Resolved KB5004237OS Build 19041.1081
KB5003690
2021-06-21
Resolved: 2021-07-13, 10:00 PT
Opened: 2021-07-08, 16:40 PT
After installing KB5003690 or later updates (including out of band updates, KB5004760 and KB5004945), you might have issues printing to certain printers. Various brands and models are affected, primarily receipt or label printers that connect via USB.

Note This issue is not related to CVE-2021-34527 or CVE-2021-1675.

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 KB5004237, released July 13, 2021. If you are using an update released before July 13, 2021, you can resolve this issue 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. 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.

Important If you install an update released July 13, 2021 ( KB5004237) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue.

December 2020

Automatic input of Furigana might not work as expected

StatusOriginating updateHistory
MitigatedN/A

Last updated: 2021-05-18, 10:21 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
Next steps: We are working on a resolution and will provide an update in an upcoming release.