Call to WHvSetupPartition failed

Discussions related to using VirtualBox on Windows hosts.
Post Reply
rai1
Posts: 2
Joined: 10. Nov 2020, 15:47

Call to WHvSetupPartition failed

Post by rai1 »

Hi,

I've spent many hours trying to sort out issue loading my VM but I get the same error every time at boot up. Please help!!

Code: Select all

Failed to open a session for the virtual machine RAI-Win10.

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

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

I'm using Virtual box Version 6.0.18 r136238 (Qt5.6.2) and already have guest machine installed. The VM currently runs on my Windows 7 machine, I've exported from my Win7 machine and imported it into my new Win 10 machine. Becides attempting this on 6.0.18, I've also tried using virtual box Version 6.1.16 and 6.1.18 on the windows 10 machine and got the same error. I've attached my log files

Code: Select all

OS Name:                   Microsoft Windows 10 Enterprise
OS Version:                10.0.18363 N/A Build 18363
System Model:              Latitude 7300
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 142 Stepping 12 GenuineIntel ~1600 Mhz
BIOS Version:              Dell Inc. 1.10.1, 03/08/2020 
Time Zone:                 (UTC+00:00) Dublin, Edinburgh, Lisbon, London
Total Physical Memory:     16,201 MB
Available Physical Memory: 12,162 MB
Virtual Memory: Max Size:  18,633 MB
Virtual Memory: Available: 14,458 MB
Virtual Memory: In Use:    4,175 MB

These are the common windows feature setting i've found where others managed to get their VM working who experienced the same issue. I implemented the same settings. Also did a cold reboot twice as advised in some of the posts.

Code: Select all

Virtual Machine Platform   UNCHECKED
Windows Hypervisor Platform UNCHECKED
Windows Sandbox UNCHECKED
Containers UNCHEDKED 
Sandbox UNCHECKED
Core Isolation/Memory INTEGRITY off
bcdedit /set hypervisorlaunchtype off

Code: Select all

My machine setting
Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-GB
inherit                 {bootloadersettings} 
displaymessageoverride  Recovery
recoveryenabled         Yes
badmemoryaccess         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Off
useplatformclock        No
Attachments
VBox.zip
(30.82 KiB) Downloaded 4 times
rai1
Posts: 2
Joined: 10. Nov 2020, 15:47

Re: Call to WHvSetupPartition failed

Post by rai1 »

Bumping this, any advise regarding this issue? Any help greatly appreciated.
Thanks you.

Rai
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Call to WHvSetupPartition failed

Post by scottgus1 »

You got both of the tell-tale signs:
VERR_NEM_VM_CREATE_FAILED: What do I do?
HMR3Init: Attempting fall back to NEM (Hyper-V is active)

Hyper-V is is still enabled and interfering. Yes, the info you posted seems to indicate it's off, but Virtualbox doesn't think so.
Post Reply