Urgent Windows Server Bug Fix Released: What Admins Need to Know About VM Issues

Hey there - if you're running Windows Server clusters with VMs, you'll want to pay attention to this one. Microsoft just dropped a fix for a pretty nasty bug that's been causing chaos with cluster services and virtual machines. Let me break down what's happening and what you need to do about it.

The Problem: VMs Going Rogue

The issue cropped up in the KB5062557 update for Windows Server 2019, and it's been giving admins headaches for weeks. The bug was causing cluster services to randomly restart and VMs to unexpectedly reboot - basically every admin's nightmare scenario. If you've been dealing with mysterious VM restarts lately, this might be why.

Speaking of securing your server infrastructure, I've seen way too many organizations still using shared admin passwords stored in spreadsheets. If that's you, please do yourself a favor and look into NordPass Business - it's what I set up for my clients to manage server credentials securely.

Microsoft's Response and Fix

Microsoft initially told affected users to contact support (yeah, I know), but they've now released a proper fix in the August 2025 KB5063877 cumulative update. Here's the catch though - you need to install the KB5005112 servicing stack update first before you can apply the fix.

How to Deploy the Fix

1. First, install the KB5005112 servicing stack update

2. Then install the KB5063877 cumulative update

3. Restart your server (plan this during maintenance window)

Other Important Updates in KB5063877

While the cluster service fix is the headline feature, this update also includes several other important improvements:

• Fixed WSUS update deployment issues

• Addressed memory management problems

• Improved system stability for domain controllers

While we're talking about server security, I should mention that if you're managing multiple Windows Servers, you really need Malwarebytes Endpoint Protection . It's saved several of my clients from ransomware attacks, and it plays nice with Windows Server updates.

The Bigger Picture: WSUS Issues

This fix is part of Microsoft's broader effort to address WSUS (Windows Server Update Services) problems that have been blocking organizations from getting critical updates. They've streamlined the update process and fixed several deployment blockers that were causing headaches for admins.

What You Should Do Now

Here's your action plan:

1. Review your cluster services and VM logs for any signs of the issue

2. Schedule maintenance window for the update

3. Test the update in your dev environment first (seriously, don't skip this)

4. Deploy to production following the two-step process above

5. Monitor cluster services and VMs for at least 24 hours after update

Stay safe out there, and don't hesitate to reach out if you need help sorting this out.

Quick heads up:Some links in this article are affiliate links. If you buy something through them, we might earn a small commission (doesn't cost you extra). We only recommend stuff we'd actually use ourselves or set up for our own families. No BS recommendations here.