Microsoft pulls new Windows Server updates due to critical bugs

Microsoft has pulled Windows Server’s January Cumulative Updates after critical bugs caused domain controllers to restart, Hyper-V to not work, and ReFS volume systems to become unavailable.

On Tuesday, Microsoft released the January 2022 Patch Tuesday updates for Windows Server, which include 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 fetches Windows Server updates

Shortly after Microsoft released this week’s Windows Server updates, administrators who installed them began reporting that they were experiencing a number of serious issues.

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

Today BleepingComputer was informed that Microsoft has retired Windows Server January Updates and they are no longer accessible through Windows Update.

In testing by BleepingComputer, we can confirm that our installation of Windows Server 2019, which has the December Cumulative Update installed, no longer offers the January KB5009557 update.

Windows Server 2019 does not offer the January 2022 Update
Windows Server 2019 does not offer the January 2022 Update
Source: BleepingComputer

We have not independently verified whether other Windows Server updates have been removed, but Windows administrators have told us that they are.

Updates are still available in the Microsoft Catalog, but BleepingComputer strongly recommends administrators not to install new Windows Server updates at this time.

While the updates resolve 97 security vulnerabilities, some of which are critical, they also cause significant disruption to Windows networks.

The January Windows 10 and Windows 11 Cumulative Updates also break L2TP VPN connections, but Microsoft has not retired these updates at this time.

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

Comments are closed.