VHDX files corrupted after V2V migration

[yoyodingo]

I've been migrating VMs from VMWare to Hyper-V using Starwind V2V. A couple months ago when we were testing hypervisor options this worked fine. Now, after going back to it a month later, booting starts failing with inaccessible boot image errors and Secure Boot errors, depending on VM settings. I'm unable to mount the converted VHDX files to inspect them and get this error:
"Couldn't Mount File: The disc image file is corrupted". I'm also unable to attach them to a VM due to similar Hyper-V errors.

I am converting from ESXi v7 to Windows Server 2022. I have used multiple ESXi hosts, multiple Hyper-V hosts, and multiple VMs. They all fail the same way.

[yoyodingo]

Unfortunately, trying to convert VMDK files individually won't be of any value to us, as we can use a Microsoft tool to do that. Starwind V2V has value for us because it can do a warm conversion.

[yaroslav (staff)]

See this thread viewtopic.php?f=15&t=6763&p=36723&hilit=google#p36723 and https://drive.google.com/file/d/1hDP4gl ... Ea_5p/view

[yoyodingo]

That older version generated valid VHDX files, but the converted VMs fail Secure Boot, and only boot with Secure Boot disabled.

[yaroslav (staff)]

Thanks for your update. Yes, sometimes it is necessary to disable secure boot after conversion.