Share via

Windows 11 Home: Unable to run nested VMs in VMWare Workstation due to Hyper-V conflict

Anonymous
2024-10-09T17:25:48+00:00

Hi,

I got a new laptop came with Windows 11 Home. I installed VMWare Workstation Pro to run eve-ng and GNS3 netsed VMs. However, it doesn't start.

I have been struggling to get it running. I tried almost all the methods mentioned in many forums and youtube. I tried disabling core isolation, disabling VBS, turning off features and stopping / disabling Hyper-V services to no avail.

This is the current state of my systeminfo output

Virtualization-based security: Status: Not enabled

                           App Control for Business policy: Enforced

                           App Control for Business user mode policy: Audit

                           Security Features Enabled:

Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.

I believe if I can somehow change Hyper-V requirements conditions to all "Yes", then I've disabled Hyper-V from interfering with the netsed VMs in VMWare workstation. I wasted a week trying to fix this issue. Kindly help.

*** Moved from Windows / Windows 11 / Devices and drivers ***

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments
Accepted answer
  1. Anonymous
    2024-10-11T03:37:21+00:00

    Hi,

    There could be conflicts between the hypervisors if you use VMWare along with Hyper-V. Make sure the Hyper-V and Virtual Machine Platform features are turned off.

    Try the following command to fully disable Hyper-V.

    dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All

    Also set the hypervisor launch type to Off. You can do this by running the following command in PowerShell as an administrator:

    bcdedit /set hypervisorlaunchtype off
    2 people found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-10-12T16:05:21+00:00

    Thanks for your reply.

    I was able to solve the issue after doing a clean install of Windows.

    Also, I did the following two things in addition to your suggestion

    1. Core Isolation - Turn off Memory
    2. Change the registry setting "EnableVirtualizationBasedSecurity" to 0.
    0 comments