Update (18/1/22)
Microsoft released OOB updates they are available for download on the Microsoft Update Catalog, and some of them can also be installed directly through Windows Update as optional updates.
UPDATE (17/1/22):
- Microsoft has confirmed they are investigating the issues.
- The updates are remove from the windows update , but they available via windows catalog.
- Some users complain that they face problems also with Windows 2016 servers.
IT looks that latest Windows Server updates are causing severe issues for administrators, with domain controllers having spontaneous reboots, Hyper-V not starting, and inaccessible ReFS volumes until the updates are rolled back
IT Looks like KB5009557 (2019) and KB5009555 (2022) and KB5009624 (2012) are causing something to fail , which then keep rebooting every few minutes.
some blogs reports errors like :
The process wininit.exe has initiated the restart of computer DC on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process ‘C:\Windows\system32\lsass.exe’ terminated unexpectedly with status code -1073741819. The system will now shut down and restart.Faulting application name: lsass.exe, version: 10.0.14393.4704, time stamp: 0x615be0cd
Faulting module name: lsadb.dll, version: 10.0.14393.4886, time stamp: 0x61d5242f
Exception code: 0xc0000005
Fault offset: 0x000000000001be5b
Faulting process id: 0x2a8
Faulting application start time: 0x01d8077b1080a9da
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\system32\lsadb.dll
Report Id: e14067b5-aac7-46a4-9e21-cc45371c522a
Faulting package full name:
Faulting package-relative application ID:
So there wininit.exe triggers the error 0xc0000005 o
How to fix?
Unfortunately, it looks that the only way to fix these issues is to uninstall the corresponding cumulative update for your Windows version.
I want to advise against rolling back snapshots, especially on DC’s, so as not to provoke USN rollbacks.
It look that the reboot loop is around 10-15 min , so you have time to have Clean Uninstall before the next boot.
Admins can do this by using one of the following commands:
Windows Server 2012 R2 - wusa /uninstall /kb:KB5009624
Windows Server 2019 - wusa /uninstall /kb:KB5009557
Windows Server 2022 - wusa /uninstall /kb:KB5009555Or Uninstall manually from Appwiz.cpl (e,g In windows 2019)
As Microsoft bundles all security fixes into the single update, removing the cumulative update may fix the bugs, but will also remove all fixes for recently patched vulnerabilities.
Therefore, uninstalling these updates should only be done if absolutely necessary.
Lets hope Microsoft will release any fix for that issues .
SHMUEL H
Microsoft pulled out the bugy updates
https://www.bleepingcomputer.com/news/microsoft/microsoft-pulls-new-windows-server-updates-due-to-critical-bugs/
Hi there,
it seems the same issue applies to Windows Server 2016. The patches you have listed, however, do not list anything for Windows Server 2016.
Also, my server (strangely enough only 1 out of 3 DCs) reboots only once per day at round about 19:50 (now 3 days in a row at the same time). The error log message:
Faulting application name: lsass.exe, version: 10.0.14393.4704, time stamp: 0x615be0cd
Faulting module name: lsadb.dll, version: 10.0.14393.4886, time stamp: 0x61d5242f
Exception code: 0xc0000005
Fault offset: 0x000000000001be5b
Faulting process id: 0x618
Faulting application start time: 0x01d80a490ad74c1f
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\system32\lsadb.dll
Report Id: 74c4ca49-1c75-43d8-9c5b-5505e84fbad3
Faulting package full name:
Faulting package-relative application ID:
Anything heard about this so far?
hi , i found that Some users also complain that they face problems also with Windows 2016 servers