virtualbox Raw-mode is unavailable courtesy of Hyp

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).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

1) I have 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?

OS: windows 10.

rebooted Del laptop many times.

Answer 1

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 2

Run CMD in administrator mode 1.bcdedit 2.bcdedit /set hypervisorlaunchtype off 3.Reboot system

This worked for me!!

Answer 3

You have to disable Memory Integrity.

Go to Device Security, then Core Isolation, disable Memory Integrity and reboot.

It seems that Memory Integrity virtualizes some processes (in this case, VMware) and we get that error.

---

You can also disable Memory Integrity from Registry Editor if your control panel was saying 'This is managed by your administrator'.

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity

Double click on Enabled and change its value from 1 to 0 to disable it.

---

Helpful source: https://forums.virtualbox.org/viewtopic.php?t=86977#p420584

Answer 4

After Windows 10 update in July of 2018 I suddenly experienced this issue with Virtual Box losing 64-Bit OS options resulting in the error.

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

Existing Laravel Homestead Boxes rendered un-bootable as a result event though HYPER-V is Disabled / Not Installed...

The FIX! (That worked for me) Drum Roll....

Install Hyper-V... Reboot, Uninstall it again... Reboot... The end

Answer 5

You need to disable Hypervisior to check new application that use VT-x before ir launch.

So, follow the next steps:

1) open command prompt as Administrator

2) run bcdedit to check hypervisor status:

bcdedit

3) check hypervisor launch type:

4) if is set to auto then disable it:

bcdedit /set hypervisorlaunchtype off

5) reboot host machine and launch VirtualBox again

I hope this helps.

Answer 6

Disabling Device Guard or Credential Guard fixed for me:

• click Start > Run, type gpedit.msc, and click Ok. The Local Group Policy Editor opens. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security. Select Disabled.
• Go to Control Panel > Uninstall a Program > Turn Windows features on or off to turn off Hyper-V.

Select. Do not restart.

Delete the related EFI variables by launching a command prompt on the host machine using an Administrator account and run these commands:

mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS 
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d

Note: Ensure X is an unused drive, else change to another drive.

Restart the host. Accept the prompt on the boot screen to disable Device Guard or Credential Guard.

Source: https://kb.vmware.com/s/article/2146361