How to Repair VirtualBox “Raw-Mode is Unavailable Courtesy of Hyper-V” Error Message

Updated December 2023: Stop these error messages and fix common problems with this tool. Get it now at this link

  1. Download and install the software.
  2. It will scan your computer for problems.
  3. The tool will then fix the issues that were found.

Many users are unable to start the VM because they get the following error message when they try to do so:

Failed to open a session for the virtual machine.
Raw mode is not available through Hyper-V.

In this article, we will fix this error with some simple solutions.

What causes the “Raw-Mode is Unavailable Courtesy of Hyper-V” error message in VirtualBox?

The reason for the “Raw-mode is unavailable thanks to Hyper-V” error message is the fact that Hyper-V is enabled on your machine. This proprietary virtualization technology from Microsoft allows you to create virtual machines on x86 and x64 systems running their own version of Windows.

One possible reason for this problem is that hardware virtualization is disabled in your BIOS or UEFI settings. Keep in mind that virtualization is enabled by default on all new hardware these days; older configurations of computers may not have this option enabled by default.

A scenario that can cause this problem is when the HyperVisorLaunchType service is set to AUTO. This will force your system to check for applications that use VT-x before every virtual machine startup.

How to solve the “Raw mode is not available due to Hyper-V” message in VirtualBox?

Updated: December 2023

This tool is highly recommended to help you fix your error. Plus, this tool offers protection against file loss, malware, and hardware failures, and optimizes your device for maximum performance. If you already have a problem with your computer, this software can help you fix it and prevent other problems from recurring:

  • Step 1 : Install the PC Repair and Optimizer Tool. (Windows 10, 8, 7, XP, Vista).
  • Step 2 : Click Start Scan to determine what problems you are experiencing with your computer.
  • Step 3 : Click Repair Allto resolve all problems.


Disabling the hypervisor

  1. Open a command prompt or PowerShell as an administrator.
  2. Now run the command bcdedit.
  3. A list of data is displayed. Look for hypervisorlaunchtype.
  4. If hypervisorlaunchtype is set to Auto, disable it by running the following command:
    bcdedit /set hypervisorlaunchtype off
  5. Reboot the computer and see if the problem is resolved.

Make sure virtualization is turned on in the BIOS

  1. Reboot the computer and enter the BIOS.
  2. Now find the Virtualization option and turn it on.
  3. Save your changes and reboot your computer.

Every version of the BIOS is different, so consult the manual to find out how to properly locate and enable virtualization in the BIOS.

Make sure Hyper-V is turned off

  1. Press Windows + R and type optionalfeatures.exe. Press Enter or press OK.
  2. The Windows Features window will appear.
  3. Find Hyper-V in the list and disable it. Click OK to save your changes.
  4. Restart your computer to apply the changes.

APPROVED: To fix Windows errors, click here.

Frequently Asked Questions

  1. Disable the Hyper-V management tools.
  2. Disable Hyper-V validation.
  3. Disable Device Guard / Credential Guard.
  4. Disable kernel isolation in Windows Defender.
  5. Enable virtualization in the BIOS or UEFI.

  1. Make sure that hardware virtualization support is enabled in your BIOS settings.
  2. Save your BIOS settings and boot your computer as normal.
  3. Click the search icon (magnifying glass) on the taskbar.
  4. Type "Enable or disable Windows features" and select that option.
  5. Select Hyper-V and turn it on.

  1. Make sure that virtualization is enabled in the BIOS.
  2. Update your BIOS.
  3. Update the drivers to the latest version.
  4. Reinstall the HyperV feature.
  5. Remove any problematic updates.
  6. Use the bcdedit command.
  7. Use the DISM command.
  8. Check if your processor supports virtualization.

Affected applications include VMware Workstation and VirtualBox. These applications may fail to start virtual machines or go into a slower emulated mode. These symptoms occur when the Hyper-V hypervisor is running.