I've encountered a frustrating issue after applying the June 2025 cumulative update to several Windows 2025 failover clusters that are running virtual machine workloads. Now, every attempt to perform actions on the remote nodes results in DCOM errors. I can't migrate roles, open VMs, or even adjust settings without hitting a wall. The specific error message I'm getting is: 'DCOM was unable to communicate with the computer *** using any of the configured protocols; requested by PID 2090 (C:WINDOWSsystem32mmc.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.' When I tried to manually run WMI calls from Node 1 to Node 2, I received an RPC unavailable error. However, I could successfully run the same WMI call from a non-cluster node (on the same domain) to one of the node members. It's the node-to-node communication that seems broken. I even tried evicting a node from the cluster, but that didn't help either. After rolling back the update, the issue persists, and clusters that weren't patched are operating just fine. Has anyone experienced something similar? I've opened a case with Microsoft, but I haven't heard back yet.
2 Answers
I've been through the wringer with issues related to the 2025 update and totally get where you're coming from. I'm starting to wonder if it's worth sticking with older versions, like 2016, which seemed a bit more stable for a lot of us. Just recently, someone mentioned they've been running 2025 in production since January without any drama, which is a bit reassuring. But I can't help but feel anxious as I see more concerning reports.
For real! I usually avoid updating cluster hosts unless there's a major security concern. I find once they're set up, leaving them be works best to avoid drama.
I'm in the camp that usually leaves the cluster alone until absolutely necessary. We just focus on keeping it secure. It’s only there for compute and storage, so if it’s stable, we try not to mess with it.
It's a mixed bag for sure! I had a tough time with 2016, so I jumped to 2019. Honestly, anything to avoid those horrible patching nightmares we faced!