Mount-VHD -Path E:\VHDs\prod_db_backup_2024.vhd -ReadOnly The error was cryptic: The VHD is corrupted. The block allocation table is inconsistent.

He opened PowerShell as Administrator and ran:

The sector size was misaligned. The VHD's internal "footer" (the last 512 bytes of the file) was intact—he confirmed that with a hex dump—but the BAT (Block Allocation Table) had a phantom block pointing to a sector that didn't exist.

Then he ran:

It was 2:00 AM on a Saturday. Marcus Chen, a senior cloud architect, stared at a single line of red text in his terminal: "Failed to mount 'prod_db_backup_2024.vhd'. The file is corrupted."

The Ghost in the Machine: A VHD Repair

chkdsk Y: /f /r /x CHKDSK ran for 90 minutes. It reported fixing three orphaned files and two bad clusters in the MFT (Master File Table). But when he unmounted and tried to attach the VHD again in Hyper-V? Same corruption error. CHKDSK fixed the filesystem inside the VHD, but not the container itself.