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
Find out how to get the update >
|IT tools for Windows 10, version 21H1
Explore the latest tools and resources to support your rollout >
|Summary||Originating update||Status||Last 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|
|Certain printers unable to print|
Most affected printers are receipt or label printers that connect via USB.
|OS Build 19041.1081|
|Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs|
The 64-bit versions of IE11 and apps using the 64-bit version of the WebBrowser control might show PDFs as just gray.
|OS Build 19041.1052|
|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 |
Printing and scanning might fail when these devices use smart-card authentication
|Status||Originating update||History||Confirmed||OS Build 19041.1110|
|Last updated: 2021-07-23, 15:32 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.
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
|Status||Originating update||History||Resolved KB5004237||OS Build 19041.1081|
|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.
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.
Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs
|Status||Originating update||History||Resolved KB5004760||OS Build 19041.1052|
|Resolved: 2021-06-29, 10:00 PT
Opened: 2021-06-25, 12:53 PT
After installing KB5003637 or later updates, Internet Explorer 11 (IE11) or apps using the 64-bit version of the WebBrowser control might fail to open PDFs or may render as just a gray background using the Adobe Acrobat plug-in. Note Internet Explorer is only affected if Enable 64-bit Processes for Enhanced Protected Mode is enabled in the Advanced tab in Internet Options.
Workaround: To mitigate the issue, you can use one of the following:
Resolution: This issue was resolved in the out-of-band update KB5004760. It is a cumulative update, so you do not need to apply any previous update before installing it. KB5004760 is now available on the Microsoft Update Catalog and must be manually downloaded and installed. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions.
Automatic input of Furigana might not work as expected
|Status||Originating update||History||Mitigated||N/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).
Next steps: We are working on a resolution and will provide an update in an upcoming release.