Resolved issues in Windows 10, version 20H2 and Windows Server, version 20H2

See a list of known issues that have been resolved for Windows 10, version 20H2 and Windows Server, version 20H2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate resolved
Connections to printers shared via print server might encounter errors
This issue is observed when print clients try to connect to a remote printer shared on a print server
OS Build 19042.1288
KB5006670
2021-10-12
Resolved
KB5007253
2021-11-22
14:00 PT
Microsoft Installer might have issues updating or repairing apps
Affected apps might fail to open after an update or repair has been attempted.
OS Build 19042.1348
KB5007186
2021-11-09
Resolved
KB5007253
2021-11-22
14:00 PT
Smartcard authentication might fail when attempting to connect using Remote Desktop
Devices attempting to make Remote Desktop connections to devices in untrusted domains might be unable to connect.
OS Build 19042.1266
KB5005611
2021-09-30
Resolved
2021-11-22
13:13 PT
UI elements and drawing within some apps may not work as expected
Some apps using GDI+ might have issues with scaling within the app or when used on high DPI or resolution displays.
OS Build 19042.1288
KB5006670
2021-10-12
Resolved
KB5007186
2021-11-09
10:00 PT
Installation of printers via Internet Printing Protocol (IPP) might not succeed
Affects organizations that share an IPP printer using printer connections
OS Build 19042.1237
KB5005565
2021-09-14
Resolved
KB5006738
2021-10-26
10:00 PT
Receiving a prompt for administrative credentials every time you attempt to print
This issue affects devices in environments in which the print server and print client are in different times zones.
OS Build 19042.1237
KB5005565
2021-09-14
Resolved
KB5006670
2021-10-12
10:00 PT
Custom printing properties might not be correctly provided to print server clients
This issue will not cause printing operations to fail, but clients might print with default settings only
OS Build 19042.1266
KB5005611
2021-09-30
Resolved
KB5006670
2021-10-12
10:00 PT
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 19042.1202
KB5005101
2021-09-01
Resolved
KB5006670
2021-10-12
10:00 PT
Installation of printers might fail when attempted over some network connections
This issue has been observed in devices which access printers via a print server using HTTP connections
OS Build 19042.1237
KB5005565
2021-09-14
Resolved
KB5005611
2021-09-30
14:00 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 19042.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
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 19042.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 19042.1081
KB5003690
2021-06-21
Resolved
KB5004237
2021-07-13
10:00 PT
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 19042.1052
KB5003637
2021-06-08
Resolved
KB5004760
2021-06-29
10:00 PT
A high-pitched noise might be heard when using 5.1 audio with certain settings
Certain combinations of apps, audio devices and Windows settings might produce a high-pitched noise when using 5.1 audio
OS Build 19042.906
KB5000842
2021-03-29
Resolved
KB5003690
2021-06-21
14:00 PT
News and interests button on the Windows taskbar might have blurry text
Certain display configurations might cause blurry text on the news and interests button in the Windows taskbar.
OS Build 19042.964
KB5001391
2021-04-28
Resolved
KB5003690
2021-06-21
14:00 PT
Apps might have issues accessing event logs on remote devices
Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later.
OS Build 19042.10000
KB5003637
2021-06-08
Resolved
KB5003637
2021-06-08
10:00 PT

Issue details

November 2021

Microsoft Installer might have issues updating or repairing apps

StatusOriginating updateHistory
Resolved KB5007253OS Build 19042.1348
KB5007186
2021-11-09
Resolved: 2021-11-22, 14:00 PT
Opened: 2021-11-18, 10:34 PT
After installing KB5007186 or later updates, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted.

Workaround: To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app.

Resolution: This issue was resolved in KB5007253. This update should prevent the issue from occurring again, but you might need to reinstall affected apps, if they will not open.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H2; 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

UI elements and drawing within some apps may not work as expected

StatusOriginating updateHistory
Resolved KB5007186OS Build 19042.1288
KB5006670
2021-10-12
Resolved: 2021-11-09, 10:00 PT
Opened: 2021-11-05, 17:58 PT
After installing KB5006670 or a later update, certain apps might have unexpected results when rendering some user interface elements or when drawing within the app. You might encounter this issue with apps that use GDI+ and set a zero (0) width pen object on displays with high dots per inch (DPI) or resolution, or if the app is using scaling.

Resolution: This issue was resolved in KB5007186.

Affected platforms:
  • Client: Windows 11, version 21H2; 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, 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

October 2021

Connections to printers shared via print server might encounter errors

StatusOriginating updateHistory
Resolved KB5007253OS Build 19042.1288
KB5006670
2021-10-12
Resolved: 2021-11-22, 14:00 PT
Opened: 2021-10-29, 11:15 PT
After installation of KB5006670, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
  • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
  • 0x0000007c (ERROR_INVALID_LEVEL)
  • 0x00000709 (ERROR_INVALID_PRINTER_NAME)
Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
 
Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
 
  • Print clients must have installed a Windows update released on or after January 2021 before the print server has installed KB5006670.
Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
  • Default start port: 49152
  • Default end port: 65535
  • Port Range: 16384 ports
Please refer to these articles for further guidance:
You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect.
 
Resolution: This issue was resolved in KB5007253.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H1; 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

Smartcard authentication might fail when attempting to connect using Remote Desktop

