VT-x is not available (0x80004005) on Win 14316

[fishouttawater]

Installed Win 14316, VB wouldn't run (as with previous win release), installed latest testbuild 5.0.17 r106359 and it completed install successfully (unlike previous testbuild setup that wouldn't run at all)
Tried to run VB and got error about checking if kernel driver was loaded, rebooted, VB started fine.

Run Ubuntu guest and:

Failed to open a session for the virtual machine Ubuntu64.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I've never required VT-x before, system configured with 1gig ram.

and from vbox.log:
00:00:01.647318 VM: fHMEnabled=true (configured) fRecompileUser=false fRecompileSupervisor=false
00:00:01.647320 VM: fRawRing1Enabled=false CSAM=true PATM=true
00:00:01.647718 VMSetError: F:\tinderbox\win-5.0\src\VBox\VMM\VMMR3\HM.cpp(576) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
00:00:01.647740 VMSetError: VT-x is not available
00:00:01.773695 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=0
00:00:01.773926 Console: Machine state changed to 'PoweredOff'
00:00:01.786880 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))
00:00:01.865549 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1280x919
00:00:01.865589 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={7303a66d-433b-25a4-f9a8-fcadf87e0c2a} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:01.865755 GUI: Aborting startup due to power up progress issue detected...

[mpack]

Please post complete VM logs, as zipped attachments.

[jonw757]

I had this same issue on VirtualBox test build 5.0.17-106359 on Windows 10 Build 14316. I ended up updating the BIOS on my PC which the latest was still from 2013, previous from 2012. Once I did that, it disabled the virtualization technologies, which I re-enabled, booted up and voila, 64-bit options were now available in VirtualBox and my 2012 R2 VM booted right up.

So, update your BIOS and try enable/disable of the VT in the BIOS.

[TimDugan]

After installing latest (VirtualBox-5.0.17-106359) and restarting windows (build 14316) VB (and Ubuntu 14.04 LTS) works fine. No issues

[fishouttawater]

Oh FFS...I forgot that when I was enabling Bash for Windows I noticed Hyper-V wasn't enabled, so enabled it just for S&Gs...

It was using VT-x so Virtualbox couldn't. Removed Hyper-V and all is well. It would REALLY be nice if Virtualbox pointed this out in the error message. "Hey dummy, disable any other Hypervisors" would have been welcome.

[Downes]

That was my problem as well. I had hyper-V turned on, making virtualization unavailable for Vagrant. I had previously enabled the Bash shell to run Docker. I used optionalfeatres.exe to turn it off, then ran vagrant up without an issue. I second the recommendation that users be advised to turn off other virtualization systems before starting Vagrant.

[Downes]

p.s. relevant section from log to assist in search by future people encountering this problem:

VM: fHMEnabled=true (configured) fRecompileUser=false fRecompileSupervisor=false
00:00:02.796579 VM: fRawRing1Enabled=false CSAM=true PATM=true
00:00:02.797013 VMSetError: F:\tinderbox\win-5.1\src\VBox\VMM\VMMR3\HM.cpp(716) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_NO_VMX
00:00:02.797042 VMSetError: VT-x is not available
00:00:02.924150 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VT-x is not available (VERR_VMX_NO_VMX)}, preserve=false aResultDetail=0