[Solved] VirtualBox Won't run VM on Windows 10 builds 17123 and 17074

[jimi2shoes]

Hello

On Windows Insider builds 17074 and 17123 (January and March build releases), VirtualBox will no longer open any VM's. It returns the following error:
Failed to open a session for the virtual machine My Wordpress Clone.

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}

I have ensured that Hyper-V is uninstalled (done an install/uninstall), and VT-x is enabled in BIOS.
Rolling back to build 17063 or earlier works fine, just 17074 and 17123 appear to break VirtualBox (17123 from what I understand is the next release candidate for Windows 10 - this could render VirtualBox completely dead on the Windows platform once it goes gold)

[jimi2shoes]

Just as I posted the above, I found the solution:

open an admin command prompt and run:

bcdedit /set hypervisorlaunchtype off

This seems to have resolved the problem

[andyp73]

As you have seen, simply deselecting Hyper-V in the Windows features doesn't always disable the functionality. That seems to have been a problem for many people with the from Version 1709 (build 16299) release.

-Andy.

[boy_I_wish_this_worked]

Still seeing this error with all of the bios/powershell/etc. workarounds in place.

Code: Select all   Expand viewCollapse view

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}


Code: Select all   Expand viewCollapse view

VirtualBox Graphical User Interface
Version 5.2.8 r121009 (Qt5.6.2)

OS build is Windows 10, 14393.2125

[mpack]

Have you given any thought to what the error means? It seems very clear to me.

In any case, no analysis is possible when the VM log is not provided.

[bmcd77]

I also have this same error on Win 10.

Attached is my VM log and config file. Can someone help out please?

I have worked through the workarounds. Such as

Code: Select all   Expand viewCollapse view

bcdedit /set hypervisorlaunchtype off

I'm moving a VM to a new Dell Latitude 5590 laptop. I can't get to the bios (work machine) and believe VT-x is not supported. My CPU count is set to 1. <HardwareVirtEx enabled="false"/> in my config. I've run the powershell command to disable Hypervisor.

I'm stuck having tried several things. Any help appreciated.

Thanks

[mpack]

Reduce the RAM size to less than 4GB, as that makes it a 64bit VM. A Win7-32bit guest should run just fine with 2GB RAM.

[bmcd77]

Hi,

Thanks for the suggestion I've given it a try but the error is the same.

Code: Select all   Expand viewCollapse view

Failed to open a session for the virtual machine Win Server 2016.

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}

This VM is working fine on another 64 bit pc (albeit Win 7 not Win 10).

I suspect the issue is that VirtualBox thinks it should use Hyper-V here which is not available. I've run the line below and rebooted which should tell it to ignore Hyper-V but I need to do something else it seems?

Code: Select all   Expand viewCollapse view

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

[bmcd77]

This line in the log:

00:00:03.117816 HVP - Hypervisor Present (we're a guest) = 1 (1)

and these:

00:00:03.151280 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:00:03.152562 VMSetError: F:\tinderbox\win-5.2\src\VBox\VMM\VMMR3\VM.cpp(361) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT
00:00:03.152565 VMSetError: Raw-mode is unavailable courtesy of Hyper-V.
00:00:03.152813 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT)}, preserve=false aResultDetail=0
00:00:03.152985 Console: Machine state changed to 'PoweredOff'
00:00:03.166503 Power up failed (vrc=VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT, rc=E_FAIL (0X80004005))
00:00:03.667068 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1280x1024
00:00:03.667105 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={76eed314-3c72-4bbb-95cf-5eb4947a4041} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:03.667257 GUI: Aborting startup due to power up progress issue detected...
00:00:04.159583 OpenGL Error: Render SPU: (MakeCurrent) failed to make 0x6d01146d, 0x10000 current with 0x6 error.
00:00:04.171583 crUtil DLL unloaded.

Seem to indicate Hyper-V is having an unwanted say in the outcome but I'm no virtualBox expert

[bmcd77]

Also worth stating I'm on Win 10 Version 1709 (OS Build 16299.309) so different to the thread title although my actual error is exactly the same

[bmcd77]

I've run this also from powershell to disable Hyper-V

Code: Select all   Expand viewCollapse view

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

[bmcd77]

bcdedit under Windows Boot Loader indicates

Code: Select all   Expand viewCollapse view

hypervisorlaunchtype    Off

[bmcd77]

Just noticed, my desktop (running VirtualBox 5.1.28) (from which the VM is being migrated) shows Win 7 (64 bit) in the list when selecting new VM.

On the laptop (VirtualBox 5.2.8) it only shows up to Win 7 (32 bit). The VM I'm migrating would need 64 bit.

[andyp73]

A bit late to this party, but still...

Reading through your logfile you appear to have the OS template set to "Windows 7" but have called the VM and the disk file "Win Server 2016". If you are trying to run Windows Server 2016 as a VM guest then I doubt you will get very far without the VT-x support being enabled in the BIOS and passed through unadulterated to the guest.

On the laptop (VirtualBox 5.2.8 it only shows up to Win 7 (32 bit). The VM I'm migrating would need 64 bit.

This means that something is stopping VirtualBox using the VT-x support that your Core-i series processor has. You need to speak to your IT folks to get them to check it is enabled in the BIOS and then look at other possible culprits such as anti-virus as you seem to have applied all of the tricks to disable Hyper-V.

-Andy.

[bmcd77]

Thanks for the helpful reply Andy.

I'll ask the central IT guys to take a look at the bios settings for me here and see where I get to.