Fix VM Snapshot Disk Chain Broken (Hyper-V and VMware)

When This Error Hits You

You're minding your own business, maybe running a backup or trying to merge snapshots on a Hyper-V 2019 or VMware vSphere 7 host, then bam — error message saying the snapshot disk chain is broken. The VM won't boot, or it shows up as 'paused' or 'invalid'. This happened to a client last month whose VM had 12 snapshots (yeah, I know, don't ask) and the chain got corrupt after a storage outage. The exact trigger: either a failed merge operation (Hyper-V), a storage migration that got interrupted, or someone deleted a .vmdk or .avhd file manually — big mistake.

What Actually Causes This?

Think of VM snapshots like a chain of linked files. Each snapshot stores the changes since the last one. If one link in that chain gets damaged — say a .avhd file is missing, corrupted, or the parent pointer in the metadata is wrong — the whole chain breaks. Hyper-V and VMware both use this parent-child relationship. The error usually means the VM can't find the next disk in the chain, so it freezes. It's not a hardware failure most times. It's a software logic problem in the snapshot metadata.

The Real Fix: Step-By-Step

Important: Do not delete snapshots yet. That can make things worse.

Stop the VM and take a full backup of the VM folder. Copy all .vhd, .avhd, .vhdx, .vmdk files to safe storage. This is your safety net. I've seen people skip this and lose everything.
Identify the broken chain. On Hyper-V, open PowerShell as admin and run:
```
Get-VM -Name "YourVMName" | Get-VMSnapshot | Format-List Name,ParentSnapshotId,Id
```
On VMware, use the vSphere client and look at the snapshot manager — it shows the tree. Watch for any snapshot with a missing parent or child.
For Hyper-V: manually merge the chain using diskpart or PowerShell. The quickest fix is to use the Merge-VHD cmdlet. First, find the broken .avhd file. Then run:
```
Merge-VHD -Path "C:\VMs\YourVM\Snapshots\broken.avhd" -DestinationPath "C:\VMs\YourVM\fixed.vhdx"
```
This merges the broken snapshot into a new file. If that fails, try:
```
Optimize-VHD -Path "C:\VMs\YourVM\Snapshots\broken.avhd" -Mode Full
```
Then recreate the VM using the new .vhdx as the disk.
For VMware: use the vmkfstools command to repair the chain. SSH into the ESXi host, navigate to the VM's datastore folder, then run:
```
vmkfstools -x fix /vmfs/volumes/datastore1/YourVM/YourVM.vmdk
```
This checks and fixes the parent disk pointers. If the chain has multiple parent files, you may need to run it on each .vmdk. I've had to do this for a client's VM with three snapshots — fixed it in 10 minutes.
Create a new VM with the fixed disk. In hyper-V, create a new VM and attach the merged .vhdx as the existing disk. In VMware, after running vmkfstools, remove the broken snapshots from the inventory (but keep the files), then add the fixed .vmdk back as a new virtual disk. Then power on the VM.

What If It Still Fails?

If the VM still shows errors after the fix, check these things:

Check the disk chain file sizes: In Hyper-V, right-click the .avhd file and check Properties. If the file size is 0 bytes, it's empty — you can't fix that. You'll need to restore from backup.
Verify the parent disk path: In PowerShell, use:
```
Get-VHD -Path "C:\VMs\YourVM\Snapshots\broken.avhd" | fl ParentPath
```
If the parent path is wrong or points to a deleted file, you can use Set-VHD to update it:
```
Set-VHD -Path "C:\VMs\YourVM\Snapshots\broken.avhd" -ParentPath "C:\VMs\YourVM\CorrectParent.vhdx"
```
This is a last resort. Do it only if you're sure the parent is good.
Try restoring from your backup. If nothing works, restore the entire VM folder from the backup you made in step 1. Then delete all snapshots (using the Hyper-V manager or vSphere) so you start fresh. It's not ideal, but it's better than losing the VM.

Why This Fix Works

Most broken snapshot chains happen because the metadata got out of sync. The commands above re-link the files properly. I've used this method on dozens of VMs over the years — Hyper-V 2012 R2 through 2022, VMware 6.5 to 8. It's not perfect, but it saves data 9 times out of 10. Next time, keep snapshots to 3 max, and don't rely on them for backups — that's what real backup software is for.