StatusOriginating updateHistory
ResolvedOS Build 19042.1266
KB5005611
2021-09-30
Resolved: 2021-11-22, 13:13 PT
Opened: 2021-10-15, 17:20 PT
After installing KB5005611 or later updates, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004
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 linked below. 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.

Group Policy installation files:
Important Verify that you are using the correct Group Policy for your version of Windows.

Installation of printers via Internet Printing Protocol (IPP) might not succeed

StatusOriginating updateHistory
Resolved KB5006738OS Build 19042.1237
KB5005565
2021-09-14
Resolved: 2021-10-26, 10:00 PT
Opened: 2021-10-13, 12:32 PT
After installing KB5005565, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005565 are unaffected and print operations to that printer will succeed as usual.

Note: IPP is not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

Resolution: This issue has been resolved in KB5006738.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1809; Windows 11, version 21H2; Windows 10, version 1909
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1809; Windows Server 2022; Windows Server, version 1909

Receiving a prompt for administrative credentials every time you attempt to print

StatusOriginating updateHistory
Resolved KB5006670OS Build 19042.1237
KB5005565
2021-09-14
Resolved: 2021-10-12, 10:00 PT
Opened: 2021-10-15, 17:21 PT
After installing KB5005565 or later updates, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones.

Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

Affected platforms:
  • Client: Windows 11, version 21H2; 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 was resolved in KB5006670. If after installing KB5006670 you still receive the prompt every time you print, see Q1 in the "Frequently ask questions" section of KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481).

Custom printing properties might not be correctly provided to print server clients

StatusOriginating updateHistory
Resolved KB5006670OS Build 19042.1266
KB5005611
2021-09-30
Resolved: 2021-10-12, 10:00 PT
Opened: 2021-10-13, 12:28 PT
After installing KB5005611 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only.

This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who have previously received the settings package prior to the installation of KB5005611 are unaffected. Servers which use default print settings and have no custom settings to provide to clients are unaffected.

Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Additionally, clients can still be modified manually to adopt desired printer settings.

Resolution: This issue was resolved in  KB5006670.

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, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

Installation of printers might fail when attempted over some network connections

StatusOriginating updateHistory
Resolved KB5005611OS Build 19042.1237
KB5005565
2021-09-14
Resolved: 2021-09-30, 14:00 PT
Opened: 2021-10-13, 12:26 PT
After installing KB5005565, devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers. Devices which had connected to and installed the printer prior to the installation of KB5005565 are unaffected and operations to that printer will succeed as usual.

This issue has been observed in devices which access printers via a print server using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download.

Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Only the automatic download and installation processes are impacted by this issue.

Resolution: This issue was resolved in  KB5005611.

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, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

September 2021

Apps might fail to open, close unexpectedly or become unresponsive

StatusOriginating updateHistory
Resolved KB5006670OS Build 19042.1202
KB5005101
2021-09-01
Resolved: 2021-10-12, 10:00 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 was resolved in KB5006670, released October 12, 2021. If you install an update released October 12, 2021 ( KB5006670) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before October 12, 2021, you can resolve this issue using KIR. 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. Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. 

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

3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt:
Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask


Administrator credentials required every time apps attempt to print

StatusOriginating updateHistory
Resolved ExternalOS Build 19042.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.

July 2021

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

StatusOriginating updateHistory
ResolvedOS Build 19042.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:
  • 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: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures.

Certain printers unable to print

StatusOriginating updateHistory
Resolved KB5004237OS Build 19042.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.

June 2021

Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs

StatusOriginating updateHistory
Resolved KB5004760OS Build 19042.1052
KB5003637
2021-06-08
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:
  • Open the PDF file directly in Adobe Acrobat, instead of within IE11 or the affected app.
  • For IE11 only: Disable the setting in the Advanced tab of Internet Options called Enable 64-bit Processes for Enhanced Protected Mode.
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.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004

News and interests button on the Windows taskbar might have blurry text

StatusOriginating updateHistory
Resolved KB5003690OS Build 19042.964
KB5001391
2021-04-28
Resolved: 2021-06-21, 14:00 PT
Opened: 2021-06-14, 17:43 PT
After installing KB5001391 or later updates, the news and interests button in the Windows taskbar might have blurry text on certain display configurations.

Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909
Resolution: This issue was resolved in KB5003690.

Apps might have issues accessing event logs on remote devices

StatusOriginating updateHistory
Resolved KB5003637OS Build 19042.10000
KB5003637
2021-06-08
Resolved: 2021-06-08, 10:00 PT
Opened: 2021-06-07, 16:10 PT
After installing KB5003637 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
  • error 5: access is denied
  • error 1764: The requested operation is not supported.
  • System.InvalidOperationException,Microsoft.PowerShell.Commands.GetEventLogCommand
  • Windows has not provided an error code.
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected.

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 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
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003637 installed.

May 2021

A high-pitched noise might be heard when using 5.1 audio with certain settings

StatusOriginating updateHistory
Resolved KB5003690OS Build 19042.906
KB5000842
2021-03-29
Resolved: 2021-06-21, 14:00 PT
Opened: 2021-05-13, 19:35 PT
After installing KB5000842 or later updates, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. Note This issue does not occur when stereo is used.

Workaround: To mitigate this issue, you can try one or more of the following:
  • Streaming the video or audio in a web browser or different app, instead of the app affected by this issue.
  • Enable Spatial sound settings by right clicking or long pressing on the volume icon in the notification area, selecting Spatial sound (Off) and selecting any of the available options.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004
Resolution: This issue was resolved in KB5003690.

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.