ERROR ..unavailable courtesy of Hyper-V .. on Windows 10 Version 1803

[Siggii]

Hi,
On Windows 10 Version 1803 build 17134 (July ?) , VirtualBox did no longer open any VM's with

Code: Select all

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

Furthermore, only 32bit machines are offered on trial to create new ones and old 64bit machines are restricted to 32bit ... strange...

Anyway, took me a few hours fiddling through the posts around Windows 10 Hyper-V issues.
Solution here was Windows Defender coming with new feature since Version 1803 !

I had the "kernel isolation" (? German: Kernisolierung) activated - which makes the funny Hyper-V error.
So, just switch it off in Windows Defender and everything will be fine again.
Hope it helps some users ...

[socratis]

On Windows 10 Version 1803 build 17134 (July ?)

No, actually it's 2018-03 (1803), so it's March/2018.

I had the "kernel isolation" (? German: Kernisolierung) activated - which makes the funny Hyper-V error.

Microsoft comes with new innovative ways of enabling Hyper-V without letting the end users know about it, leaving us scratching our collective heads.

Thank you for posting the information.

[BillG]

That is not strictly accurate. There is a problem with Hyper-V or Credential Guard being used instead of hardware virtualization in error messages.

Disabling Hyper-V or Credential Guard does not solve the problem if, as in this case, it is something else causing the problem.

I had never seen this one before, in version 1803 or the Insider builds since then.

[Jacek_T]

I have same problem on my Windows 10 Enterprise (same version as mentioned here 1803, 17134.619). VirtualBox version 6.0.4
Symptoms:

1. I only have 32 bit quest os available, no 64 bit option
2. When starting 32 bit quest I have error VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT

Things I did according to this topic from this forum "I have a 64bit host, but can't install 64bit guests"

1. My CPU is E3-1505M v6 and it has VT-x and VT-d
2. In BIOS/UEFI I enabled VT-x and VT-d, and disabled Trusted Execution Technology
3. Hyper V is disabled in Windows features (bcdedit says "hypervisorlaunchtype Off")
4. In "Local Group policy" I disabled "Turn on Virtualization Based Security" and "Deploy Windows Defender ...."
   (I also edited it in registry, the key EnableVirtualizationBasedSecurity is set to 0, it wasn't set to 0 after disabling option from 'Local Group Policy')
5. I set ' Core Isolation Details ' in registry (don't have access there) in HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ DeviceGuard \ Scenarios \ HypervisorEnforcedCode Integrity, after registry change it is marked as off in Windows
6. I checked Socratis list and:
   • Windows Defender Application Guard -> turned off
   • Credential and Device Guard -> successfully (?) disable in point 4
   • <any> Guard -> didn't find anything else
   • Containers -> turned off
   • Virtual Machine Platform -> N/A, it is probably available from build 1809
   • Windows Hypervisor Platform -> turned off
   • Windows Sandbox -> N/A
   • WSL2 -> N/A

I also did two more things that didn't help

• dism /Online /Disable-Feature:Microsoft-Hyper-V in CMD
• disabled FastBoot

Anything else I should check or set?

[mpack]

Things are moving fast with Windows 10, so commenting on a year old topic is not really helpful. Search for current discussions of Hyper-v, they are not hard to find.

Locking this.