

That’s it! Re-mount your new copied image in Hyper-V and boot right up! Even though this can be done with the free demo version, the UFS software is well worth the $70 to have in the toolbox and then you can do individual file recovery off just about anything.

Create a new empty VHDX file and mount / initialize it in Windows – this is where we’ll be recovering the data so make sure it is the same size as the corrupt VHD / VHDX.How to fix your corrupt VHD / VHDX file by copying to a new VHD / VHDX file

The free demo version of UFS Standard Recovery saved the day. Then I stumbled on this old reddit post where someone mentioned having luck with UFS Explorer to mount the VHD / VHDX files. It can’t be THAT broken, right? After an hour or so of Googling, I found many other programs that also couldn’t help. Trying to mount the disk image resulted in “Couldn’t mount file” – “The disk image file is corrupted.” Surely this is an easy fix but I was really surprised that Microsoft didn’t have some simple tool to fix. Had a server lose power over the weekend and the VHDX file of a client’s FreePBX Virtual Machine was corrupted.
