Windows ten, version 1809 and Windows Server 2019

  • Article
  • 9 minutes to read

Find information on known problems for Windows ten, version 1809 and Windows Server 2019. Looking for a specific issue? Printing CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release wellness updates? Follow @WindowsUpdate on Twitter.

Current status every bit of May 11, 2021:
Equally of May eleven, 2021, all editions of Windows ten, version 1809 and Windows Server 2019 accept reached finish of servicing, except LTSC editions. Devices running these editions volition no longer receive monthly security and quality updates containing protections from the latest security threats.
As ever, nosotros recommend that you update your devices to the latest version of Windows 10 equally presently as possible to ensure that you can take advantage of the latest features and avant-garde protections from the latest security threats. For information about servicing timelines and lifecycle, see the Windows 10 release data and Lifecycle FAQ - Windows.
  • Windows 11 is now available

    Explore this latest release.

  • How to get Windows xi

    Explore the upgrade experience.

    Known issues

    This table offers a summary of current active bug and those issues that have been resolved in the last 30 days.

    Summary Originating update Status Last updated
    Windows Servers domain controllers might restart unexpectedly
    Later installing updates released Jan 11, 2022, DCs might restart unexpectedly later on receiving an Lsass.exe mistake.
    		 Bone Build 17763.2452
    KB5009557
    2022-01-11    		 Resolved
    KB5010791    		 2022-01-eighteen
    14:00 PT
    Certain apps or devices might be unable to create Netlogon secure channel connections
    Scenarios which rely on synthetic RODC machine accounts might fail if they do non accept a linked KRBTGT account.
    		 OS Build 17763.2452
    KB5009557
    2022-01-11    		 Investigating
    		 2022-02-24
    17:41 PT
    Outlook search might not locate recent emails
    Searches on Outlook desktop app might neglect when emails are stored locally in PST or OST files
    		 OS Build 17763.2330
    KB5007266
    2021-11-22    		 Resolved
    KB5010351    		 2022-02-08
    x:00 PT
    Apps that learn or set Active Directory Wood Trust Information might take issues
    Apps using Microsoft .Internet to larn or set Forest Trust Information might fail, shut, or you might receive an error.
    		Os Build 17763.2452
    KB5009557
    2022-01-11    		 Mitigated
    		 2022-02-07
    15:36 PT
    Windows 10 Enterprise might not actuate via KMS
    Windows 10 Enterprise LTSC 2019 and Windows ten Enterprise LTSC 2016 might have issues activating using new CSVLK.
    		 OS Build 17763.1911
    KB5001384
    2021-04-22    		 Confirmed
    		 2021-12-01
    18:x PT
    Devices with some Asian language packs installed may receive an mistake
    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
    ten:59 PT

    Issue details

    February 2022

    Certain apps or devices might be unable to create Netlogon secure channel connections

    Status Originating update History
    Investigating OS Build 17763.2452
    KB5009557
    2022-01-11    		 Last updated: 2022-02-24, 17:41 PT
    Opened: 2022-02-24, 17:25 PT

    After installing KB5009557 or any updates released January eleven, 2022 and later on your domain controllers, scenarios which rely on Read-merely domain controllers (RODCs) or constructed RODC machine accounts might fail to establish a Netlogon secure channel. RODC accounts must accept a linked and compliant KRBTGT account to successfully constitute a secure aqueduct. Affected applications or network appliances, such equally Riverbed SteelHead WAN Optimizers, might have issues joining domains or limitations later joining a domain.

    Next Steps: Affected apps and network appliances will need an update from their developer or manufacturer to resolve this issue. Microsoft and Riverbed are soon investigating and will provide an update when more information is available.

    Affected platforms:

    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Apps that acquire or set Active Directory Woods Trust Data might have issues

    Status Originating update History
    Mitigated Bone Build 17763.2452
    KB5009557
    2022-01-11    		 Final updated: 2022-02-07, fifteen:36 PT
    Opened: 2022-02-04, 16:57 PT

    After installing updates released January 11, 2022 or subsequently, apps using Microsoft .NET Framework to larn or prepare Agile Directory Woods Trust Information might fail, close, or you might receive an error from the app or Windows. Y'all might besides receive an access violation (0xc0000005) mistake. Note for developers: Affected apps use the System.DirectoryServices API.

    Next Steps: This effect was resolved in the out-of-ring update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and volition not install automatically. To get the standalone parcel, search for the KB number for your version of Windows and .Internet Framework in the Microsoft Update Catalog. Yous tin manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Director. For WSUS instructions, run across WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.

    For instructions on how to install this update for your operating system, meet the KB articles listed beneath:

    • ​Windows Server 2022:
      • ​.Internet Framework 4.8 KB5011258
    • ​Windows Server 2019:
      • ​.NET Framework 4.8 KB5011257
      • ​.Internet Framework iv.7.two KB5011259
    • ​Windows Server 2016:
      • ​.Cyberspace Framework 4.eight KB5011264
      • ​.NET Framework 4.half-dozen.2, 4.7, 4.vii.1 or 4.7.2 KB5011329
    • ​Windows Server 2012 R2:
      • ​.Cyberspace Framework 4.viii KB5011266
      • ​.Net Framework 4.6, 4.6.1, 4.6.2, 4.vii, iv.seven.1 or 4.7.two KB5011263
      • ​.Net Framework four.5.2 KB5011261
    • ​Windows Server 2012:
      • ​.Internet Framework 4.viii KB5011265
      • ​.NET Framework 4.6, 4.six.1, 4.6.2, iv.7, 4.7.1 or 4.seven.two KB5011262
      • ​.Cyberspace Framework 4.5.2 KB5011260

    Affected platforms:

    • ​Client: None
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    January 2022

    Windows Servers domain controllers might restart unexpectedly

    Status Originating update History
    Resolved KB5010791 OS Build 17763.2452
    KB5009557
    2022-01-11    		 Resolved: 2022-01-18, 14:00 PT
    Opened: 2022-01-13, 14:14 PT

    Later on installing KB5009557 on domain controllers (DCs), afflicted versions of Windows Servers might restart unexpectedly. You might receive an error dialog for Lsass.exe, stating "Your PC volition automatically restart in one minute" or "The system volition now shut down and restart." Note: On Windows Server 2016 and later, you lot are more likely to exist affected when DCs are using Shadow Principals in Enhanced Security Admin Environment (ESAE) or environments with Privileged Identity Management (PIM).

    Resolution: This issue was resolved in the out-of-ring update KB5010791. We recommend you lot install the latest security update for your device. Currently, the latest security update was released on February eight, 2022 and is the recommended pick. Information technology contains important improvements and bug resolutions, including this one. Information technology is a cumulative update, and so you do non demand to apply whatsoever previous update before installing it. If y'all would like to install the update, y'all will need to Check for updates and select "Optional updates" and so select KB5010791. To get the standalone parcel for KB5010791, search for information technology in the Microsoft Update Catalog. Yous can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Notation KB5010791 will not install automatically.

    Affected platforms:

    • ​Client: None
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    Outlook search might not locate recent emails

    Condition Originating update History
    Resolved KB5010351 Bone Build 17763.2330
    KB5007266
    2021-xi-22    		 Resolved: 2022-02-08, ten:00 PT
    Opened: 2022-01-19, fifteen:40 PT

    Recent emails might not appear in search results on Outlook desktop app on Windows 11. This event is related to emails which have been stored locally in a PST or OST files. It might impact Popular and IMAP accounts, also as Microsoft Exchange and Microsoft 365 hosted accounts. If the default search in the Outlook app is gear up to server search, the issue will only affect the advanced search.

    Workaround: To mitigate the upshot, you can disable Windows Desktop Search which will crusade Outlook to use its built-in search. For instructions, see Outlook Search non showing recent emails later on Windows update KB5008212.

    Resolution: This issue was resolved in KB5010351, released Feb 8, 2022. If y'all install an update released February 8, 2022 ( KB5010351) or later, yous do not need to use a Known Result Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before February 8, 2022, you can resolve this issue using KIR. For enterprise-managed devices that have installed an affected update and encountered this upshot, information technology can exist resolved by installing and configuring a special Grouping Policy. Important Verify that you are using the correct Group Policy for your version of Windows.

    Group Policy for KIR:

    • ​Windows 10, version 20H2, Windows 10, version 21H1 and Windows 10, version 21H2
    • ​Windows 10, version 1809, Windows 10 Enterprise LTSC 2019, and Windows Server 2019

    Affected platforms:

    • ​Customer: Windows 11, version 21H2; Windows 10, version 21H2; Windows x, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
    • ​Server: Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019

    December 2021

    Windows ten Enterprise might not activate via KMS

    Status Originating update History
    Confirmed Os Build 17763.1911
    KB5001384
    2021-04-22    		 Last updated: 2021-12-01, eighteen:ten PT
    Opened: 2021-12-01, 17:44 PT

    After installing updates released April 22, 2021 or subsequently on an affected version of Windows Server when used as Key Management Services (KMS) host, client devices running Windows 10 Enterprise LTSC 2019 and Windows x Enterprise LTSC 2016 might neglect to actuate. This issue only occurs when using a new Client Support Volume License Key (CSVLK). Note: This does not touch on activation of whatsoever other version or edition of Windows.

    Customer devices attempting to activate that are affected by this issue might receive the error, "Error: 0xC004F074 The Software Licensing Service reported that the computer could not exist activated. No Primal Management Service (KMS) could be contacted. Please see the Awarding Event Log for additional information." Outcome Log entries related to activation is another fashion to tell that you might be affected by this issue. Open Consequence Viewer on the client device that failed activation and go to Windows Logs, and so Application. If yous run across just effect ID 12288 (without a corresponding issue ID 12289), this means that the KMS client was not able to reach the KMS host, the KMS host did non reply, or the client did not receive the response. For more information on these event ID, see Useful KMS client events - Event ID 12288 and Event ID 12289.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Afflicted platforms:

    • ​Client: Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016

    May 2019

    Devices with some Asian language packs installed may receive an error

    Status Originating update History
    Mitigated Os 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 Apr 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."

    Afflicted platforms:

    • ​Customer: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
    • ​Server: Windows Server, version 1809; Windows Server 2019

    Workaround:

    1. ​Uninstall and reinstall whatever recently added language packs. For instructions, come across "Manage the input and display language settings in Windows 10".
    2. ​Click Check for Updates and install the April 2019 Cumulative Update. For instructions, come across "Update Windows ten".

    Note: If reinstalling the language pack does not mitigate the issue, reset your PC equally follows:

      1. ​Go to Settings app -> Recovery.
      2. ​Click on Get Started under "Reset this PC" recovery selection.
      3. ​Select "Keep my Files".

    Adjacent steps: Microsoft is working on a resolution and will provide an update in an upcoming release.