Vt x is not available virtualbox windows 10

Hello,
i use VirtualBox from a lot of year.
Tomorrow windows 10 get the last update (Version 10.0.15063) and after it mi windows Xp Vm doesn’t start any more

When Virtual box give VERR_VMX_NO_VMX error tipically the virtual-t in bios isn’t active.
In may case nothing is changed, only windows make an update.

I already try to unistall and install Virtual Box, but nothing chage.
I already try to stop all services where hyper-v is named.

I finish the idea. I already search this error on the comunity, but i have not find a right solution for my problem.

Sameone has already fixed my problem?
Thanks you for support.
Best regards
Davide Cossano.

I had already stopped all services about hyper-v
i tryed to unistall hyper-v from windows component
but wasn’t enought…

I solved using this command from console:

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Thanks you for you support.
Regards
Davide.

This appears to be happening again due to Microsoft issuing an update on the normal Windows 10 release track. They are enabling Hyper-v to one of their security issues.

Just thought I’d mention this, since mpack gets tired of regurgitating the same thing, over and over.

I KNOW I turned OFF Hyper-v when installing VirtualBox. It WAS working fine, and then MS Updates happened. Suddenly Hyper-v was back on, and VBox failed to open my XP VM.

Lesson learned: Check that Hyper-v is not enabled, even if you know you have previously disabled it. M$ is turning it back on for you.

Thank You for your support!

It seems to be back and disabling Hyper-V is no longer the solution…

I recently updated Windows to Build 17074.rs_prelrease.180106-2256 and now I find that my vbox linux vm no longer starts up with:

Code: Select all   Expand viewCollapse view

VT-x is not available (VERR_VMX_NO_VMX).

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

I have double checked that Hyper-V is not enabled. I have checked that the BIOS settings have not changed (vt-x is enabled).

Any other hints are welcome.

This is the solution (Tested in Windows 10 19036 OS Build 18362.592 / VirtualBox 6.1.4 r136177)
1. Turn Window features Off
• Hyper -V
• Virtual Machine Platform
• Windows Defender Application Guard
• Windows Hypervisor Plarform
• Windows SandBox /
2. Disable Fast Boot
• Control Panel > Power Options > Choose what the power buttons do > ShutDown Settings > Turn off fast startup
3. Disable Device Guard / Credential Guard:
• Start > Run > gpedit.msc The Local group Policy Editor opens.
• Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.
• Select Disabled.
4. Delete the related EFI variables by launching a command prompt as Administrator and run these commands:
// Ensure that X is an unused drive letter, else change to another drive letter.
• mountvol X: /s
• copy %WINDIR%System32SecConfig.efi X:EFIMicrosoftBootSecConfig.efi /Y
• bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d “DebugTool” /application osloader
• bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path “EFIMicrosoftBootSecConfig.efi”
• bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
• bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
• bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
• mountvol X: /d

5. Restart.
6. Accept the prompt on the boot screen to disable Device Guard or Credential Guard.

Now VirtualBox will work

Super!!! thanks for the post. After a Windows10 update I was experiencing this issue.

I believe the trigger to get my VMs operating again was this:
Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.
• Select Disabled.

This topic was already marked as solved (in 2017!), and recent posts simply repeat what’s already in the FAQ (see posts 2 and 3).

Locking this.

I had the same problem. Tried the turning the HyperV off and rebooting but that did not work. My BIOS had Virtural turned on too. What fixed it for me was to go into BIOS, turn the virtual off then reboot it. Then reboot again and go back into the BIOS and turn virtual back on.

I got the same error, and simply enabling BIOS VT-x was enabled, but simply enabling again BIOS VT-x got rid of the error. Uninstall virtual box, delete Virtual box files in program files, and in ProgramData

In windows 10

Settings-> Update & security->Recovery -> Advanced startup ->Restart now

Next after restarting choose
Troubleshoot ->Advanced options->UEFI Firmware Settings ->click Restart

Then select F10 ->System configurations->Virtualization Technology select enabled and pressed enter
Exit Saving changes->Select yes

Then reinstall virtual box, hope it helps

answered May 7, 2020 at 16:50

I followed these steps here (like you did) and nothing worked.

Eventually, I disabled VT-d in my BIOS, and suddenly I was able to run VirtualBox machines. I have no idea why it worked, just try it if you have nothing else to do.

answered Aug 11, 2020 at 17:44

answered Nov 7, 2022 at 22:13

This happend with me when windows 10 updated to windows 2004

So to fix this Make sure you disable the feature HyperV of windows feature

start -> Windows Features -> Windows Hypervisor Platform -> uncheck if checked.

restart your PC.

then try vagrant up or start the virtualbox machine again

answered Jun 13, 2020 at 22:41

Recently I started having an issue with VT-x on my Windows 10 running on HP EliteBook. I was using Oracle VirtualBox to run some VMs on it before and VT-x was enabled in BIOS and was working fine.

I started getting VT-x is not available error every time I was trying to start any of my VMs. That started happening after I installed Docker on my machine, so I tried uninstalling it and rebooting. Didn’t help.

I checked BIOS settings and it says VT-x is enabled but checking with Intel(R) Processor Identification Utility shows that VT-x is not supported and Oracle VirtualBox also doesn’t see it.

There were no hardware changes and the only software change was installing/uninstalling Docker.

How can this issue be fixed?

asked Dec 6, 2016 at 11:01

I was tripped up by the fact there was 2 options in the Windows Features dialog to turn off:

• Hyper-V
• Windows Hypervisor Platform

I had attempted an upgrade to VirtualBox 6, and some performance issues, and downgraded to VirtualBox 5 and had these issues. Hopefully this helps someone else out.

answered Mar 14, 2019 at 12:49

Virtualbox was working ok. I updated Avast anti-virus today, 29th June 2017. Virtualbox then gave the VT-x error. In Avast Settings, go to Troubleshooting and enable «Use nested virtualiszation where available» and then reboot your PC. This worked for me with no other changes required.

Hyper-V and VirtualBox can co-exist on Windows 10. The config step is documented in How to use VirtualBox and Hyper-V together on Windows 10. The gist is

1. Enable Hyper-V and Windows hypervisor platforms
   
2. Set Paravirtualization Interface of a guest VM to Hyper-V
   

answered Nov 6, 2020 at 14:32

I came to this post thinking that VT-x wasn’t enabled, because Hyper-V was telling me that «The virtual machine is using processor-specific features not supported on physical computer». This started after installing Windows updates and restarting the server. In reality, VT-x was actually enabled.

The fix was to delete saved state for all VMs, effectively a power-off.

It looks like the reason for this may have been a CPU microcode update but it’s hard to be sure, it’s just something that came up in a number of search results.

answered Mar 14, 2019 at 0:52

The only change that worked for me, after trying many tips related here, was:

On some Windows hosts with an EFI BIOS, DeviceGuard or CredentialGuard
may be active by default, and interferes with OS level virtualization
apps in the same way that Hyper-v does. These features need to be
disabled. On Pro versions of Windows you can do this using gpedit.msc
(set Local Computer Policy > Computer Configuration > Administrative
Templates > System > Device Guard > Turn on Virtualization Based
Security to Disabled.

answered Feb 13, 2020 at 19:13

answered Oct 4, 2021 at 12:46

answered Jun 25, 2020 at 2:31