Windows Server 2016 Only Gives Login Screen in Safe Mode
Update 1/17/21: Microsoft has released OOB updates to prepare the Windows Server bugs.
The latest Windows Server updates are causing severe problems for administrators, with domain controllers having spontaneous reboots, Hyper-V not starting, and inaccessible ReFS volumes until the updates are rolled dorsum
Yesterday, Microsoft released the Windows Server 2012 R2 KB5009624 update, the Windows Server 2019 KB5009557 update, and the Windows Server 2022 KB5009555 update as part of the January 2022 Patch Tuesday.
After installing these updates, administrators have been contesting multiple issues that are simply resolved afterwards removing the updates.
Windows domain controller boot loops
The most serious issue introduced past these updates is that Windows domain controllers enter a boot loop, with servers getting into an endless cycle of Windows starting and then rebooting later a few minutes.
Equally first reported by BornCity, this upshot affects all supported Windows Server versions.
"Looks KB5009557 (2019) and KB5009555 (2022) are causing something to neglect on domain controllers, which then keep rebooting every few minutes," a user posted to Reddit.
A Windows Server ambassador told BleepingComputer that they run into the LSASS.exe process use all of the CPU on a server and then ultimately end.
Equally LSASS is a critical procedure required for Windows to operate correctly, the operating system volition automatically restart when the process is terminated.
The following error will be logged to the event viewer when restarting due to a crashed LSASS process, equally another user on Reddit shared.
"The process wininit.exe has initiated the restart of computer [computer_name] on behalf of user for the following reason: No championship for this reason could exist found Reason Lawmaking: 0x50006 Shutdown Type: restart Comment: The system procedure 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The organization will at present shut downwards and restart."
Hyper-V no longer starts
In improver to the boot loops, BleepingComputer has been told by Windows administrators that after installing the patches, Hyper-V no longer starts on the server.
This problems primarily affects Windows Server 2012 R2 server, only other unverified reports say information technology affects newer versions of Windows Server.
Every bit Hyper-V is not started, when attempting to launch a virtual machine, users will receive an mistake stating the following:
"Virtual machine thirty could non be started because the hypervisor is non running."
Microsoft released security updates to fix four different Hyper-V vulnerabilities yesterday (CVE-2022-21901, CVE-2022-21900, CVE-2022-21905, and CVE-2022-21847), which are probable causing this issue.
ReFS file systems are no longer accessible
Finally, numerous admins are reporting that Windows Resilient File System (ReFS) volumes are no longer accessible or are seen as RAW (unformatted) afterward installing the updates.
The Resilient File System (ReFS) is a Microsoft proprietary file organisation that has been designed for high availability, data recovery, and loftier performance for very large storage volumes.
"Installed these updates this night, in a 2 server Exchange 2016 CU22 DAG, running on Server 2012 R2. After a actually long reboot, the server came back upwardly with all the ReFS volumes as RAW," explained a Microsoft Commutation ambassador on Reddit.
"NTFS volumes attached were fine. I realize this is non exclusively an exchange question simply it is impacting my ability to bring services for Exchange dorsum online."
Uninstalling the Windows Server updates made the ReFS volumes accessible again.
Yesterday, Microsoft fixed 7 remote lawmaking execution vulnerabilities in ReFS, with one or more likely 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.
How to ready?
Unfortunately, the only mode to fix these issues is to uninstall the corresponding cumulative update for your Windows version.
Admins tin 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:KB5009555 Equally 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 just be washed if absolutely necessary.
Not to exist outdone by Windows Server, Windows 10 and Windows xi'due south updates are also breaking L2TP VPN connections.
On Jan 17th, Microsoft released out-of-band updates to ready the post-obit issues:
- Windows L2TP VPN connection bug
- Domain controller reboots
- Hyper-Five not starting
- ReFS volumes becoming inaccessible
More information about these updates tin can be found in our dedicated "Microsoft releases emergency fixes for Windows Server, VPN bugs" article.
Update 1/17/21: Added information nearly the OOB updates released to fix these issues.
Windows Server 2016 Only Gives Login Screen in Safe Mode
DOWNLOAD HERE
Source: https://www.bleepingcomputer.com/news/microsoft/new-windows-server-updates-cause-dc-boot-loops-break-hyper-v/
Posted by: ellaalwand.blogspot.com
Comentarii
Trimiteți un comentariu