Solved – VT-x Is Not Available (VERR_VMX_NO_VMX) [MiniTool News]
By Tina | Follow | Last Updated January 22, 2020
Summary :
What is the error vt-x is not available (verr_vmx_no_vmx)? What causes the error that vt-x is not available? How to fix the error that verr_vmx_no_vmx vt x is not available? This post from MiniTool will show you the solutions.
What Causes VT-x Is Not Available (VERR_VMX-NO-VMX)?
When you are trying to open any virtual machines using VirtualBox or other similar software, you may encounter the error that vt-x is not available (verr_vmx_no_vmx). In general, the error that vt-x is not available may be caused by various reasons. In the following part, we will list some.
- Vt-x is not enabled in the BIOS settings.
- The machine’s CPU does not support vt-x.
- Hyper-V virtualization is enabled in Windows.
- Core location is enabled.
So, in the following section, we will show you how to fix the error that vt-x is not available.
How to Fix VT-x Is Not Available (VERR_VMX_NO_VMX)?
In this section, we will walk you through how to solve the error that verr_vmx_no_vmx vt x is not available.
Way 1. Disable Hyper-V Virtualization
In order to fix the error that vt-x is not available (verr_vmx_no_vmx), you can choose to disable Hyper-V virtualization.
Now, here is the tutorial.
- Type Command Prompt in the search box of Windows and choose the best-matched one.
- Then right-click it to choose Run as administrator.
- In the pop-up window, type the command exe /Online /Disable-Feature:Microsoft-Hyper-V and hit Enter to continue.
When the process is finished, close the command line window and reboot your computer. Then open the virtual machine again to check whether the error that vt-x is not available (verr_vmx_no_vmx) is solved.
If this solution is not effective, try other solutions.
Way 2. Disable Core Isolation from Windows Defender
In order to fix the error that verr_vmx_no vmx vt x is not available, you can also choose to disable core isolation from Windows Defender.
Now, here is the tutorial.
- Press Windows key and I key together to open Settings.
- In the pop-up window, choose Update & Security to continue.
- Then choose Open Windows Security to continue.
- On the right panel, choose Device Security to continue.
- In the pop-up window, click Core isolation details.
- Then change toggle under Memory integrity to Off.
After that, reboot your computer and check the error that vt-x is not available is solved.
Way 3. Enable VT-X from BIOS Settings
If the Virtualization Technology is disabled from the BIOS settings, you can also get the error that vt-x is not available (verr_vmx_no_vmx). Thus, you can choose to enable vt-x from BIOS settings.
Now, here is the tutorial.
- Boot your computer. Once the Windows logo appears, press the setup continuously to enter BIOS.
- After entering the BIOS, navigate to the Security tab and scroll down to System Security.
- Then check whether Virtualization Technology or VTx/VTd is listed here and whether it is enabled.
- If no, change its status to enabled.
After all steps are finished, reboot your computer to check whether the error that vt-x is not available (verr_vmx_no_vmx) is solved.
Final Words
To sum up, this post has introduced 3 ways to fix the error that vt-x is not available. If you have encountered the same error, try these ways. If you have any better solution to fix the error that verr_vmx_no_vmx vt x is not available, you can share it in the comment zone.
virtualbox.org
End user forums for VirtualBox
Error after upgrade:VT-x is not available. (VERR_VMX_NO_VMX)
Error after upgrade:VT-x is not available. (VERR_VMX_NO_VMX)
by yellowduck » 30. Nov 2013, 14:48
VB 4.3.4 on Win7 64bit
I installed the 4.3.4 update this morning and now get an error when opening any guests. I have been running VB for many years on the same computer and the same guests, no problems until I installed the update.
Guests are WinXP, Win7, Win2008. Guest additions are installed on the guests.
Error message:
Failed to open a session for the virtual machine Windows XP.
VT-x is not available. (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole
Attached is the VM log file.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by noteirak » 30. Nov 2013, 19:20
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by yellowduck » 30. Nov 2013, 19:35
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by yellowduck » 30. Nov 2013, 19:36
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by mpack » 30. Nov 2013, 19:47
The log says that you have VT-x enabled in this VM recipe, hence the VM can’t run without VT-x and it gives an error saying so. AFAIK this has not changed recently.
64bit guests require VT-x. I suspect you selected the «XP-64bit» template when you installed the OS, or you tried that «longmode» command line tweak that’s been discussed recently.
Make sure you don’t have a 64bit template selected in |General|Basic , and turn off VT-x in |System|Acceleration .
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by Perryg » 30. Nov 2013, 20:07
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by yellowduck » 30. Nov 2013, 23:22
Thank you perryg, setting longmode off did the trick.
These VMs were setup many years ago on a 32 bit computer. I guess it’s just old stuff catching up with new software and somewhere something was forgotten.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by Perryg » 1. Dec 2013, 01:33
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by sergiomb » 3. Dec 2013, 19:13
Code: Select all Expand viewCollapse view VBoxManage modifyvm —longmode off
Also worked here , my Box is Linux , and yes, I already know, this CPU doesn’t have VT-x , so it is a 64-bits machine, but all vms just work in 32 bits . this issue happens on all vms: Linux , WindowsXP and Windows 7.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by jakeochs » 3. Dec 2013, 21:53
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by Perryg » 3. Dec 2013, 21:55
From the hosts terminal/command window type VBoxManage showvminfo —details and post here. Replace with the actual name of the VM. Use » » if the name has a space in it.
Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by 21grams » 4. Dec 2013, 07:48
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by OldBloke » 4. Dec 2013, 08:13
I am having a similar problem since the last upgrade. I’m running a Win8.1 host on an old 64bit processor that doesn’t have virtualization.
I tried the modifyvm workaround but got the following error message:
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) — Server execu
tion failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or
failed to start.
showvminfo also produces a similar error.
Oddly, I was able to start a machine using a vhd originally created in VMWare. None of my VBox machines now work, they all give the VT-x error.
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by alsov » 4. Dec 2013, 08:30
Try to change setting HardwareVirtEx in your virtual machine config file ( .vbox).
It’s a CPU section/ Looks like this
Re: Error after upgrade:VT-x is not available. (VERR_VMX_NO_
by OldBloke » 4. Dec 2013, 09:11
Do I only need to set HardwareVirtEx to false or should I set all the VirtEx* settings to false?
Edit: It helps to experiment. I only needed to change the first one, HardwareVirtEx to false.
virtualbox.org
End user forums for VirtualBox
[Solved] VT-x is not available, no solutions have worked
[Solved] VT-x is not available, no solutions have worked
by CowsayRoot » 30. Dec 2018, 18:43
I recently received a new laptop and have been trying to get some VMs up and running on it. I’ve been through Google and the forums trying to find the solution, and have seen multiple suggestions, but nothing has worked for me. Each time I try to start a VM, I get the following error:
Code: Select all Expand viewCollapse view Failed to open a session for the virtual machine Kali-Linux-2018.4-vbox-amd64.
VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole
Now my searches have told me that this is most commonly due to either virtualization not being enabled in BIOS, or Hyper-V running and not allowing VirtualBox access to VMX.
I have checked my machine’s BIOS and confirmed that virtualization is enabled.
I have also checked my CPU (Intel Core i7-8550U) and ensured that it supports VT-x.
I have tried many things with Hyper-V including the following:
- Removing Hyper-V through Enable/Disable Features and conducting complete power-cycle
- Running the following command in an admin powershell (per
- ):
Code: Select allExpand viewCollapse view bcdedit /set hypervisorlaunchtype off - Running the following command in an admin powershell (per
- ):
Code: Select allExpand viewCollapse view dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
Versioning and other specs follow:
VirtualBox Version: 6.0.0
(I removed 6.0.0 and tried 5.2.22 and got the same error)
Host: Windows 10 Pro x64 v 1803
Guest: Kali Linux x64 v 2018.4 (logs provided)
Guest: Kali Linux x86 v 2018.4
Host Memory: 16GB
Guest Memory 2GB
At this point I’m at a loss, if anyone can provide me any guidance, I would appreciate it! And if this has already been solved somewhere else, and I missed it, I apologize for the redundant post.
Re: VT-x is not available, no solutions have worked
by socratis » 30. Dec 2018, 22:36
You don’t have a hardening problem, the availability of VT-x is not related to hardening. Something is using your VT-x. And it’s not just the things that you mentioned. There’s Device Guard for example.
After making 110% sure that Hyper-V is disabled in the Windows Features, you might want to make sure that Fast Boot is disabled and do a cold boot (i.e. shut down the host for a minute or two). You also must make sure that nothing else is using Hyper-V, things like antivirus, debuggers, emulators, etc. Check out the article «I have a 64bit host, but can’t install 64bit guests» to get some ideas.
Also, Microsoft article on Credential Guard: Manage Windows Defender Credential Guard.
Re: VT-x is not available, no solutions have worked
by CowsayRoot » 31. Dec 2018, 03:07
Re: VT-x is not available, no solutions have worked
by CowsayRoot » 31. Dec 2018, 04:27
Re: VT-x is not available, no solutions have worked
by socratis » 31. Dec 2018, 13:11
It’s either one of the installed remaining software, or a Win feature that you may have missed.
The problem is that there’s no mechanism (yet) to tell which application/service is using VT-x, you have to try it by trial and error. That’s also the reason that we cant offer you more than generic advice. You got to find what’s «wrong» with your setup.
Re: VT-x is not available, no solutions have worked
by CowsayRoot » 31. Dec 2018, 22:25
Re: VT-x is not available, no solutions have worked
by SurgeonX1 » 31. Dec 2018, 23:10
I have exactly the same problem on a windows 8.1 machine.
But only after updating virtualbox.
Before everything works fine !
No change on the PC !
Can sb explaine what is vt -x ?? And what is ver vmx no vmx .
Why does this happen only after update of virtualbox ??
Most faults i experienced were after simple update !
Re: VT-x is not available, no solutions have worked
by CowsayRoot » 1. Jan 2019, 00:51
Re: [Solved] VT-x is not available, no solutions have worked
by socratis » 1. Jan 2019, 01:19
Re: [Solved] VT-x is not available, no solutions have worked
by sasos90 » 11. Mar 2019, 23:27
Re: [Solved] VT-x is not available, no solutions have worked
by BillG » 12. Mar 2019, 00:20
No. If Hyper-V is enabled, VT-x is locked to the Windows hypervisor.
In version 6 of VirtualBox there is an option to run a vm (slowly) even if Hyper-V is enabled, but it is not operational yet.
Re: [Solved] VT-x is not available, no solutions have worked
by sasos90 » 27. Apr 2019, 21:45
Re: [Solved] VT-x is not available, no solutions have worked
by socratis » 28. Apr 2019, 22:54
When Microsoft stops being selfish! Complain to them!
The trick with VT-x is that it has to be shared, since it’s «only one» available slot for its use. For example, VMware and VirtualBox (and until recently, KVM) do not use VT-x at the same time, but rather take turns. To put it simply, every program that uses VT-x should do this:
- VT-x lock
- Execute privileged VT-x code
- VT-x unlock
This way other processes can use VT-x in turns.
On the other hand, Hyper-V permanently takes over VT-x and doesn’t let anyone else use it. If a program uses VT-x from the moment it is loaded, and doesn’t let go till the moment it dies, you have a problem. So, please complain to Microsoft about that.
Re: [Solved] VT-x is not available, no solutions have worked
by swakop_toe » 4. Jun 2019, 10:56
Re: [Solved] VT-x is not available, no solutions have worked
by andyp73 » 4. Jun 2019, 11:09
It has been on the list of known culprits for a while which has appeared on many threads related to this subject in the list that looks like: