Probably, but I'm stubborn. I'd like to figure out what the issue is exactly so that I can deal with it more easily later in case it happens to a critical system that can't be rebuilt.

I did a P2V as a Gen 2.

I'll retry as Gen 1, then Disk2VHD

I did an instant recovery from Veeam, and no dice. Exact same issue.

That's going to be the next option.

I just ran a V2V as a Gen 1, and no go. The disk is a GPT in VMWare so it is created as a GPT and that isn't compatible with Gen 1.

I've created a gen 1 VM from scratch and added the VHDX that I created earlier to the IDE and it doesn't boot either. I just get a boot failure message in Hyper-V. Most likely because the Gen 2 is GPT and not MBR. I've only tried to convert the VMWare into a Gen 2, never Gen 1. So now I'm attempting...

It never gets into windows. Just the recovery console. From there there isn't much I can do.

OK that's what I thought. I just keep running into brick walls to get the correct drivers going. I've removed all the VMWare tools prior to doing the migration... When I enable recovery mode, and boot into recovery mode, do I need to do the other links to reset the VM back to using IDE? Or are there...

I'm in the process of migrating VMs from VMWare 7.1 to Hyper-V, and I've successfully used V2V for the linux machines. However, I'm trying to get a couple of Windows Server 2012R2 machines to migrate to Hyper-V and it just isn't working. When the migration is complete, I try starting the Hyper-V vir...