This article provides steps to make sure that a migrated Windows 11 virtual machine (VM) can start after you migrate it from VMware to Hyper-V.
Symptoms
After you migrate a VM from VMware to Hyper-V, the VM doesn't start. When this issue occurs, you don't see any specific error codes.
Cause
Windows 11 requires a TPM for Secure Boot and security compliance. The following settings affect VM startup:
- Secure Boot configuration
- Trusted Platform Module (TPM) configuration
Solution
For best results when you migrate a VM, we recommend that you follow the procedures that are provided in Convert a VMware VM to Hyper-V in the VMM fabric. That article provides detailed steps for how to prepare to migrate a VM and the migration process itself.
The following procedure provides steps that are specific to VMs that run Windows 11 or a later version.
Important:
- Make sure that you have administrative access to both the VMware and Hyper-V environments.
- Make sure that System Center Virtual Machine Manager (SCVMM) is installed and configured to manage and migrate the VM. For more information, see the "Start by bringing your vCenter server and the source ESXi hosts under SCVMM management" section of Convert a VMware VM to Hyper-V in the VMM fabric.
- Verify that the edition of Windows 11 that you're using is compatible with Hyper-V requirements, including TPM support.
To configure the security settings for the migrated VM, follow these steps:
-
In Hyper-V Manager, right-click the VM, and then select Settings.
-
Select Security. On the Security page, make sure that the following settings are selected:
- Secure Boot
- Trusted Platform Module (TPM)
-
Under Secure Boot, make sure that Template is set to Microsoft UEFI Certificate Authority.
-
Select OK to save the settings.
-
Restart the VM.
Additional support
If the VM still doesn't start after you complete these steps, contact Microsoft Support for further assistance. As part of your support request, specify that you have a Hyper-V or SCVMM issue.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
