Saturday, March 21, 2026

Getting 'Enabled Nested VT-x/AMD-V' Working in VirtualBox

This was a way more complicated process than I ever wanted it to be; I went down so many rabbit holes, I just hope I can stop myself or anyone else from doing this in the future.

  1. Turn off Core Memory Integrity on your host as it conflicts with being able to turn on this option.
    • Go to Windows Security > Device Security > Core Isolation details, and toggle Memory Integrity off, as it conflicts with nested virtualization.
  2. In the VM client, run this command in an elevated command prompt
    • bcdedit /set hypervisorlaunchtype off
  3. Now you can turn on "Enabled Nested VT-x/AMD-V" in your settings of your VM client.
  4. With luck the VM will start up. If not, remove all the VM's Hyper-V/Windows Features. Disable these in "Turn Windows features on or off" and restart.


0 Comments:

Post a Comment

<< Home