Resolved issues in Windows 10, version 1909 and Windows Server, version 1909

  • Article
  • 17 minutes to read

See a list of known issues that have been resolved for Windows 10, version 1909 and Windows Server, version 1909 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

Summary Originating update Status Date resolved
Installation of printers via Internet Printing Protocol (IPP) might not succeed
Affects organizations that share an IPP printer using printer connections
OS Build 18363.1801
KB5005566
2021-09-14
Resolved
KB5007189
2021-11-09
10:00 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 18363.1854
KB5006667
2021-10-12
Resolved
KB5007189
2021-11-09
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 18363.1801
KB5005566
2021-09-14
Resolved
KB5006667
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 18363.1832
KB5005624
2021-09-21
Resolved
KB5006667
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 18363.1766
KB5005103
2021-08-26
Resolved
KB5006667
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 18363.1801
KB5005566
2021-09-14
Resolved
KB5005624
2021-09-21
15:00 PT
Azure Virtual Desktops may not be able to update via Windows Server Update Services
Manual download and installation of security updates is available, and may be necessary.
N/A Resolved
KB5005566
2021-09-14
10: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 18363.1734
KB5005031
2021-08-10
Resolved External
2021-09-16
18:23 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 18363.1679
KB5004245
2021-07-13
Resolved
2021-08-03
10:36 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 18363.1533
KB5001396
2021-04-22
Resolved
KB5003698
2021-06-15
14:00 PT
Microsoft 365 apps might be unable to sign in
Authentication issues might be encountered for apps such as Microsoft Teams, OneDrive for Business and Outlook.
OS Build 18363.1556
KB5003169
2021-05-11
Resolved
KB5003635
2021-06-09
10: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 18363.10000
KB5003635
2021-06-08
Resolved
KB5003635
2021-06-08
10:00 PT

Issue details

November 2021

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

Status Originating update History
Resolved KB5007189 OS Build 18363.1854
KB5006667
2021-10-12
Resolved: 2021-11-09, 10:00 PT
Opened: 2021-11-05, 17:58 PT
After installing KB5006667 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 KB5007189.
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
Back to top

October 2021

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

Status Originating update History
Resolved KB5007189 OS Build 18363.1801
KB5005566
2021-09-14
Resolved: 2021-11-09, 10:00 PT
Opened: 2021-10-13, 12:32 PT
After installing KB5005566, 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 KB5005566 are unaffected and print operations to that printer will succeed as usual.
Note: IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.
Resolution: This issue has been resolved in KB5007189.
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
Back to top

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

Status Originating update History
Resolved KB5006667 OS Build 18363.1801
KB5005566
2021-09-14
Resolved: 2021-10-12, 10:00 PT
Opened: 2021-10-15, 17:21 PT
After installing KB5005566 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 KB5006667. If after installing KB5006667 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).
Back to top

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

Status Originating update History
Resolved KB5006667 OS Build 18363.1832
KB5005624
2021-09-21
Resolved: 2021-10-12, 10:00 PT
Opened: 2021-10-13, 12:28 PT
After installing KB5005624 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 KB5005624 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  KB5006667.
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
Back to top

Installation of printers might fail when attempted over some network connections

Status Originating update History
Resolved KB5005624 OS Build 18363.1801
KB5005566
2021-09-14
Resolved: 2021-09-21, 15:00 PT
Opened: 2021-10-13, 12:26 PT
After installing KB5005566, 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 KB5005566 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  KB5005624.
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
Back to top

September 2021

Apps might fail to open, close unexpectedly or become unresponsive

Status Originating update History
Resolved KB5006667 OS Build 18363.1766
KB5005103
2021-08-26
Resolved: 2021-10-12, 10:00 PT
Opened: 2021-09-24, 11:00 PT
After installing KB5005103 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 KB5006667, released October 12, 2021. If you install an update released October 12, 2021 ( KB5006667) 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):
  • Windows Sever 2022
  • Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1
  • Windows 10, version 1909
  • Windows 10, version 1809, Windows Server 2019
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. NoteDevices 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                  
Back to top

