Hyper‑V Parent‑Child path repair

Question

Hyper‑V Parent‑Child path repair

Hafiz Othman 20

Hello,

I’ve been troubleshooting an issue with Hyper‑V checkpoint chains after moving them to new storage. Once relocated, the guest VMs fail to boot and display the error “Parent VHDX Not Found.” It appears that the relative path bindings between parent and child disks were broken during the transfer.

I’ve already checked disk permissions and verified that the differencing disks are intact, but the problem persists. Could someone please explain the correct procedure or PowerShell syntax for repairing parent‑child relative path bindings using Set‑VHD -ParentPath?

Any guidance or examples from those who’ve resolved similar issues would be greatly appreciated

0 comments

2 answers

Your answer

Answer 1

Hello Hafiz,

The error you’re seeing is expected when differencing disks lose their parent reference after being moved. Hyper‑V stores the parent path inside the child VHDX metadata, and if the relative or absolute path no longer matches, the VM cannot resolve the chain. The correct way to repair this is with Set‑VHD -ParentPath, but you must point it to the exact parent VHDX file in its new location.

For example, if your child disk is D:\VMs\Guest01\Guest01-Checkpoint-Auto.vhdx and the parent base disk is now located at E:\VMStorage\BaseDisks\Guest01.vhdx, you would run the following from an elevated PowerShell session:

powershell

Set-VHD -Path "D:\VMs\Guest01\Guest01-Checkpoint-Auto.vhdx" -ParentPath "E:\VMStorage\BaseDisks\Guest01.vhdx"

Repeat this for each differencing disk in the chain until all references point correctly. If you have multiple checkpoints, you need to repair them in sequence, starting from the most recent child back to the base. You can verify the chain with:

powershell

Get-VHD -Path "D:\VMs\Guest01\Guest01-Checkpoint-Auto.vhdx" | Select-Object ParentPath

This will confirm whether the binding is correct. Also ensure NTFS permissions are consistent; the Hyper‑V Virtual Machine Management Service (VMMS) must have access to both parent and child disks. If you moved storage across volumes, double‑check that the SYSTEM account retains full control.

One important note: if the parent VHDX was renamed or altered during the move, you must restore its original identity. Hyper‑V differencing disks are sensitive to both path and file integrity. If the parent file is missing or corrupted, the child cannot be repaired.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

HL.

Answer 2

If the parent disk was only moved or renamed, the parent-child link can be repaired by pointing the child disk to the correct parent path.

Inspect the child disk to confirm what parent it expects:

Get-VHD -Path <AVHDX path> | fl *

This shows the current chain information, including the parent path.

Repair the link with Set-VHD:

Set-VHD -Path <child.vhdx> -ParentPath <correct_parent.vhdx>

Set-VHD can set the ParentPath property of a virtual hard disk.

If the chain is valid after relinking, merge if needed:

Merge-VHD -Path <child AVHDX> -DestinationPath <parent VHD>

If checkpoints are orphaned or not visible, inspect the VM disk chain first:

Get-VMHardDiskDrive -VMName <VMName> | ForEach-Object { Get-VHD -Path $_.Path | Select-Object Path, ParentPath, VHDType }

Then identify any .avhdx files that are not visible in Hyper-V Manager and merge them in the correct order.

After repair or merge, verify the VM is attached to the correct merged .vhdx and then start the VM.

Important limitation: if the parent disk was changed, not just moved or renamed, relinking is not a supported recovery path. The accepted guidance states that Set-VHD -ParentPath works only when the parent’s internal structure is still identical to what the child expects. If the parent was expanded, recovery is not supported; the recommended path is to restore the original parent from backup and then reattach the differencing disks.

Before manual repair or merge, back up all VHDX/AVHDX files. Incorrect merge order or attaching the wrong parent can cause data loss or make the chain unusable.

References: