[Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Discussions related to using VirtualBox on Windows hosts.

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby socratis » 21. Jul 2019, 20:20

Seriously now? For real? A new Terminal? One that requires VT-x??? :shock:
Why don't they just go ahead and make the Calculator its own hardware accelerated, VT-x enabled, app? :roll:
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25831
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby haty1 » 24. Jul 2019, 11:41

Thanks @socratis, your instructions fixed it for me!
Windows 1903
haty1
 
Posts: 1
Joined: 24. Jul 2019, 11:36

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby MilenG » 26. Jul 2019, 14:13

Looks like "Enabled -> Virtual Machine Platform" leads to something like "vt -x is not available". So, after solving this the current "Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)." appears. And I haven't reached solution to this yet.
MilenG
 
Posts: 1
Joined: 26. Jul 2019, 14:08

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby scottgus1 » 26. Jul 2019, 14:21

Milen, the Virtual Machine Platform inWindows would re-enable Hyper-V and hog VT-x. If you want to run Virtualbox on Windows 10 you should deactivate everything related to hyper-V, as shown in this thread: viewtopic.php?f=1&t=62339#p452019
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
Volunteer
 
Posts: 4447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby rqcol » 3. Aug 2019, 13:34

i have followed all the steps given above but still i get the error whats next because i have enabled disabled, bios settings still nothing help me
thanks frankie
rqcol
 
Posts: 1
Joined: 3. Aug 2019, 13:25

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby scottgus1 » 3. Aug 2019, 14:28

@rqcol, first, you need to buy a new keyboard. Apparently its Shift keys and period key are broken, and the comma key is sporadic. It also seems to be stuck in Twitter mode.

Then look at Minimum information needed for assistance.
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
Volunteer
 
Posts: 4447
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: Win 10 1903 ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)

Postby BenevalJr » 15. Aug 2019, 22:21

rd91 wrote:bcdedit /set hypervisorlaunchtype off

Tks, this solution works for me...
BenevalJr
 
Posts: 1
Joined: 15. Aug 2019, 22:09

Re: Win 10 1903 ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)

Postby oferdavidi » 16. Aug 2019, 18:42

Thnx, the same here :)
oferdavidi
 
Posts: 2
Joined: 29. Dec 2018, 02:09

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby ¯\_(ツ)_/¯ » 6. Sep 2019, 05:30

May see info for disabling Windows Defender Credential Guard if still having issues... MS Docs credential-guard-manage
¯\_(ツ)_/¯
 
Posts: 1
Joined: 6. Sep 2019, 05:25

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby socratis » 6. Sep 2019, 06:26

¯\_(ツ)_/¯ wrote:MS Docs credential-guard-manage

I think that this is the one that you mean: Manage Windows Defender Credential Guard (https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-manage).
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25831
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Win 10 1903 ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)

Postby jburro » 28. Sep 2019, 15:33

Thanks for the clear instructions, this worked for me with Windows 10 1903 (unlike previous posts).

rd91 wrote:Google search results led me here, this may help someone else (may not work for all configurations).

Error:
Code: Select all   Expand viewCollapse view
Failed to open a session for the virtual machine ubuntu-server.
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}

Solution:
Code: Select all   Expand viewCollapse view
Windows Features
----------------------
Disabled -> Hyper-V
Enabled  -> Virtual Machine Platform
Enabled  -> Windows Hypervisor Platform
Disabled -> Windows Sandbox

Elevated Powershell/Cmd
-------------------------------
bcdedit /set hypervisorlaunchtype off

BIOS
-----
Enabled  -> Virtualization Technology (VTx)
Enabled  -> Virtualization Technology for Directed I/O (VTd)
Disabled -> HP Hypervisor

Windows specifications
----------------------------
Edition     Windows 10 Pro
Version     1903
OS build    18362.116

Other Windows Features (Possibly irrelevant, can view img*)
Code: Select all   Expand viewCollapse view
i[.]imgur[.]com/NgDGQvW.png

*Forum won't let me post images due to account age
jburro
 
Posts: 1
Joined: 28. Sep 2019, 15:31

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby Spoons » 14. Oct 2019, 21:56

I just started using VirtualBox a few days ago, I got everything setup so I could run some legacy CAD software on a Windows XP Professional virtual machine and then this damn Windows 10 Update 1903 screwed up everything. I'm in this process because my Windows 2000 computer is reaching the end of its lifespan and I need to take the next step into the modern 2019/2020 CAD world. This virtual machine concept is relatively new to me, the only one I've had to deal with was an older server that was put on a virtual rive while our new server was being built.

I read through some of the "fixes" in some of these threads and did what I full understood how to do and the rest of the instructions simply blew straight over my head. I'm not a professional IT guy, I'm a long time above average user from all the way back to the old DOS days and I knows enough to fix a lot of things and I also know when to get an IT professional to take up where I lacking in knowledge.

I'm really frustrated with this turn of events to say the very least; I get it all working and then it dies because Windows 10 upgraded. When I compared the two; I liked VirtualBox better than Hyper-V because Hyper-V seemed a lot slower for graphics intense software like my legacy CAD software packages.

Is it possible for VirtualBox to write an updated version that can be installed on a Windows 10 with the 1903 upgrade so I can simply install it and it will work without jumping through all kinds of IT hoops? If not; can someone write a step-by-step detailed instruction on how to fix this? I literally have thousands of legacy CAD files (2003 software and earlier) that I need to be able to access until I get things recreated in 2019/2020 software.

I have a bad feeling that the next major Windows 10 upgrade might cause the same kind of headache.

Spoons
Spoons
 
Posts: 2
Joined: 14. Oct 2019, 21:34

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby BillG » 15. Oct 2019, 00:39

The short answer is no. There is no way that VirtualBox can access hardware virtualization if the host OS or some program running on that OS is using it. The devs are trying to find a workaround but have had little success.

You are correct on one point. Microsoft (and other software developers) are constantly finding new ways to use hardware virtualization, so the list of things which interfere with VirtualBox (and other type 2 hypervisors) will continue to grow.
Bill
BillG
Volunteer
 
Posts: 4181
Joined: 19. Sep 2009, 04:44
Location: Sydney, Australia
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 7,8,Server

Re: [Solved] Windows 10 Version 1903: Failed to open session; call to WHvSetupPartition failed

Postby Spoons » 15. Oct 2019, 01:26

BillG wrote:The short answer is no. There is no way that VirtualBox can access hardware virtualization if the host OS or some program running on that OS is using it. The devs are trying to find a workaround but have had little success.


Bummer :(

BillG wrote:Microsoft (and other software developers) are constantly finding new ways to use hardware virtualization, so the list of things which interfere with VirtualBox (and other type 2 hypervisors) will continue to grow.


It's no just screwing with hypervisors, the 1903 update also completely wrecked my one month old brand new SolidWorks 2019 CAD software running on Windows 10, I had to completely unload it and do a new install. This kind of stuff eats up a LOT of time that I could be productive, it's all so danged frustrating!
Spoons
 
Posts: 2
Joined: 14. Oct 2019, 21:34

Previous

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 48 guests