![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 63%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEJ%3C/text%3E%3C/svg%3E)
System Center Virtual Machine Manager
A family of System Center products that enable enterprise-wide management of virtual machines.
It seems that the issue you are encountering is due to the VM being created as a Generation 1 (Gen1) VM in Hyper-V, while your source VMware VM was configured with UEFI firmware. Hyper-V Gen1 VMs use BIOS firmware, which is not compatible with UEFI.
To resolve this issue, you should convert the VMware VM to a Generation 2 (Gen2) VM in Hyper-V. Here are the steps you can follow:
- Ensure the VMware VM is in a Stopped State: Before conversion, make sure the VM is powered off and there are no snapshots associated with it.
- Use the SCVMM to Convert: When you are in the conversion wizard, make sure to select Generation 2 for the virtual machine configuration if the source VMware VM is configured with UEFI firmware.
- Verify Settings: After the conversion, check the settings of the new VM in Hyper-V Manager to ensure that it is set to use UEFI firmware and that the boot settings are correctly configured.
- Boot Order: Ensure that the boot order in the VM settings is set to boot from the correct virtual hard disk.
If you follow these steps, it should help you avoid the boot failure issue you are experiencing.