Broken VHD after Conversion VMware to Hyper-V

[ms220188]

Hello everyone,

Im using the Starwind Converter right now to migrate from VMware to Hyper-V. But with some machines i got the issue that the converted VHD is not readable or damaged, when i try to start up the VM on Hyper-V. Mounting the VHD with Windows Board Tools also fails with the message, that the Drive is not readable or broken.

I converted nine VMs so far and the problem only occurs with three of them. All the others converted just fine and booted up without any issues. I compared the settings of those machines and i can see no real diffences in their configuration. The only thing I noticed is, that the ones having the issue are running on an older VM-Version. So i tried to Upgrade that on one machine and start over with the conversion, but the issue remains. So the only clue i have now is that the affected machines might be older ones.

Can I do anything to these machines in advance of the conversion or afterwards to get them running? I'd be thankful for any hint.

With kind regards
Martin

[yaroslav (staff)]

Hi,

For those few that break, try an older version of the software. Please see if the error you face looks like one from this thread viewtopic.php?f=15&t=6763&p=36723&hilit=google#p36723

[rice2]

Are there specific tools or methods available for troubleshooting and repairing VHD files that have been converted but are failing to mount or boot in Hyper-V? Thanks

[yaroslav (staff)]

The VM does not like the destination because of the driver conflict or wrong controller used.
You can try removing VMware or Integration tools before conversion.