Hyper-V checkpoint recovery

A failed AVHDX merge must be mapped from child to parent before any checkpoint file is deleted or renamed.

Hyper-V checkpoints store changes in AVHDX differencing disks. Backup failures, storage exhaustion, file locks, missing parents, interrupted merges, or manual file operations can leave a VM unable to start or using an incomplete chain.

Start a recovery case Call 682-325-7712

Understand the symptom

Each differencing disk depends on the exact parent and sequence above it.

WHY

What is happening

Hyper-V records ParentPath and disk identifiers through a chain. A merge writes child changes into its parent, so order, free space, locks, and parent integrity matter. Orphaned files not visible in Hyper-V Manager may still contain the newest guest writes.

What you may see

Symptoms that change the recovery path.

Checkpoint deletion fails

Hyper-V cannot complete the expected background merge.

AVHDX files remain after backup

A temporary recovery checkpoint was orphaned or cleanup was interrupted.

VM cannot locate a parent disk

The differencing chain is broken, moved, renamed, or incomplete.

Host volume ran out of space

Merge or backup operations stopped before committing all changes.

Protect the source

Actions that can make the situation worse.

Deleting AVHDX discards guest changes

The newest filesystem and application state may exist only in a child disk.

Wrong merge order corrupts the chain

A child must be associated with its correct parent generation.

Starting an older VHDX causes divergence

The guest can write a new history while newer changes remain orphaned.

Do this now

Safe steps before evaluation.

Shut down the affected VM

Stop guest writes and backup jobs without deleting checkpoint files.

Copy the complete VM folder

Preserve VMCX, VMRS, VHDX, AVHDX, MRT, RCT, logs, and permissions.

Map the chain read-only

Record ParentPath, disk identifiers, timestamps, sizes, and Hyper-V checkpoint inventory.

Document storage exhaustion or locks

Save host free space, event logs, antivirus, backup, CSV, and cluster state.

NEPFOSYS process

How a data-first evaluation proceeds.

Checkpoint-chain analysis

NEPFOSYS maps each AVHDX to its parent and identifies the newest coherent state.

Protected chain copies

Repairs and merges are tested on duplicated virtual disks.

Guest validation

Recovered disks are mounted read-only and priority applications and files are checked.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can I delete old AVHDX files?

No. Microsoft warns not to delete them directly because they may contain active checkpoint data.

Which order should checkpoints merge?

The exact child-parent chain must be established first. Manual merging without that map can combine incompatible states.

Why preserve files not shown in Hyper-V Manager?

Orphaned AVHDX files created by backups can contain newer guest writes even when the UI does not list them.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case