Faulting application name: lsass.exe in Windows Server 2019 after KB5013941

Question

After installation of KB5013941 (Mai Update) on serveral windows 2019 VMs, the VMs crash and reboot from time to time with the following error:

Faulting application name: lsass.exe, version: 10.0.17763.2686, time stamp: 0xcb5bd01a
Faulting module name: ntdll.dll, version: 10.0.17763.2989, time stamp: 0x21d18902
Exception code: 0xc0000008
Fault offset: 0x00000000000a381a
Faulting process id: 0x270
Faulting application start time: 0x01d870d78b59e446
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

The behavior is the same with the later KB5015018 and KB5014022.

The VMs are Windows Server core and standalone (no Domain etc.). The only service running on the VMs is Docker with many WCF server applications running inside the containers.

After going back to KB5012647 (April Update) the crashes are gone.

Any idea what might have caused this behavior?

I could not find any information that KB5013941 causes problem with Docker and/or WCF server applications.

Answer 1

Hello @HS ,

Thanks for your query. Is everything going well after installation of KB5013941 if you uninstall Docker with many WCF server applications?
Did you encounter the same error message after update to KB5015018？
https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-10-1809-and-windows-server-2019
https://borncity.com/win/2022/01/12/windows-server-januar-2022-sicherheitsupdates-verursachen-boot-schleife/

For further professional help, we sincerely recommend that you open a case to Microsoft support: https://support.microsoft.com/en-us/help/4341255/support-for-busines
Thanks for your cooperation!

Best regards,
Leila

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

Hello HS-0586

The behavior is described in the next Known issues for the CU:

https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-10-1809-and-windows-server-2019#may-2022

Which should be resolved with KB5015018 (https://support.microsoft.com/en-us/topic/may-19-2022-kb5015018-os-build-17763-2931-out-of-band-e4c28a4d-7dbe-4ef5-a539-f0b21cba2ebb) but still it contains also other Known issues that may want to address in the section "Known issues in this update"

Additionally, it would be recommended to check the Integration Services version and upgrade if needed, on the virtual machines that are affected by this issue:
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services

------------------------------------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept as answer--