Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
E_FAIL (0x80004005) caused by Windows sandbox
E_FAIL (0x80004005) caused by Windows sandbox
I enable Windows Sandbox on my Windows 10 Enterprise, 1903.It makes an error code E_FAIL (0x80004005) so that I can't start a virtual machine. Here is the detail:
Last edited by socratis on 24. May 2019, 21:12, edited 1 time in total.
Reason: Enclosed the information in [quote] tag for better readability
Reason: Enclosed the information in [quote] tag for better readability
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: E_FAIL (0x80004005) caused by Windows sandbox
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
- Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
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.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 8
- Joined: 2. Nov 2017, 18:57
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 7, Windows 10
Re: E_FAIL (0x80004005) caused by Windows sandbox
Hello,
I had the same problem (Windows 10 1903 + windows sandbox feature activated), please find attached vbox log file.
Restoring the last windows restore point solved the problem. (disabling windows sandbox feature wasn't enough).
I'll stay away from this sandbox tool for a while.
I had the same problem (Windows 10 1903 + windows sandbox feature activated), please find attached vbox log file.
Restoring the last windows restore point solved the problem. (disabling windows sandbox feature wasn't enough).
I'll stay away from this sandbox tool for a while.
- Attachments
-
- Panorama 7.5-2019-05-27-09-24-30.zip
- (7.79 KiB) Downloaded 423 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: E_FAIL (0x80004005) caused by Windows sandbox
Windows Sandbox is just another name for a VM, i.e. Hyper-v. See previous discussions.
-
- Posts: 1
- Joined: 27. May 2019, 15:59
Re: E_FAIL (0x80004005) caused by Windows sandbox
I'm also seeing the same issue although I can't say it's caused by Windows Sandbox, as I didn't try running VB before enabling WSB i'll call it.
While mpack says this is hyper-v, I find it interesting that in Control Panel | Windows Features | Turn Windows features on or off, none of
Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
are enabled.
It looks like MS has created a "rose by any other name," that name being sandbox.
My vbox.log is attached.
While mpack says this is hyper-v, I find it interesting that in Control Panel | Windows Features | Turn Windows features on or off, none of
Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
are enabled.
It looks like MS has created a "rose by any other name," that name being sandbox.
My vbox.log is attached.
- Attachments
-
- ubu19-2019-05-27-21-47-35.zip
- vbox.log
- (7.48 KiB) Downloaded 246 times
-
- Volunteer
- Posts: 5105
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: E_FAIL (0x80004005) caused by Windows sandbox
Sandbox runs in an isolated environment. That environment is provided by using the hardware virtualization ability of the CPU (ie VT-x for Intel or AMD-V for AMD). This is the same reason that Hyper-V, Credential Guard etc prevent VirtualBox from running. It is, indeed, "a rose by any name".
Bill
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: E_FAIL (0x80004005) caused by Windows sandbox
Here's my list as it stands today:GregSDownUnder wrote:in Control Panel | Windows Features | Turn Windows features on or off, none of
- Application Guard
- Credential Guard
- Device Guard
- <any> * Guard
- Containers
- Hyper-V
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Sandbox
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
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.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: E_FAIL (0x80004005) caused by Windows sandbox
Hello,
Running off VirtualBox VM 6.0.8 (r130520 win.amd64), I have the same "WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}" error, with any guest VM I tried (DOS 6, Windows 7, etc.)
I do have Hyper-V enabled and running ok but, reading on that forum, I had the impression that VirtualBox was able to run with hyper-V enabled (with degraded performance and the green turtle icon, etc...) on recent versions on Windows. My Windows version is 1903 (10.0.18362 Build 18362.175), and has been installed from scratch pretty recently (not on any insider build), VT-x (and VT-d) are enabled in the BIOS (of course since Hyper-V runs ok)
So, is it possible to run VirtualBox on Windows 1903 with Hyper-V or just not?
PS: my CPU is detected as "Intel Core i7-6700K" as it's in fact an "i9-9900K", not sure it's of any importance.
Running off VirtualBox VM 6.0.8 (r130520 win.amd64), I have the same "WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}" error, with any guest VM I tried (DOS 6, Windows 7, etc.)
I do have Hyper-V enabled and running ok but, reading on that forum, I had the impression that VirtualBox was able to run with hyper-V enabled (with degraded performance and the green turtle icon, etc...) on recent versions on Windows. My Windows version is 1903 (10.0.18362 Build 18362.175), and has been installed from scratch pretty recently (not on any insider build), VT-x (and VT-d) are enabled in the BIOS (of course since Hyper-V runs ok)
So, is it possible to run VirtualBox on Windows 1903 with Hyper-V or just not?
PS: my CPU is detected as "Intel Core i7-6700K" as it's in fact an "i9-9900K", not sure it's of any importance.
- Attachments
-
- win7_VBox.zip
- windows 7 guest virtual box.log
- (6.86 KiB) Downloaded 235 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: E_FAIL (0x80004005) caused by Windows sandbox
It's a new feature, teething problems are to be expected, especially since MS keep moving the goalposts. The feature currently works fine for some, not for others. Complicated by people using "bleeding edge" versions of Win10. Eventually things will settle down, perhaps in a few months to a year.Smo wrote: So, is it possible to run VirtualBox on Windows 1903 with Hyper-V or just not?