Hyper-V virtual disk recovery
A virtual machine may fail because of physical storage, RAID, CSV or ReFS damage, a missing VHDX, a broken AVHDX checkpoint chain, an interrupted backup merge or corruption inside the guest.
Understand the symptom
A base VHDX can have one or more differencing AVHDX files created by checkpoints or backup software. Each child references a parent and contains newer changed blocks. Missing, renamed, mismatched or partially merged files can break the chain. The virtual storage may also sit on RAID, SMB, iSCSI, Cluster Shared Volumes, Storage Spaces or ReFS, so lower-layer health must be established before repairing virtual metadata.
What you may see
Paths, permissions, storage presentation or a chain member may be missing.
A backup or deletion operation may have stopped with AVHDX files still active.
The differencing disk references a parent whose ID, path or state no longer matches.
The chain may attach while guest data remains inconsistent after an abrupt event.
Protect the source
Checkpoint files can contain the only current version of changed guest sectors.
An incorrect or interrupted merge can alter the base and collapse useful recovery states.
Boot writes logs, journals, updates and application data into the current disk chain.
Do this now
Prevent restarts, checkpoint creation, merge retries, replication and storage migration.
Preserve VHDX, AVHDX, VM configuration, runtime state, logs and backup metadata.
Document host, cluster, CSV, RAID, SAN, SMB, ReFS, snapshots and recent failures.
Identify critical guest files, databases and the minimum useful recovery point.
NEPFOSYS process
Physical disks, RAID, volumes and file systems are protected before virtual-disk changes.
Parent IDs, paths, generation order and merge state are analyzed on copies.
Recovered virtual disks are checked for file-system and application consistency in isolation.
A clear next step
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 reviewQuestions, answered
No. An AVHDX may contain current guest blocks that have not been merged into its parent. Deleting it can remove part of the virtual disk state.
Not on the only copy when the chain or underlying storage is damaged. Preserve the complete chain and verify parent relationships first.
No. Guest file systems, databases and applications can be inconsistent even when the virtual disk attaches and starts.
DFW local · Nationwide mail-in