Raw-Mode is Unavailable Courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

When launching a virtual machine in VirtualBox, the error “Raw-mode is unavailable courtesy of Hyper-V (VERR SUPDRV NO RAW MODE HYPER V ROOT)” appears. Despite the fact that Hyper-V technology is disabled on some users’ computers, this error still occurs for them.

Your first port of call in trying to resolve this issue would be to make sure Hyper-V is not turned on under Windows Features. If it’s already disabled, other potential offenders include a hypervisor check that is enabled, Device Guard (Credential Guard) that is enabled, or any interference made possible by Core Isolation, a security feature of Windows Defender.

On older machine configurations, however, you might also encounter this error because hardware virtualization is turned off at a BIOS or UEFI level.

Solution 1: Disable the Hyper-V Management Tools First

The fact that Hyper-V is enabled on your computer is the main factor in the “Raw-mode is unavailable courtesy of Hyper-V” error. On x86 and x64 systems running a native Windows version, virtual machines can be created using this exclusive Microsoft virtualization technology.

However, none of the third-party alternatives, such as VMware or VirtualBox, use it for stability reasons. Furthermore, they expressly object to working when this technology is activated. Windows 10 is now set up to favour Hyper-V over a competing virtualization technology, though.

As you might expect, this could result in a variety of problems, including the VERR SUPDRV NO RAW MODE HYPER V ROOT error code. To correct it, you must turn off Hyper-V and allow a third-party replacement to take control.

You have two options when it comes to moving forward with this. Either directly from the terminal or from the Programs and Features GUI menu are both options. Feel free to use whichever strategy you like:

Using the GUI, Disable Hyper-V

1. A Run dialogue box will appear when you press the Windows key + R. Then, enter “appwiz.cpl” to launch the Programs and Features menu.
2. After entering the Programs and Features menu, select Turn Windows features on or off from the left-hand pane using the menu on the right.
3. Expand the Hyper-V folder from within the Windows Features menu. Before clicking OK, make sure to uncheck the box next to Hyper-V Management Tools and Hyper-V Platform.
4. After the procedure is finished, restart your computer and check to see if the problem has been fixed.

Using the CMD terminal, Disable Hyper-V

1. A Run dialogue box will appear when you press the Windows key + R. To open an advanced Command Prompt, type “cmd” into the text box and press Ctrl + Shift + Enter. Once the User Account Control (UAC) window appears, click Yes to grant administrative rights.
2. To disable the Hyper-V feature, enter the following command or paste it into the elevated CMD terminal after you’ve succeeded in doing so:
3. After the command has been successfully executed, shut down CMD and restart your computer.
4. Repeat the action that resulted in the Raw-mode is unavailable courtesy of Hyper-V error at the next startup to see if the issue has been fixed.

If this procedure didn’t enable you to resolve the issue, see the steps below for an alternative approach.

Solution 2: Select Disable Hypervisor

It turns out that even with Hyper-V disabled, you might still experience this problem. A common scenario where this problem may arise is when the HyperVisorLaunchType service is configured to AUTO. Your system will eventually be forced to check for VT-x-using programmes before launching each virtual machine as a result of this.

By using the Bcdedit utility to check the status of HyperVisorLaunchType and disable it in case it is set to Automatic, several affected users have been able to resolve this issue.

A quick tutorial for doing this on any Windows computer is provided below:

1. A Run dialogue box will appear when you press the Windows key + R. To open an elevated CMD terminal, type “cmd” into the text box and then press Ctrl + Shift + Enter.
2. To check the status of HyperVisor, type the following command into the elevated CMD terminal and press Enter.
3. When the results are available, scroll down to the hypervisorlaunchtype section and check to see if the status is Auto.
4. If the hypervisorlaunchtype status is Auto, type the following command or paste it, then press Enter to change the status to Disabled:

5 Close the elevated CMD terminal once the command has been successfully executed, then restart the host computer.

6. Launch a VirtualBox virtual machine at the next startup to check if the issue has been fixed.

Move on to the next potential solution below if the problem is still present.

Solution 3: Turn off Credential Guard and Device Guard

Other impacted users were able to resolve the Raw-mode is unavailable courtesy of Hyper-V error by disabling Device Guard using the Gpedit (Local Group Policy Editor) (also known as Credential Guard).

It turns out that this mix of security-focused enterprise software and services may end up clashing with some VirtualBox VM features. If Device Guard is the cause of the error VERR SUPDRV NO RAW MODE HYPER V ROOT, you can quickly fix the problem by turning it off in the Local Group Policy Editor.

