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.

    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
    Update might fail to install and you might receive a 0x800f0922 error
    Security update for Secure Boot DBX might fail to install.
    OS Build 17763.3280
    KB5012170
    2022-08-09
    Investigating
    2022-08-12
    17:08 PT
    Microsoft Edge might not open on 32-bit versions of Windows
    Edge might be unable to open on some 32-bit versions of Windows 10.
    OS Build 17763.30000
    KB5015880
    2022-07-21
    Resolved
    2022-07-21
    14:11 PT
    PowerShell Desired State Configuration resources might fail to apply successfully
    DSC resources in environments which require the PSCredential property might fail.
    OS Build 17763.3046
    KB5014692
    2022-06-14
    Resolved
    KB5015811
    2022-07-12
    10: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 not have a linked KRBTGT account.
    OS Build 17763.2452
    KB5009557
    2022-01-11
    Investigating
    2022-02-24
    17:41 PT
    Apps that acquire or set Active Directory Forest Trust Information might have issues
    Apps using Microsoft .NET to acquire or set Forest Trust Information might fail, close, 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 activate via KMS
    Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might have issues activating using new CSVLK.
    OS Build 17763.1911
    KB5001384
    2021-04-22
    Confirmed
    2021-12-01
    18:10 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

    August 2022

    Update might fail to install and you might receive a 0x800f0922 error

    StatusOriginating updateHistory
    InvestigatingOS Build 17763.3280
    KB5012170
    2022-08-09
    Last updated: 2022-08-12, 17:08 PT
    Opened: 2022-08-12, 17:08 PT

    When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.

    Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.

    Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

    Next steps: We are presently investigating and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    July 2022

    Microsoft Edge might not open on 32-bit versions of Windows

    StatusOriginating updateHistory
    ResolvedOS Build 17763.30000
    KB5015880
    2022-07-21
    Resolved: 2022-07-21, 14:11 PT
    Opened: 2022-07-21, 13:34 PT

    After installing KB5015880 or later updates on devices running 32-bit versions of Windows, you might be unable to open Microsoft Edge.

    Resolution: This issue was resolved in the latest Microsoft Edge Stable channel release, version 103.0.1264.62. Please see Microsoft Edge release notes for Stable Channel for more information. Microsoft Edge should update in the background but if you do not want to wait, you can download Microsoft Edge to update to the latest version right away.

    Affected platforms:

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

    PowerShell Desired State Configuration resources might fail to apply successfully

    StatusOriginating updateHistory
    Resolved KB5015811OS Build 17763.3046
    KB5014692
    2022-06-14
    Resolved: 2022-07-12, 10:00 PT
    Opened: 2022-07-19, 17:55 PT

    After installing updates released June 14, 2022, or later ( KB5014692), PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to: “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”. Note: Environments which use non-encrypted PSCredential properties will not experience the issue.

    DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows.

    Resolution: This issue was resolved in KB5015811.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2016

    February 2022

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

    StatusOriginating updateHistory
    InvestigatingOS 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 11, 2022 and later on your domain controllers, scenarios which rely on Read-only domain controllers (RODCs) or synthetic RODC machine accounts might fail to establish a Netlogon secure channel. RODC accounts must have a linked and compliant KRBTGT account to successfully establish a secure channel. Affected applications or network appliances, such as Riverbed SteelHead WAN Optimizers, might have issues joining domains or limitations after 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 presently 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 Forest Trust Information might have issues

    StatusOriginating updateHistory
    MitigatedOS Build 17763.2452
    KB5009557
    2022-01-11
    Last updated: 2022-02-07, 15:36 PT
    Opened: 2022-02-04, 16:57 PT

    After installing updates released January 11, 2022 or later, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API.

    Next Steps: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see 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, see the KB articles listed below:

    • ​Windows Server 2022: 
    • ​Windows Server 2019: 
    • ​Windows Server 2016: 
    • ​Windows Server 2012 R2: 
    • ​Windows Server 2012:

    Affected platforms:

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

    December 2021

    Windows 10 Enterprise might not activate via KMS

    StatusOriginating updateHistory
    ConfirmedOS Build 17763.1911
    KB5001384
    2021-04-22
    Last updated: 2021-12-01, 18:10 PT
    Opened: 2021-12-01, 17:44 PT

    After installing updates released April 22, 2021 or later 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 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note: This does not affect activation of any other version or edition of Windows.

    Client 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 be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information." Event Log entries related to activation is another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs, then Application. If you see only event ID 12288 (without a corresponding event ID 12289), this means that the KMS client was not able to reach the KMS host, the KMS host did not respond, 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.

    Affected 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

    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.