Page 1 of 1
[Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 14. Sep 2017, 15:52
by davide.cossano
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.
Re: VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 14. Sep 2017, 16:35
by mpack
Disable Hyper-v, per all the previous discussions of this problem.
Re: VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 14. Sep 2017, 17:16
by 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.
Re: VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 14. Sep 2017, 17:39
by mpack
Thanks for reporting back.
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 1. Dec 2017, 23:57
by RBStorms
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!
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 23. Jan 2018, 00:43
by georgn
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
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.
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 23. Jan 2018, 06:36
by BillG
You can expect to see odd things happen when you run pre-release versions of the OS on the host.
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 23. Jan 2018, 10:31
by socratis
@georgn
BillG is absolutely correct, there is a special forum for discussions like these:
Windows pre-releases. Just so that you know, you're not alone. A couple more users have
reported the exact same issue. If you want you could continue the conversation in that thread.
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 23. Jan 2018, 17:13
by georgn
Awesome! Thanks! Heading over to the other forum.
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 21. Feb 2020, 21:04
by Vic.CRI
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%\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,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
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 28. Feb 2020, 16:42
by Joeyjoe
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.
Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update
Posted: 28. Feb 2020, 18:16
by mpack
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.