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. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Known issues
Summary | Originating update | Status | Last updated |
---|---|---|---|
The May 2024 security update might fail to install Some IT admins have reported that the update fails to install on devices where Windows is not set to English language | OS Build 17763.5820 KB5037765 2024-05-14 | Confirmed | 2024-05-16 19:24 PT |
VPN connections might fail after installing the April 2024 security update We are investigating user reports, and we will provide more information in the coming days | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved KB5037765 | 2024-05-14 10:02 PT |
NTLM traffic issue after installing the April 2024 security update Customers have reported NTLM authentication failures and high load on affected domain controllers | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved KB5037765 | 2024-05-14 10:02 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 | Resolved | 2024-04-26 16:21 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
May 2024
The May 2024 security update might fail to install
Status | Originating update | History |
---|---|---|
Confirmed | OS Build 17763.5820 KB5037765 2024-05-14 | Last updated: 2024-05-16, 19:24 PT Opened: 2024-05-15, 19:17 PT |
Windows servers attempting to install the May 2024 security update (KB5037765), released May 14, 2024, might face issues during the installation process. The installation might fail with an error code 0x800f0982. This issue is more likely to affect devices that do not have the English (United States) language pack.
Some customers also reported install errors for this update on Windows 10, version 1809. Home users of Windows are unlikely to experience this issue since the Home and Pro editions of this Windows version reached end of servicing in 2020. Only Enterprise and IoT LTSC editions are under extended support.
Next steps: We are working on a resolution and will release it as soon as possible.
Affected platforms:
- Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
April 2024
VPN connections might fail after installing the April 2024 security update
Status | Originating update | History |
---|---|---|
Resolved KB5037765 | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:15 PT |
Windows devices might face VPN connection failures after installing the April 2024 security update (KB5036896) or the April 2024 non-security preview update.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037765), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
Client: Windows 11, version 23H2; Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2, Windows 10, version 21H2.
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
NTLM traffic issue after installing the April 2024 security update
Status | Originating update | History |
---|---|---|
Resolved KB5037765 | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:56 PT |
After installing the April 2024 security update (KB5036896) on domain controllers (DCs), you might notice a significant increase in NTLM authentication traffic. This issue is more likely to affect Active Directory (AD) deployments already servicing a large number of NTLM authentication requests where a small number of Primary Domain Controllers (PDCs) are supporting a large number of read-write Backup Domain Controllers (DCs) and Read Only Domain Controllers (RODCs).
Note: In rare instances, Windows Servers running the Domain Controller (DC) role might experience Local Security Authority Subsystem Service (LSASS) crashes resulting in a reboot.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037765), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
Client: none
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008
October 2023
BitLocker might incorrectly receive a 65000 error in MDMs
Status | Originating update | History |
---|---|---|
Resolved | N/A | Resolved: 2024-04-26, 16:21 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.
Resolution: Because this version of Windows 10 is under extended support, this issue will not be addressed in a future update. To learn about the scope of security updates for this version of Windows 10, see the Product Lifecycle FAQ - Extended Security Updates (ESU) program.
Please note, this issue remains limited to a reporting scenario only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues. BitLocker encryption functionality is expected to work correctly, despite the incorrect display of this error message in this issue.
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
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 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
Status | Originating update | History |
---|---|---|
Mitigated | OS 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:
- .NET Framework 4.8 KB5011258
- Windows Server 2019:
- Windows Server 2016:
- Windows Server 2012 R2:
- .NET Framework 4.8 KB5011266
- .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 or 4.7.2 KB5011263
- .NET Framework 4.5.2 KB5011261
- 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.