Hyper-V VM Shows Critical? Fix It Fast

The Exact Scenario When This Happens

You open Hyper-V Manager and see a VM with a red Critical status. The VM is still running — you can RDP into it, apps work fine, but the icon won't turn green. This usually pops up after a backup job (Veeam, Windows Backup, or a third-party snapshot) fails or gets interrupted. I've also seen it happen after a host reboot or when Integration Services version mismatch occurs after a Windows Update.

The real trigger is the Hyper-V VSS (Volume Shadow Copy) writer backing out mid-operation. It leaves the VM in a weird state where the host can't confirm the guest is alive. The VM itself is fine, but Hyper-V Manager gives up and marks it Critical.

Root Cause? Just One Thing

Critical status almost always means the heartbeat service lost connection between the host and the guest. Hyper-V uses Integration Services to send heartbeats every few seconds. If the host doesn't get one for around 30 seconds, it panics. The most common reason: the VSS writer inside the VM crashed or didn't respond during a backup, and the Integration Services component that handles heartbeats got stuck.

Don't bother checking disk space or memory usage first — those don't cause Critical. The culprit is Integration Services or VSS writer, plain and simple.

Fix It in 5 Steps

Step 1: Check If the VM Is Actually Running

Connect to the VM via RDP or console. If it's working, move to Step 2. If it's not responding, force a restart from Hyper-V Manager (right-click > Shut Down or Reset). But 90% of the time, the VM is fine.

Step 2: Restart the Integration Services (No Reboot Needed)

Inside the VM, open an admin PowerShell session and run:

Restart-Service -Name vmicheartbeat -Force

This restarts the heartbeat service. Wait 30 seconds. Check Hyper-V Manager again. If the icon turns green, you're done. If not, move on.

Step 3: Reset the VSS Writer

Open an admin command prompt inside the VM and run:

vssadmin list writers

Look for Hyper-V Volume Shadow Copy Requestor. Its state should be Stable. If it says Failed, run:

net stop vss
net start vss

Then restart the Hyper-V Integration Services service from the host side (optional, but I do it):

Get-VM | Restart-VMIntegrationService -Name 'Heartbeat'

Refresh Hyper-V Manager. Should be green now.

Step 4: Reinstall Integration Services (If Steps 2 and 3 Fail)

Inside the VM, go to Device Manager and look for Hyper-V Integration Services. If it has a yellow exclamation mark, right-click and uninstall it. Then shut down the VM (not restart — full shutdown). From the host, run:

Get-VM | Update-VMVersion

Start the VM back up. Windows should auto-detect and reinstall the Integration Services. This fixes most stubborn cases.

Step 5: Fix the Backup Software (Prevent Recurrence)

If this keeps happening after backups, check your backup software logs. Veeam and Windows Backup sometimes take too long to snap, causing VSS timeouts. In Veeam, set VM quiescence to Enable guest quiescence (instead of using Microsoft's VSS). For native Windows Backup, increase the VSS timeout in the registry:

HKLM\SYSTEM\CurrentControlSet\Services\VSS\Settings
Create a DWORD: MaxShadowCopyTimeout
Value: 300 (decimal, meaning 5 minutes)

Reboot the host after the change.

If It Still Shows Critical

First, verify the VM's replication status if you're using Hyper-V Replica. A broken replica can show Critical. Also check the host's event logs under Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS > Admin for errors like Heartbeat timeout or VSS failed. If nothing else works, try moving the VM to another host (live migration) and back — that resets the state on the new host. Last resort: export the VM (with state) and reimport it. That clears any corrupt metadata.

Honestly, 1 out of 50 times I've seen a Critical status that didn't fix with Step 2 or Step 3. Stick with those two first, and you'll save yourself a lot of headache.