Windows 10, version 1809 and Windows Server 2019

Find information on known issues for Windows 10, version 1809 and Windows Server 2019. 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 11, 2021:
As of May 11, 2021, all editions of Windows 10, version 1809 and Windows Server 2019 have reached end of servicing, except LTSC editions. Devices running these editions will no longer receive monthly security and quality updates containing protections from the latest security threats.

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 information about servicing timelines and lifecycle, see the Windows 10 release information and Lifecycle FAQ - Windows.
Windows 10, version 21H1 is now available Windows 10, version 21H1 is now available
Find out how to get the update >
IT tools for Windows 10, version 21H1 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.

SummaryOriginating updateStatusLast 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 17763.2061
KB5004244
2021-07-13
Confirmed
2021-07-23
15:51 PT
Devices with some Asian language packs installed may receive an error
Devices with Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
OS Build 17763.437
KB4493509
2019-04-09
Mitigated
2019-05-03
10:59 PT

Issue details

July 2021

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

StatusOriginating updateHistory
ConfirmedOS Build 17763.2061
KB5004244
2021-07-13
Last updated: 2021-07-23, 15:51 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: For more information on this issue, please see KB5005408 - Smart-card authentication might cause print and scan failures.

May 2019

Devices with some Asian language packs installed may receive an error

StatusOriginating updateHistory
MitigatedOS Build 17763.437
KB4493509
2019-04-09
Last updated: 2019-05-03, 10:59 PT
Opened: 2019-05-02, 16:36 PT
After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
Workaround:
  1. Uninstall and reinstall any recently added language packs. For instructions, see "Manage the input and display language settings in Windows 10".
  2. Click Check for Updates and install the April 2019 Cumulative Update. For instructions, see "Update Windows 10".
Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
    1. Go to Settings app -> Recovery.
    2. Click on Get Started under "Reset this PC" recovery option.
    3. Select "Keep my Files".
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.