Microsoft pulls new Windows Server updates due to critical bugs

by chebbi abir

Microsoft has pulled the January Windows Server cumulative updates after critical bugs caused domain controllers to reboot, Hyper-V to not work, and ReFS volume systems to become unavailable.

Tuesday, Microsoft released the January 2022 Patch Tuesday updates for Windows Server that includes numerous security updates and bug fixes.

These updates are KB5009624 for Windows Server 2012 R2, KB5009557 for Windows Server 2019, and KB5009555 for Windows Server 2022.

Microsoft pulls Windows Server updates

Soon after Microsoft released this week’s Windows Server updates, admins who installed them began reporting that they encountered numerous severe issues.

These issues included domain controllers going through an endless reboot loop, ReFS volumes becoming inaccessible and showing as RAW file systems, and Hyper-V no longer starting on servers.

Today, BleepingComputer has been told that Microsoft has pulled the January Windows Server updates, and they are no longer accessible via Windows Update.

In tests conducted by BleepingComputer, we can confirm that our Windows Server 2019 install, which has the December cumulative update installed, is no longer offered the January KB5009557 update.

Windows Server 2019 not offered the January 2022 update
Windows Server 2019 not offered the January 2022 update
Source: BleepingComputer

We have not independently verified if the other Windows Server updates have been removed but have been told by Windows admins that this is the case.

The updates are still available from the Microsoft Catalog, but BleepingComputer strongly recommends that admins not install the new Windows Server updates at this time.

While the updates resolve 97 security vulnerabilities, with some being critical, they are also causing significant disruption on Windows networks.

January’s Windows 10 and Windows 11 cumulative updates are also breaking L2TP VPN connections but Microsoft has not pulled those updates at this time.


BleepingComputer has contacted Microsoft again about these bugs, and now the updates being pulled, but have not received a response.


To read the original article:


Interdit de copier  ce contenu