virtualbox Raw-mode is unavailable courtesy of Hyper-V windows 10

Question

issues:

Failed to open a session for the virtual machine ubuntu.

Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Resul         


        

Answer 1

In my case, was the Docker that cause problems:

Answer 2

1) Run below command in powershell with admin mode:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

2) run below command in command prompt with admin mode:

bcdedit /set hypervisorlaunchtype off 

3) disabled Hyper-V: Control Panel\Programs\Programs and Features\

4) VMBox memory made it to: 3155 MB (VMbox->settings->system)

VM box Acceleration is deactivated. How do activate this? and fix above error?

Restart your system.

Answer 3

To check the status of Hyper-v in Windows 10,

right click <"start"> → Run → OptionalFeatures.exe, → look for the "Hyper-V" option.

The box should be empty, not checked or shaded.

Make sure to fully power down and reboot the host after changing the Hyper-v setting.

PS

Docker known for activating this "Hyper-V" without asking for user opinion and then Oracle VirtualBox does not want to work.

Answer 4

As in the docs, if you are on windows you can use hyperv drivers.

Docker for Windows - You can use docker-machine create with the hyperv driver to create additional local machines.

Answer 5

For me the combination of the following three was the solution:

1. control panel > turn windows features on or offf > Hyper-V : deselect

2. admin cmd > bcdedit > hypervisorlaunchtype:Auto disabling: bcdedit /set hypervisorlaunchtype off

3. gpedit.msc > 'Computer configuration > Administrative Template > Device Guard' > Turn On Virtualization Based Security : Change from 'Not configured' to 'Disabled'

REBOOT

---

note: after the reboot the VirtualBox worked, but Docker Desktop's VirtualBox started complaining about missing Hyper-V !

It seems that this might have been the root of all my evil... Extra info: https://forums.docker.com/t/running-docker-and-virtualbox-on-the-same-machine/23578/13

Answer 6

i had same problem guys

virtual box was running smoothly on my windows machine but when new update came virtual started giving me this error and believe me guys just a little S%$& thing fixed it

in my case this problem fixed just by installing windows extension pack that's it