Merge pull request #9514 from v-tappelgate/AB#6972-Migrate-W11-VM-to-Hyper-V

AB#6972: Migrate W11 VM from VMware to Hyper-V

Author: v-tappelgate

support/windows-server/toc.yml

@@ -2836,8 +2836,10 @@ items:
       href: ./virtualization/get-vmnetworkadapter-doesnt-report-ip-addresses.md
     - name: Virtual Machines enter the paused state
       href: ./virtualization/virtual-machines-enter-paused-state-low-disk-free.md
-    - name: virtual machine shutdown actions don't run
+    - name: Virtual machine shutdown actions don't run
       href: ./virtualization/vm-shutdown-actions-not-run.md
+    - name: Windows 11 virtual machine doesn't start after you migrate it from VMware to Hyper-V
+      href: ./virtualization/windows-11-vm-wont-start-after-migrating-from-vmware-to-hyper-v.md
   - name: Virtual machine will not boot
     items:
     - name: 0x8000FFFF error when you start VM

support/windows-server/virtualization/windows-11-vm-wont-start-after-migrating-from-vmware-to-hyper-v.md

@@ -0,0 +1,56 @@
+---
+title: Windows 11 Virtual Machine Doesn't Start After Migration From VMware to Hyper-V
+description: Describes how to configure a Windows 11 virtual machine after you migrate it from VMware to Hyper-V.
+ms.date: 08/15/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika
+ms.custom:
+- sap:virtualization and hyper-v\virtual machine state
+- pcy:WinComm Storage High avail
+---
+
+# Windows 11 VM doesn't start after migration from VMware to Hyper-V
+
+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](/system-center/vmm/vm-convert-vmware?view=sc-vmm-2025). 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](/system-center/vmm/vm-convert-vmware?view=sc-vmm-2025#start-by-bringing-your-vcenter-server-and-the-source-esxi-hosts-under-scvmm-management).
+> - 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:
+
+1. In Hyper-V Manager, right-click the VM, and then select **Settings**.
+1. Select **Security**. On the **Security** page, make sure that the following settings are selected:
+
+   - **Secure Boot**
+   - **Trusted Platform Module (TPM)**
+
+1. Under **Secure Boot**, make sure that **Template** is set to **Microsoft UEFI Certificate Authority**.
+
+1. Select **OK** to save the settings.
+1. 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.