New update of Windows Server causes many serious errors
The latest Windows Server updates have caused headaches for administrators. After the update, the server system encountered serious problems such as domain controller automatically restarting, Hyper-V not running, and not being able to access the ReFS volume until the update was removed.
Windows domain controller keeps restarting by itself
The most serious problem that new updates cause is that the Windows domain controller keeps restarting itself. The server goes into an endless Windows launch cycle and then restarts after a few minutes.
As reported by multiple sources, this issue affects all versions of Windows Server that are still supported by Microsoft.
An administrator shared that he saw the LSASS.exe process take up all the CPU resources on the server and then stopped working.
Since LSASS is a necessary process for Windows to function properly, the operating system will restart itself when the process stops working.
Hyper-V not running
In addition to the constant reboots, administrators reported that after installing the update, Hyper-V was no longer working on the servers. This bug mainly affects Windows Server 2012 R2. Some unverified reports suggest that it affects newer versions of Windows Server as well.
Because Hyper-V does not start, when trying to run a virtual machine the user will receive the following error message:
"Virtual machine xxx union not be started because the hypervisor is not running".
Microsoft's recently released updates fix four Hyper-V vulnerabilities (CVE-2022-21901, CVE-2022-21900, CVE-2022-21905, and CVE-2022-21847) and could be the source of the problem. generate error.
Unable to access ReFS file system
Finally, administrators reported that Windows Resilient File System (ReFS) volumes were no longer accessible or shrunk as RAW (unformatted) after installing updates.
Resilient File System (ReFS) is a proprietary file system from Microsoft. It is designed for high availability, data resiliency and high data processing performance for very large storage volumes.
Temporary fix
Unfortunately, at the moment the only way to fix these 3 problems is to remove the updates that have just been installed on your Windows Server.
Administrators can do this 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
However, you should note that removing the above updates will also remove the recent bug fixes and vulnerability patches. Therefore, only uninstall updates if you feel absolutely necessary.
You should read it
- Recent Windows Server Updates Cause DNS Errors
- Windows Server January Update causes Netlogon error
- Steps to fix 'Unable to Contact your DHCP Server' error on Windows 10
- How to fix BCD boot error on Windows Server 2012
- Fix connection error with Apple ID server on Windows 10
- Microsoft warns new Windows updates can cause printer errors
- Updates KB5009543, KB5009566 crash L2TP VPN connection on Windows
- Use IIS to set up FTP Server on Windows
- Some ways to fix DNS Server Not Responding on Windows 7/8/10
- How to fix 'Event ID 2505: Server Could Not Bind to Transport' error on Windows
- Instructions for fixing 'A referral was returned from the server'
- How to fix Windows Update error 0x80190001
Maybe you are interested
How to Enable and Disable Tabs in File Explorer on Windows 11
5 macOS Sequoia Features Not Available on Windows 11
Why does Windows operating system have such a bad reputation?
Quickly fix Unmountable Boot Volume error on Windows 10/11
15 safe software and application download websites for Windows
How to Fix Clipboard History Error in Windows 11 Latest Update