Windows Server KB5062557 Update Triggers Cluster & VM Problems
▼ Summary
– Microsoft warns of Cluster service and VM restart issues after installing the July 2024 Windows Server 2019 security update (KB5062557).
– The bug causes Cluster service failures, node rejoining problems, and BitLocker errors on Cluster Shared Volumes (CSV) drives.
– Affected systems may experience repeated restarts, quarantine states, and Event ID 7031 errors in logs.
– Microsoft advises businesses to contact support for mitigation until a permanent fix is released in a future update.
– The July 2024 updates also resolved a DHCP service freeze issue caused by June 2025 updates and a WSUS sync problem.
Microsoft is urging businesses to contact support following widespread cluster service and virtual machine disruptions linked to the latest Windows Server 2019 security update. The problematic KB5062557 patch, released on July 8, has triggered critical failures in cluster operations, forcing repeated service restarts and preventing nodes from rejoining clusters properly.
Administrators report the update introduces instability across environments where BitLocker is enabled on Cluster Shared Volumes (CSV), with systems logging frequent Event ID 7031 errors. Virtual machines experience unexpected reboots, while affected nodes may enter quarantine states, severely disrupting operations. Microsoft acknowledges the issue in internal advisories but has not yet released a public fix.
For now, the company advises impacted organizations to seek direct assistance through Microsoft’s business support channels to implement temporary workarounds. A permanent resolution is expected in an upcoming update, eliminating the need for manual mitigation.
This incident follows another recent Windows Server Update Services (WSUS) glitch that blocked update deployments across networks. The July 2024 patches also addressed a separate DHCP service freeze caused by June’s security updates.
Until Microsoft issues an official fix, IT teams should monitor cluster stability closely and prepare for potential VM interruptions. Proactive engagement with support teams remains the recommended course of action for businesses facing severe operational impacts.
(Source: Bleeping Computer)