However, keep in mind that not every Windows version comes with the Gpedit utilities. It won’t be present in Windows 10 Home and a few other related sub-versions. But you can follow some steps to install gpedit.msc on Windows 10.

1. A Run dialogue box will appear when you press the Windows key + R. The Local Group Policy Editor will then open after you type “gpedit.msc” and press Enter.
2. After entering the Local Group Policy Editor, use the left-side menu to find the following place:
3. Once you’ve managed to find the right place, click twice on Turn on Virtualization Based Security in the Gpedit utility’s right-hand section.
4. Once you’re in the window that asks you to enable virtualization-based security, all you need to do is set the status to “Disabled” and click “Apply” to save the modifications.
5. Once you’ve accomplished this, DON’T restart your computer just yet. Instead, press Windows key + R to open an elevated command prompt, type “cmd,” and then press Ctrl + Shift + Enter.
6. Paste the following commands into the CMD window and hit Enter after each one to remove any associated EFI variables that could still be causing this issue:
7. After each command has been successfully executed, restart the host computer to check if the issue has been fixed.

Continue to the next method below if you’re still getting the “Raw-mode is unavailable courtesy of Hyper-V” error.

Solution 4: In Windows Defender, Disable Core Isolation

It turns out that this problem can also be caused by a security feature from the default AV. Core Isolation is a feature of Windows Defender in Windows 10 that essentially adds another layer of virtualization-based security in order to defend against more advanced attacks.

However, it is well known that this security measure interferes with virtual machines’ smooth operation, particularly those supported by third-party alternatives.

A number of affected users who were also getting the “Raw-mode is unavailable courtesy of Hyper-V” error have reported that they were finally able to resolve the problem by enforcing some modifications that allowed them to turn off Core isolation from the Windows Security settings menu.

Here is a quick tutorial on how to disable Core Isolation in Windows Defender’s settings menu:

1. A Run dialogue box will appear when you press the Windows key + R. The Windows Security tab of the Settings app will then open after you type “ms-settings:windowsdefender” in the text box and press Enter.
2. Once you’re in the Windows Security tab, click on Device Security in the Protection areas section on the right.
3. After that, click on Core isolation details after navigating to the bottom of the list of alternatives (under Core isolation).
4. Ensure that the toggle for Memory integrity is turned off inside the Core isolation menu.
5. Restart your computer after the modification has taken effect to see if the issue has been resolved.

Here is a quick guide on using Registry Editor to accomplish the same goal in the event that the toggle connected to Core Isolation is greyed out or you receive an error message when you attempt to set it to OFF:

1. To bring up the Run dialogue box, press Windows key + R. Then, to launch Registry Editor, type “regedit” into the text box and press Enter. When the UAC (User Account Prompt) appears, select Yes to grant administrative rights.
2. In Registry Editor, navigate to the following location using the left-hand section:
3. Once you’ve found the right spot, move to the right side of the screen and double-click the Enabled key.
4. When you’ve successfully opened the Enabled Value, leave the base at Hexadecimal and change the Value data to 0.
5. After saving the change by clicking Ok, exit Registry Editor and restart your computer to see the results.
6. Repeat the action that brought on the VERR SUPDRV NO RAW MODE HYPER V ROOT error code at the next machine startup and check to see if the issue is still present.

Move on to the following potential solution below if the problem is still not fixed.

Solution 5: Turn on Virtualization in the UEFI or BIOS

If hardware virtualization is disabled in the BIOS or UEFI settings, that could also be a possible cause of this issue. Remember that modern hardware has virtualization turned on by default; this feature may not be turned on by default in older computer configurations.

You might need to manually enable hardware virtualization from your BIOS or UEFI settings if your PC has an older configuration. A number of affected users have confirmed that doing this completely resolved the problem.

A quick tutorial on how to enable virtualization in your BIOS or UEFI settings is provided below:

1. If your computer is BIOS-powered, turn it on and begin repeatedly pressing the Setup key as soon as you see the startup screen. The Setup key in the majority of configurations is either the Del key or one of the F keys (F2, F4, F6, F8).
2. As soon as you are in your BIOS or UEFI settings, begin navigating the menus to find the virtualization technology equivalent for your motherboard (Intel VT-x, Intel Virtualization Technology, AMD-V, Vanderpool, etc.)
3. As soon as you find it, make sure to set it to Enabled.
4. Once you’ve managed to turn on virtualization, save your changes to the UEFI or BIOS settings and restart your computer to make it possible for it to boot normally.
5. Repeat the action that resulted in the “Raw-mode is unavailable courtesy of Hyper-V” error during the subsequent startup sequence and check to see if the issue has been resolved.