I downloaded VirtualBox, knowing that my computer has VT-X, and I just created two VMs, but when I started them, I saw this error:
VirtualBox - Error
Failed to start the virtual machine Android.
(Details)
VT-x is not available (VERR_VMX_NO_VMX).Result Code:
E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
[Manually transcribed]
I have previously run VirtualBox on this PC flawlessly. Why am I getting this error now? How can I get VirtualBox to work?
Thank you Hrobky, this was helpful. At an ASUS i7 with a UEFI BIOS that does not allow to disable safe boot, on a Windows 10 without encryption, it was enough these 2 steps from your solution:
start->GPedit
Computer Config > Admin Templates > System > Device Guard >
Virtualization Based Security: Disabled
admin cmd: bcdedit /set hypervisorlaunchtype off
then reboot
with change these setting at BIOS
Boot / Launch CSM : Enable
Boot / Launch CSM / Boot Device Control : UEFI and Legacy OPROM
Boot / Fast Boot : Disabled
Boot / OS Type : Other OS
...while keeping following components installed! In your case the procedure could be shorter. Just omit the steps not relevant to your setup.
Related errors
VERR_VMX_NO_VMX
VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT
The culprit is Virtualization Based Security (VBS), which uses Windows embedded virtualization hypervisor (which doesn't conflict with HyperV). This how-to does not describe, how to run Hyper-V and VirtualBox simultaneously, nor how to run VirtualBox on top of Hyper-V hypervisor (as stated in Changelog 6.0.0), according to the Forum, this does not work on Win10 1703.
You will be able to switch between HyperV and VBS working versus VirtualBox requiring a reboot.
Remark: If you use BitLocker, have prepared your recovery key on a paper beforehand! :-] It shouldn't be required though. Control Panel -> BitLocker -> Backup Recovery Key
Here's the how-to:
Computer Config > Admin Templates > System > Device Guard > Virtualization Based Security: Disabled
DG_Readiness_Tool_v3.6.ps1 -Disable
The -disable
option adds a boot option to disable VBS and sets bootmgr to boot into it once. This is why we turned off SecureBoot once and why in turn we needed to suspend BitLocker.HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LsaCfgFlags
bcdedit /set hypervisorlaunchtype off
This disables the hypervisor and allows VirtualBox to run.Now you can switch between Hyper-V (and VBS running) and VirtualBox by bcdedit /set hypervisorlaunchtype auto
and bcdedit /set hypervisorlaunchtype off
respectively and rebooting. Don't ask me why VBS is running again despite the GPedit setting when hypervisorlaunchtype is auto - there might be some corporate settings and magic involved. Nevertheless, VirtualBox's VT-x is working :)
I definitely don't recommend leaving VBS turned off, as it could have something to do with Mimikatz / Kekeo protection which is quite an issue nowadays. Let's hope this wourkaround won't be necessary in a near future.
In the setup "system" section, "Acceleration" tab, uncheck "Hardware Virtualization: [ ] Enable VT-x/AMD-V" click "OK" button
User contributions licensed under CC BY-SA 3.0