Windows 10, version 20H2 and Windows Server, version 20H2
Find information on known issues and the status of the rollout for Windows 10, version 20H2 and Windows Server, version 20H2. 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 May 18, 2021
Windows 10, version 20H2 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|
|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 19042.1165|
|Resolved External||2021-09-16 |
|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.
Administrator credentials required every time apps attempt to print
|Status||Originating update||History||Resolved External||OS Build 19042.1165|
|Last updated: 2021-09-16, 18:11 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.
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.
Automatic input of Furigana might not work as expected
|Status||Originating update||History||Resolved KB5005101||N/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).
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.