Windows 10, version 1809 and Windows Server 2019

Find information on known issues and the servicing status for Windows 10, version 1809 and Windows Server 2019. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates.

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

    See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

    SummaryOriginating updateStatusLast updated
    Issue with Kerberos requests on domain controllers may cause LSASS memory leaks
    This issue affects on-premises and cloud-based Active Directory DCs after installing the March 2024 security update
    OS Build 17763.5576
    KB5035849
    2024-03-12
    Resolved
    KB5037425
    2024-03-25
    10:43 PT
    BitLocker might incorrectly receive a 65000 error in MDMs
    "Requires Device Encryption" might incorrectly report as an error in some managed environments.
    N/A

    Mitigated
    2023-10-31
    10:06 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

    Issue details

    March 2024

    Issue with Kerberos requests on domain controllers may cause LSASS memory leaks

    StatusOriginating updateHistory
    Resolved KB5037425OS Build 17763.5576
    KB5035849
    2024-03-12
    Resolved: 2024-03-25, 11:00 PT
    Opened: 2024-03-20, 18:39 PT

    Following installation of the March 2024 security update, released March 12, 2024 (KB5035849), Local Security Authority Subsystem Service (LSASS) may experience a memory leak on domain controllers (DCs). This is observed when on-premises and cloud-based Active Directory Domain Controllers service Kerberos authentication requests.

    Extreme memory leaks may cause LSASS to crash, which triggers an unscheduled reboot of underlying domain controllers (DCs).

    Note: This issue does not occur on Home devices. It affects only environments in organizations using some Windows Server platforms.

    Resolution: This issue was resolved in the out-of-band (OOB) update KB5037425, which is only available via the Microsoft Update Catalog. We strongly recommend you do not apply the March 2024 security update on DCs and install KB5037425 instead. As this is a cumulative update, you do not need to apply any previous update before installing KB5037425. To install this update, search for KB5037425 in the Microsoft Update Catalog. The OOB update can then be manually imported to Windows Server Update Services (WSUS) and Configuration Manager. For guidance, see WSUS and the Microsoft Update Catalog.

    If you manage update catalogs in Configuration Manager, please check the section Import updates. If you with you work with software update synchronization in Configuration Manager, review the steps on Import updates from the Microsoft Update Catalog. For more information about the Microsoft Update Catalog, visit Microsoft Update Catalog - FAQs

    Important: This update (KB5037425) is not available from Windows Update and will not install automatically.

    Affected platforms:

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

    October 2023

    BitLocker might incorrectly receive a 65000 error in MDMs

    StatusOriginating updateHistory
    MitigatedN/A

    Last updated: 2023-10-31, 10:06 PT
    Opened: 2023-10-09, 14:51 PT

    Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

    Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured.

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

    Affected platforms:

    • ​Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
    • ​Server: None

    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

    Report a problem with Windows updates

    To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.

    Need help with Windows updates?

    Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.

    For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.

    View this site in your language

    This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.