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

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.

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...