Share via

I cannot enable the nested VT-x/AMD-V to both VMWare Workstation and Virtualbox using Windows 11 Pro.

Anonymous
2024-05-16T17:48:35+00:00

I cannot enable the nested virtualization VT-x/AMD-V to both VMWare Workstation and Virtualbox (already in latest versions) using my Windows 11 Pro. Virtualization is already enabled in BIOS.

To troubleshoot, I already disabled the following:

  1. Windows Features:
    • Hyper-V
    • Virtual Machine Platform
    • Windows Hypervisor Platform
  2. Core Isolation > Memory integrity
  3. Credential Guard > Virtualization Based Security from Not configured to Disabled

Can you share me how to fix this please.

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-05-28T02:45:44+00:00

    Hi,

    Thank you for posting in the community.

    To enable nested virtualization for VirtualBox or VMware Workstation, Hyper-V need to be disabled on Windows. Please open Windows PowerShell or Command Prompt as administrator, run bcdedit and make sure hypervisorlaunchtype is set to Off. If not, run 

    bcdedit /set hypervisorlaunchtype Off

    then restart the computer.

    If the above step doesn't work, you might need to enable nested virtualization manually. For VirtualBox, you can use the VBoxManage command

    VBoxManage modifyvm <vmame> --nested-hw-virt = on

    Since these are third-party virtualization software, it's also recommended to contact Oracle/VMWare to confirm how to set up nested virtualization.

    3 people found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-05T22:44:28+00:00

    This issue is all over internet for years. It seems like even microsoft does not know how to fix this. Best of Luck!

    1 person found this answer helpful.
    0 comments