Microsoft Fix Bug Error 0x1E When Shutdown Windows 10 LTSC 2019

Some time ago, Microsoft released update KB5016690 for users of Windows 10 LTSC 2019 and Windows Server 2019, where in this update there are a number of fixes that are presented, including bug fixes. error 0x1E which users have complained about when turning off their Windows 10.

With this update, the Windows 10 LTSC 2019 Build that we are using will change to 17763.3346, and it should also be noted that this update is part of the optional updates and is not offered directly via Windows Update.

In my case, this update will appear when I double press check for updates, is this a coincidence, or is that the method? I’m curious too.

Now in addition to bringing improvements to Error 0x1E, there are also a number of improvements that are presented, including:

• New! Enhances Microsoft Defender for Endpoint’s ability to identify and intercept ransomware and advanced attacks.
• Addresses an issue that causes ServerAssignedConfigurations to be null in a few full configuration scenarios.
• Addresses an issue that might generate error 0x1E when you shut down or restart a device.
• Addresses an issue that prevents virtualized App-V Microsoft Office applications from opening or causes them to stop working.
• Addresses an issue that leads to a false negative when you run scripts while Windows Defender Application Control (WDAC) is turned on. This might cause AppLocker events 8029, 8028, or 8037 to appear in the log when they should not.
• Addresses an issue that causes the Resultant Set of Policy tool (Rsop.msc) to stop working when it processes 1,000 or more “File System” security settings.
• Addresses an issue that causes the Settings app to stop working on server domain controllers (DCs) when accessing the Privacy > Activity history page.
• Addresses a race condition that causes the Local Security Authority Subsystem Service (LSASS) to stop working on Active Directory domain controllers. This issue occurs when LSASS processes simultaneous Lightweight Directory Access Protocol (LDAP) over Transport Layer Security (TLS) requests that fail to decrypt. The exception code is 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN).
• Addresses an issue that affects a lookup for a non-existent security ID (SID) from the local domain using a read-only domain controller (RODC). The lookup unexpectedly returns the STATUS_TRUSTED_DOMAIN_FAILURE error instead of STATUS_NONE_MAPPED or STATUS_SOME_MAPPED.
• Addresses an issue that prevents a private virtual LAN (PVLAN) from providing tenant and virtual machine (VM) isolation.
• Addresses an issue that delays a client’s acquisition of the Internet Protocol version 6 (IPv6) address for extended periods in an IPv6 environment.
• Addresses an issue that might cause Remote Desktop Session licensing to display a 60-minute disconnection warning after reconnecting.
• Addresses an issue that causes a RODC to unexpectedly restart. In the event log, you’ll find the following:
  • Event 1074 with the message, “The system process ‘C:Windowssystem32lsass.exe’ terminated unexpectedly with status code -1073740286. The system will now shut down and restart.”
  • Event 1015 with the message, “A critical system process, C:Windowssystem32lsass.exe, failed with status code c0000602. The machine must now be restarted.”
  • Event 1000 with the message, “Faulting application name: lsass.exe, Faulting module name: ESENT.dll, Exception code: 0xc0000602.”
• Addresses an issue that might cause cldflt.sys to reference invalid memory in race conditions.

There are quite a few, right?, so for you Windows 10 LTSC 2019 users, it’s a good idea to update your system immediately to get the above update.

You can just jump to the page Settings > Update & Security > Windows Updates > Check for Updates.

You can also download this update manually from the Microsoft Update Catalog page following.