Hyper-V VM Stuck on Starting – Quick Fix That Works

Yeah, that's frustrating. VM sits there on 'Starting' like it's waiting for a bus that never comes. Don't reboot the host yet — there's a straightforward fix.

The Fix: Kill the Saved State

The real fix is to remove the saved state file. Saved state is like a snapshot of the VM's RAM — it can get corrupted after a power failure, a host crash, or a bad checkpoint.

1. Open Hyper-V Manager.
2. Right-click the stuck VM and select Delete Saved State.
3. Wait 10–20 seconds. The VM should show 'Off' instead of 'Starting'.
4. Now start the VM normally.

If the option is grayed out, use PowerShell:

Get-VM "YourVMName" | Remove-VMSavedState

That clears the saved state instantly. I've used this on Windows Server 2012 R2 through 2022 — same deal.

Why This Works

The saved state file (.vsv) holds the VM's memory and CPU state. When the host restarts or Hyper-V service restarts, it tries to restore that state. If the file is corrupted — say, from an unexpected shutdown or a flaky storage subsystem — the VM hangs forever trying to load it.

Deleting that file forces Hyper-V to treat the VM as fully off. No state to reload, no hang. You lose whatever was in the VM's RAM at the time, but that's better than a dead VM.

Less Common Variations of the Same Issue

Corrupted VHDX

Sometimes the saved state is fine, but the VM still won't start. Try this:

1. Shut the VM down (or force stop it).
2. Run chkdsk /f on the host drive where the VHDX sits.
3. Mount the VHDX as a drive on the host:

Mount-VHD -Path "C:\VMs\YourVM.vhdx" -ReadOnly
# Check for errors with:
Repair-VHD -Path "C:\VMs\YourVM.vhdx" -Scan

If the VHDX is corrupt, you'll see errors. You can try Repair-VHD -Path "C:\VMs\YourVM.vhdx" -Scan and then -Repair if it's recoverable. But if the disk is badly borked, you'll need a backup.

Stuck Checkpoints

Another one I've seen: the VM has a checkpoint that's partially applied. Hyper-V tries to apply it, gets stuck. Fix:

1. Open Hyper-V Manager, go to the checkpoints tab for that VM.
2. Delete any checkpoints that show 'Applying' or 'Created' with a yellow icon.
3. If that fails, use PowerShell:

Get-VMSnapshot -VMName "YourVMName" | Remove-VMSnapshot

This wipes all checkpoints. You lose the ability to roll back, but the VM boots. I've done this more times than I count on busy file servers.

Host Resource Starvation

Rare, but a host with zero free RAM or disk space can cause a VM to hang on start. Check the host's disk space — if it's below 1%, Hyper-V can't allocate memory for the VM. Free up space or add a page file to the host.

Prevention: Don't Let It Happen Again

• Never hard-power-off a Hyper-V host without gracefully shutting down VMs first. That's how saved states get corrupted.
• Limit automatic checkpoints. In Windows Admin Center, turn off auto checkpoints for VMs that don't need them. Fewer checkpoints = fewer chances for corruption.
• Monitor host disk space. Set up an alert when free space drops below 10%.
• Use a dedicated storage volume for VHDX files. Don't mix them with the OS drive. It reduces I/O contention and makes disk errors easier to isolate.
• Enable VM Guest Integration Services. It helps the VM shut down cleanly when the host restarts.

That's it. 80% of the time, deleting the saved state fixes it. The other 20% is VHDX corruption or bad checkpoints. You won't lose the VM's data in any of these scenarios — just the last few seconds of work. Don't overthink it.