[ad_1]
The most recent Home windows Server updates are inflicting extreme points for directors, with area controllers having spontaneous reboots, Hyper-V not beginning, and inaccessible ReFS volumes till the updates are rolled again
Yesterday, Microsoft launched the Home windows Server 2012 R2 KB5009624 replace, the Home windows Server 2019 KB5009557 replace, and the Home windows Server 2022 KB5009555 replace as a part of the January 2022 Patch Tuesday.
After putting in these updates, directors have been battling a number of points which might be solely resolved after eradicating the updates.
Home windows area controller boot loops
Essentially the most severe concern launched by these updates is that Home windows area controllers enter a boot loop, with servers entering into an limitless cycle of Home windows beginning after which rebooting after a couple of minutes.
As first reported by BornCity, this concern impacts all supported Home windows Server variations.
“Appears to be like KB5009557 (2019) and KB5009555 (2022) are inflicting one thing to fail on area controllers, which then hold rebooting each couple of minutes,” a person posted to Reddit.
A Home windows Server administrator informed BleepingComputer that they see the LSASS.exe course of use the entire CPU on a server after which finally terminate.
As LSASS is a vital course of required for Home windows to function appropriately, the working system will robotically restart when the method is terminated.
The next error shall be logged to the occasion viewer when restarting resulting from a crashed LSASS course of, as one other person on Reddit shared.
“The method wininit.exe has initiated the restart of pc [computer_name] on behalf of person for the next purpose: No title because of this could possibly be discovered Cause Code: 0x50006 Shutdown Sort: restart Remark: The system course of ‘C:WINDOWSsystem32lsass.exe’ terminated unexpectedly with standing code -1073741819. The system will now shut down and restart.”
Hyper-V not begins
Along with the boot loops, BleepingComputer has been informed by Home windows directors that after putting in the patches, Hyper-V not begins on the server.
This bug primarily impacts Home windows Server 2012 R2 server, however different unverified reviews say it impacts newer variations of Home windows Server.
As Hyper-V just isn’t began, when making an attempt to launch a digital machine, customers will obtain an error stating the next:
“Digital machine xxx couldn’t be began as a result of the hypervisor just isn’t working.”
Microsoft launched safety updates to repair 4 completely different Hyper-V vulnerabilities yesterday (CVE-2022-21901, CVE-2022-21900, CVE-2022-21905, and CVE-2022-21847), that are doubtless inflicting this concern.
ReFS file programs are not accessible
Lastly, quite a few admins are reporting that Home windows Resilient File System (ReFS) volumes are not accessible or are seen as RAW (unformatted) after putting in the updates.
The Resilient File System (ReFS) is a Microsoft proprietary file system that has been designed for top availability, information restoration, and excessive efficiency for very giant storage volumes.
“Put in these updates tonight, in a two server Alternate 2016 CU22 DAG, working on Server 2012 R2. After a very lengthy reboot, the server got here again up with all of the ReFS volumes as RAW,” defined a Microsoft Alternate administrator on Reddit.
“NTFS volumes hooked up have been fantastic. I notice this isn’t completely an change query however it’s impacting my means to carry providers for Alternate again on-line.”
Uninstalling the Home windows Server updates made the ReFS volumes accessible once more.
Yesterday, Microsoft mounted seven distant code execution vulnerabilities in ReFS, with a number of doubtless behind the inaccessible ReFS volumes.
These vulnerabilities are tracked as CVE-2022-21961, CVE-2022-21959, CVE-2022-21958, CVE-2022-21960, CVE-2022-21963, CVE-2022-21892, CVE-2022-21962, CVE-2022-21928.
Easy methods to repair?
Sadly, the one approach to repair these points is to uninstall the corresponding cumulative replace to your Home windows model.
Admins can do that through the use of one of many following instructions:
Home windows Server 2012 R2: wusa /uninstall /kb:KB5009624
Home windows Server 2019: wusa /uninstall /kb:KB5009557
Home windows Server 2022: wusa /uninstall /kb:KB5009555As Microsoft bundles all safety fixes into the one replace, eradicating the cumulative replace might repair the bugs, however may even take away all fixes for not too long ago patched vulnerabilities.
Subsequently, uninstalling these updates ought to solely be finished if completely mandatory.
To not be outdone by Home windows Server, Home windows 10 and Home windows 11’s updates are additionally breaking L2TP VPN connections.
BleepingComputer has reached out to Microsoft for fixes on these points however has not heard again presently.
[ad_2]
