VHDX region-table recovery
A VHDX region table tells Hyper-V where essential structures such as the metadata region and block allocation table are stored. If the table, its checksum, or a required entry is damaged, the disk may be rejected before guest partitions are examined.
Understand the symptom
VHDX stores two region-table copies. Each table has a signature, checksum, entry count, and GUID-based entries with file offsets, lengths, and required flags. Recovery compares both copies, headers, file layout, BAT boundaries, metadata fields, and payload evidence rather than assuming the second table is automatically current or valid.
What you may see
Hyper-V, Mount-VHD, or a parser rejects the disk before it exposes a volume.
Implementations may differ in how strictly they validate checksums, duplicate entries, and required regions.
The beginning of the file may be present while a table, log, BAT, or payload range is incomplete.
A child disk can be valid yet unusable when its parent region metadata cannot be interpreted.
Protect the source
A plausible table can still direct reads into unrelated file regions.
Writing before both original tables are preserved removes an important comparison source.
A completed clone is not proof that every guest block was mapped correctly.
Do this now
Disable starts, merges, replication, backup, export, and storage optimization.
Copy VHDX, AVHDX, VMCX, VMRS, exports, logs, and storage snapshots together.
Save host events, PowerShell output, file size, timestamps, and the first reported invalid offset.
If the datastore reports I/O errors, protect it before a full-file scan.
NEPFOSYS process
NEPFOSYS evaluates both tables and their checksums against the selected header and file layout.
Candidate entries are validated using metadata, BAT, log, and guest structures without changing the source.
Partitions, file systems, databases, and requested files are checked from the reconstructed view.
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
Redundant copies improve resilience, but both still must be validated against the same disk generation and physical layout.
No. Region offsets, lengths, metadata, and allocation structures belong to the original disk.
Not necessarily. Compact control metadata can block access while much of the payload remains present.
DFW local · Nationwide mail-in