Skip to content

Commit f1669bb

Browse files
authored
Update windows-11-vm-wont-start-after-migrating-from-vmware-to-hyper-v.md
Edit review per CI 6972
1 parent 77a7976 commit f1669bb

1 file changed

Lines changed: 15 additions & 15 deletions

File tree

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Windows 11 virtual machine doesn't start after you migrate it from VMware to Hyper-V
3-
description: Describes how to configure a Windows 11 virtual machine after you migrate it from VMware to Hyper-V
2+
title: Windows 11 Virtual Machine Doesn't Start After Migration From VMware to Hyper-V
3+
description: Describes how to configure a Windows 11 virtual machine after you migrate it from VMware to Hyper-V.
44
ms.date: 08/15/2025
55
manager: dcscontentpm
66
audience: itpro
@@ -11,46 +11,46 @@ ms.custom:
1111
- pcy:WinComm Storage High avail
1212
---
1313

14-
# Windows 11 virtual machine doesn't start after you migrate it from VMware to Hyper-V
14+
# Windows 11 VM doesn't start after migration from VMware to Hyper-V
1515

16-
This article provides steps to make sure that a migrated Windows 11 virtual machine can start.
16+
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.
1717

1818
## Symptoms
1919

20-
After you migrate a virtual machine from VMware to Hyper-V, the virtual machine doesn't start. You don't see any specific error codes.
20+
After you migrate a VM from VMware to Hyper-V, the virtual machine doesn't start. When this issue occurs, you don't see any specific error codes.
2121

2222
## Cause
2323

24-
Windows 11 requires a TPM for Secure Boot and security compliance. The following settings affect virtual machine startup:
24+
Windows 11 requires a TPM for Secure Boot and security compliance. The following settings affect VM startup:
2525

2626
- Secure Boot configuration
2727
- Trusted Platform Module (TPM) configuration
2828

2929
## Solution
3030

31-
For best results when you migrate virtual machines, 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 preparing to migrate and for the migration process itself.
31+
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.
3232

33-
The following procedure provides steps that are specific to virtual machines that run Windows 11 or a later version.
33+
The following procedure provides steps that are specific to VMs that run Windows 11 or a later version.
3434

3535
> [!IMPORTANT]
3636
>
3737
> - Make sure that you have administrative access to both the VMware and Hyper-V environments.
38-
> - Make sure that System Center Virtual Machine Manager (SCVMM) is installed and configured to manage and migrate the virtual machine. For more information, see [Convert a VMware VM to Hyper-V in the VMM fabric: Start by bringing your vCenter server and the source ESXi hosts under SCVMM management](/system-center/vmm/vm-convert-vmware?view=sc-vmm-2025#start-by-bringing-your-vcenter-server-and-the-source-esxi-hosts-under-scvmm-management).
38+
> - 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).
3939
> - Verify that the edition of Windows 11 that you're using is compatible with Hyper-V requirements, including TPM support.
4040
41-
To configure the security settings for the migrated virtual machine, follow these steps:
41+
To configure the security settings for the migrated VM, follow these steps:
4242

43-
1. In Hyper-V Manager, right-click the virtual machine, and then select **Settings**.
44-
1. Select **Security**, and then on the **Security** page, make sure that the following settings are selected:
43+
1. In Hyper-V Manager, right-click the VM, and then select **Settings**.
44+
1. Select **Security**, open the **Security** page, and then make sure that the following settings are selected:
4545

4646
- **Secure Boot**
4747
- **Trusted Platform Module (TPM)**
4848

49-
1. Under **Secure Boot**, make sure that **Template** is set to **Microsoft UEFI Certificate Authority**
49+
1. Under **Secure Boot**, make sure that **Template** is set to **Microsoft UEFI Certificate Authority**.
5050

5151
1. Select **OK** to save the settings.
52-
1. Restart the virtual machine.
52+
1. Restart the VM.
5353

5454
## Additional support
5555

56-
If the virtual machine 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.
56+
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.

0 commit comments

Comments
 (0)