Problem with KB5062557 on Server 2019 2-node S2D Cluster

Question

Problem with KB5062557 on Server 2019 2-node S2D Cluster

RICHARD PLOECHL 5

We installed KB5062557 on our Server 2019 two-node S2D Test-Cluster - all fine.

We then installed KB5062557 on a productive cluster (Server 2019 two-node S2D)

After installation uf the update on one node this the node fails to keep Cluster service running, enters / leave cluster repeatedly until it was quarantined.

Beside that many VMs were restarted more than once.

No chance to get the node active in the cluster again,

Start-ClusterNode -Name "node1" -ClearQuarantine does not work.

We uninstalled KB5062557 from the node - cluster is fine again, both nodes active.

How to get the update installed without damaging the cluster?

We have some more clusters waiting for updates but we should wait until we know the reason for the failure.

Richard

sz 0 Zuverlässigkeitspunkte

2025-07-18T15:12:56.1466667+00:00

I have come across the same issue over multiple clusters. It appears that the failover cluster service on the patched nodes fails to start due to a network resource handling issue.

Having different patch levels isn't the problem since even two hosts with the July patch fail to talk to each other.

I have attempted to manually update the servers using the patch from the Windows catalog with the same results.

I have also attempted to evict the server, remove the failover cluster feature, install the patch, and add the failover cluster feature back.
Bernard Shum 0 Zuverlässigkeitspunkte

2025-07-21T08:51:28.8733333+00:00

I have the same problem on one of our clusters. It will have network communication issue after installing the patch although the network is pingable. Even tried updating NIC firmware and driver and still the same. Uninstall the patch and it would resume working. Already spend two weekends to attempt installing the update. The servers are pretty healthy as they were in the cluster for a couple of years and all previous patches installed just fine.

Ihre Antwort

sz 0 Zuverlässigkeitspunkte

2025-07-18T15:12:56.1466667+00:00

I have come across the same issue over multiple clusters. It appears that the failover cluster service on the patched nodes fails to start due to a network resource handling issue.

Having different patch levels isn't the problem since even two hosts with the July patch fail to talk to each other.

I have attempted to manually update the servers using the patch from the Windows catalog with the same results.

I have also attempted to evict the server, remove the failover cluster feature, install the patch, and add the failover cluster feature back.
Bernard Shum 0 Zuverlässigkeitspunkte

2025-07-21T08:51:28.8733333+00:00

I have the same problem on one of our clusters. It will have network communication issue after installing the patch although the network is pingable. Even tried updating NIC firmware and driver and still the same. Uninstall the patch and it would resume working. Already spend two weekends to attempt installing the update. The servers are pretty healthy as they were in the cluster for a couple of years and all previous patches installed just fine.