Vagrant up - VBoxManage.exe error: VT-x is not available (VERR_VMX_NO_VMX) code E_FAIL (0x80004005) gui headless [closed]

Answer 1

If you are getting the above error on Windows 10 Pro then you can disable the Hyper-V. Hyper-V is default enable in the Windows 10. You can either use Hyper-V or Virtual Box. So, to use the Virtual box you have to disable hyper-v in windows, you can follow following steps to do -

1. Search Control Panel
2. Click on Uninstall a program
3. Turn Windows features on or off
4. Unselect the Hyper-V option.
5. Click on OK
6. Restart the system to apply the changes.

Answer 2

Along with Hyper-V option, I had to uncheck "Containers" Windows feature to have my Vagrant work.

Answer 3

This is what helped me:

1. Remove Hyper-V and install Hypervisor platform.

   • In the elevated Powershell prompt do:

     Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
     Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform
     

   • Restart

2. Disable Windows Defender Credential Guard

   • "Local Group Policy Editor" → "Computer Configuration" → "Administrative Templates" → "System" → "Device Guard" → "Turn on Virtualization Based Security" → Set to "Disabled"

   • Delete the following registry settings:

     • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LsaCfgFlags
     • HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceGuard\LsaCfgFlags

   • Restart

3. Delete the Windows Defender Credential Guard EFI variables

   • In the elevated command prompt do:

     mountvol X: /s
     copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
     bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
     bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
     bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
     bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO
     bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
     mountvol X: /d
     

   • Restart

4. Disable virtualization-based security

   • Delete all registry keys under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceGuard\* (but keep DeviceGuard itself).

   • Restart

See also: Disable Windows Defender Credential Guard

Answer 4

The only thing that worked for me was running the installers and doing a repair for VM VirtualBox and Vagrant.

Answer 5

Although this is an old question, but I've still encounter it recently.

This is what worked for me on my i7-3770 3.40GHz, Z77 extreme motherboard running Windows 10.

In Windows, disable Hyper-V:

1. Open up a PowerShell or CMD session as Administrator.
2. Type the following command: dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All
3. Windows will ask you to restart.

In the bios:

1. Disable >>> Intel Virtualization Technology, vt-d
2. Save the bios settings and allow it to restart and boot into Windows.
3. Shutdown the computer (I've tried just restarting and it didn't work)
4. Power up the computer, go into the bios and re-enable the above disabled settings.
5. Save, restart.

Download the Intel Utility to check.

You should now see it been supported:

If it still doesn't work, try re-enabling Hyper-V first then following the steps above.

Answer 6

Stop hyper-v service running by default in Windows 8/10, since it blocks all other calls to VT hardware.

Additional explanation here: https://social.technet.microsoft.com/Forums/windows/en-US/118561b9-7155-46e3-a874-6a38b35c67fd/hyperv-disables-vtx-for-other-hypervisors?forum=w8itprogeneral

Also as you have mentioned, if not already enabled, turn on Intel VT virtualization in BIOS settings and restart the machine.

---

To turn Hypervisor off, run this from Command Prompt (Admin) (Windows+X):

bcdedit /set hypervisorlaunchtype off

and reboot your computer. To turn it back on again, run:

bcdedit /set hypervisorlaunchtype on

If you receive "The integer data is not valid as specified", try:

bcdedit /set hypervisorlaunchtype auto

-- credit Tj Kellie