Troubleshooting VT-x Is Not Available (VERR_VMX_NO_VMX)

Troubleshooting VT-x Is Not Available (VERR_VMX_NO_VMX)

This guide provides instructions to resolve the following error in VirtualBox: “Failed to open session for virtual machine (VM MachineName). VT-x not available (VERR_VMX_NO_VMX) with result code: E_FAIL (0x80004005).

The VirtualBox “VT-x not available” error occurs on a computer running Windows 10 Pro with a Gigabyte Z370 HD3P motherboard and an Intel Core i7-8700 processor that supports IntelĀ® Virtualization Technology (VT-x). In addition to the “VT-x not available” error message in VirtualBox, the SecurAble tool also reports that hardware virtualization is not available on the system.

What causes VT-x (VERR_VMX_NO_VMX) to be unavailable?

What causes VT-x (VERR_VMX_NO_VMX) to be unavailable?

When you try to open a virtual machine using VirtualBox or similar software, you may encounter the following error: vt-x not available (verr_vmx_no_vmx). In general, the error that vt-x is unavailable can be caused by various reasons. In the next section, we will list some of them.

  • Vt-x is not enabled in the BIOS settings.
  • The computer’s processor does not support vt-x.
  • Hyper-V virtualization is enabled in Windows.
  • Central storage is enabled.

In the next section, we show you how to troubleshoot vt-x is not available.

How to troubleshoot VT-x is not available (VERR_VMX_NO_VMX)

How to troubleshoot VT-x is not available (VERR_VMX_NO_VMX)

Enable VT-x in your BIOS

  1. Reboot your computer
  2. Boot into BIOS (press Del, F2, Esc depending on your motherboard)
  3. Find the virtualization option and turn it on. It may look different on your system.

Disable Hyper-V virtualization

Since this is one of the most common scenarios because many people have reported having this problem well after the release of the Fall Creators Update of Windows 10. First of all, let’s make sure that Hyper-V virtualization does not interfere with VT-x.

When Hyper-V virtualization is enabled, the VT-x virtualization equivalent is automatically disabled. The update may have interrupted Hyper-V functionality. Therefore, we will manually disable Hyper-V using the commands.

You may run into this problem after installing an application such as Docker. Keep in mind that in most cases, even if you uninstall the application that enabled Hyper-V, the technology will remain enabled, preventing VT-x from running.

Let’s test this scenario by disabling Microsoft Hyper-V. There are several ways to disable Hyper-V virtualization, but we want to keep it as simple as possible. Here’s how to disable Microsoft Hyper V from the extended command line:

  1. Press the Windows + R key to open the “Run” dialog box. Then type “cmd” and press Ctrl + Shift + Enter to open the extended command prompt. When prompted in the UAC (User Account Control) window, click Yes.
  2. In the extended prompt, insert the following commands to disable Microsoft Hyper V and press Enter:
    bcdedit /set hypervisorlaunchtype Off
    bcdedit /set vm No
    dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
  3. If the commands are correct, close the extended command line and restart your computer.
  4. The next time you start up, open the Virtualbox machine again and see if you get the same error message.

If you still see the VT-x is not available (verr_vmx_no_vmx) error when trying to start the virtual machine, go to the following method.

Disable Windows Defender Core Isolation

Core Isolation is a Windows Defender security option that is known to conflict with VT-X. If you receive a VT-x unavailable error (verr_vmx_no_vmx) and you are using Windows Defender as your default security feature, we recommend that you do the necessary research to determine if Core Isolation is enabled.

Perform the following steps:

  1. Go to the Start icon in the bottom left corner and look for Windows Defender. Then click on Windows Defender Security Center to open the built-in security option.
  2. Once in the Windows Defender Security Center, click Device Security on the left-hand menu.
  3. In the Device Security menu, click on Core Isolation Details (under Core Isolation).
  4. In the Core Isolation menu, make sure that the Memory Integrity switch is set to OFF.
  5. After disabling the setting, restart the computer and verify that the problem is corrected on the next startup.

Enable nested virtualization in the Avast settings menu (if applicable)

If you use Avast, note that an update to the app released in June 2017 adds an automatic feature that prevents VT-X from running on your system if certain conditions are met.

Fortunately, there is a way to solve this problem without uninstalling the third-party security client.

Many users have reported that they can solve this problem by going to Avast Settings -> Troubleshooting and checking the Use nested virtualization where possible and Enable hardware-assisted virtualization checkboxes.

Frequently Asked Questions

  1. Start your computer.
  2. After entering the BIOS, go to the Security tab and scroll down to System Security.
  3. Then check to see if virtualization or VTx/VTd technology is listed here and if it is enabled.
  4. If not, change the status to enabled.

Press the F2 key when starting the BIOS setup. Press the right arrow key to go to the System Configuration tab, Select Virtualization Technology, and press Enter. Select Enabled and press Enter. Press F10, select Yes, and press Enter to save your changes and restart Windows.

  1. Reboot your computer.
  2. Once the computer boots with a black screen, press Delete, Esc, F1, F2, or F4.
  3. In the BIOS settings, find the configuration items that relate to the processor.
  4. Turn on virtualization; the setting may be VT-x, AMD-V, SVM, or Vanderpool.
  5. Save your changes and reboot.

  1. Reboot your computer.
  2. Boot into BIOS (press Del, F2, Esc. Depending on your motherboard).
  3. Find the virtualization option and turn it on. It may look different on your system.