Administrator credentials required every time apps attempt to print

Status Originating update History
Resolved External OS Build 18363.1734
KB5005031
2021-08-10
Last updated: 2021-09-16, 18:23 PT
Opened: 2021-09-16, 18:11 PT
After installing KB5005031 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.
Back to top

July 2021

Azure Virtual Desktops may not be able to update via Windows Server Update Services

Status Originating update History
Resolved KB5005566 N/A Resolved: 2021-09-14, 10:00 PT
Opened: 2021-07-02, 12:40 PT
We are investigating an issue where devices running Windows 10 Enterprise multi-session, version 1909 might not be able to download updates later than May 2021. This is observed in the Settings app under the Windows Update setting, which will display the message "You're up to date" even if no updates later than May 2021 have been installed.
Workaround: There are 2 alternatives to resolve this issue. As the latest images from the Azure Marketplace will be up-to-date with all of the security updates, redeployment of images to existing devices will solve this issue. If redeployment is not an option, security updates can still be installed manually on these devices, via downloads from the Microsoft Update Catalog. For instructions, please see KB5004926 and review the Workaround section.
Affected platforms:
  • Client: Windows 10 Enterprise multi-session, version 1909
  • Server: Windows Server multi-session, version 1909
Resolution: This issue was resolved in  KB5005566.
Reminder: As of May 11, 2021, the Home and Pro editions of Windows 10, version 1909 have reached end of servicing. Devices running these editions will no longer receive monthly security or quality updates and will need to update to a later version of Windows 10 to resolve this issue.
Back to top

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

Status Originating update History
Resolved OS Build 18363.1679
KB5004245
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.
Back to top

June 2021

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

Status Originating update History
Resolved KB5003698 OS Build 18363.1533
KB5001396
2021-04-22
Resolved: 2021-06-15, 14:00 PT
Opened: 2021-06-14, 17:43 PT
After installing KB5001396 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 KB5003698. Reminder As of May 11, 2021, the Home and Pro editions of Windows 10, version 1909 have reached end of servicing. Devices running these editions will no longer receive monthly security or quality updates and will need to update to a later version of Windows 10 to resolve this issue.
Back to top

Apps might have issues accessing event logs on remote devices

Status Originating update History
Resolved KB5003635 OS Build 18363.10000
KB5003635
2021-06-08
Resolved: 2021-06-08, 10:00 PT
Opened: 2021-06-07, 16:10 PT
After installing KB5003635 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 KB5003635 installed.
Back to top

May 2021

Microsoft 365 apps might be unable to sign in

Status Originating update History
Resolved KB5003635 OS Build 18363.1556
KB5003169
2021-05-11
Resolved: 2021-06-09, 10:00 PT
Opened: 2021-05-19, 10:55 PT
After installing KB5003169 and restarting your device, you might be unable to sign into some Microsoft 365 desktop client apps such as Microsoft Teams, OneDrive for Business and Microsoft Outlook. You might also receive an 80080300 error or "We ran into a problem. Reconnecting…" when attempting to authenticate or sign into Teams. Note Mobile, web and non-Windows versions are not impacted.
Workaround: To mitigate this issue on most devices, you can restart your device a second time. Most devices will sign into affected apps as expected for all subsequent restarts after the first restart that completes installation of the update. If restarting does not mitigate the issue on your device, you can use the web versions of the apps:
  • Microsoft Teams
  • OneDrive for Business
  • Outlook
Affected platforms:
  • Client: Windows 10, version 1909
Resolution: This issue was resolved in KB5003635. Reminder As of May 11, 2021, the Home and Pro editions of Windows 10, version 1909 have reached end of servicing. Devices running these editions will no longer receive monthly security or quality updates and will need to update to a later version of Windows 10 to resolve this issue.
Back to top