We have a Windows 10 vmdk that fails on boot with "OS not found." We need files stored on that VM. (Bad practice, I know.)
We tried:
- Boot from a variety of LiveCDs. Fails because vmdk is corrupt and LiveCD OS can not see .vmdk-resident partitions.
- Mount vmdk using vmware command-line utility. Fails same reason.
- Mount with 7-zip, PowerISO, OSFMount. All fail, vmdk unreadable.
- Create new guest OS using same files. Fails, returns same error.
- vmware command-line repair. Fails, returns no result.
The data stored in the vmdk is intact. We iknow this because we applied a test (read-only) version of a particular $700(!) tool that displays 100% of the original Windows file-system. The vendor states that any visible file is recoverable in the full version of their tool.
Question: what is this very expensive software doing to analyze and display the contents of the vmdk, and how can we do this using other, more accessible tools?
Thanks for your help.