-->
Windows 10 is a huge release from the Redmond-based software giant. In fact, it's so big that it's expected to break the Internet during its rollout period. And with a lot riding on this big. Update for Windows 10 1709, Windows 10 1803 and Windows 10 1809 for x64-based Systems (KB4468550) Windows 10. Critical Updates. Microsoft.NET Framework 4.8 for Windows 10 Version 1809 and Windows Server 2019 for x64 (KB4486153). The end of the road for Windows 10 in general, however, is a little over four years from now.' Microsoft will continue to support at least one Windows 10 semi-annual channel until October 14, 2025. Every Windows 10 version from 20H2, which was released on October 20, 2020, will come with the new version of the browser preinstalled. The Windows 10 October 2020 update added a price comparison tool to the Edge browser.
Find information on known issues and the status of the rollout for Windows 10, version 21H1. 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. |
Windows 10, version 21H1 is available for users with devices running Windows 10, version 20H2 and Windows 10, version 2004, who manually seek to “Check for updates” via Windows Update. We are now starting a new phase in our rollout. Using the machine learning training we have done so far, we are increasing the number of devices selected to update automatically to Windows 10, version 21H1 that are approaching end of servicing. We will continue to train our machine learning through all phases to deliver a smooth update experience. As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For more details, see How to get the Windows 10 May 2021 Update. |
| 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 > |
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
| 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 19043.1110 KB5004237 2021-07-13 | Resolved | 2021-08-03 10:36 PT |
| Certain printers unable to print Most affected printers are receipt or label printers that connect via USB. | OS Build 19043.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 | ||
| Status | Originating update | History |
| Resolved | OS Build 19043.1110 KB5004237 2021-07-13 | Resolved: 2021-08-03, 10:36 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:
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures. | ||
Windows 10 Media Creation Tool
Windows 10 Download
Certain printers unable to print | ||
| Status | Originating update | History |
| Resolved KB5004237 | OS Build 19043.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:
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. | ||
Windows 10 Media Creation Tool
December 2020
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). Affected platforms:
Next steps: We are working on a resolution and will provide an update in an upcoming release. | ||
Comments are closed.