Share via

How to fix virtualbox failed to open a session for the virtual machine (version 6.0.12)

Anonymous
2019-09-26T10:29:58+00:00

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}
Windows for home | Windows 10 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

20 answers

Sort by: Most helpful
  1. Anonymous
    2020-04-21T11:06:28+00:00

    I am from Spain so am Using W10 Home Spanish version

    Unknow how I get Hyper-V active, probably trying to instal Microsoft Sandbox with the sandbox-installer.zip

    file at Deskmodder (which did not work either).

    My VM VirtualBox went south after that and I have spend three days reading and trying lots of non-working solutions.

    Luckily I have found one that has restored my virtual box

    In a  Powershell window opened as Administrator

    bcdedit /set hypervisorlaunchtype Off

    reboot two times. I did them as cold reboot (unswitching computer from mains more than 10 seconds)

    Hope it work for you too

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-09-26T11:03:01+00:00

    Windows 10 Home 1903 

    OS Build - 18362.356

    10 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-04-26T11:05:32+00:00

    I am from Spain so am Using W10 Home Spanish version

    Unknow how I get Hyper-V active, probably trying to instal Microsoft Sandbox with the sandbox-installer.zip

    file at Deskmodder (which did not work either).

    My VM VirtualBox went south after that and I have spend three days reading and trying lots of non-working solutions.

    Luckily I have found one that has restored my virtual box

    In a  Powershell window opened as Administrator

    bcdedit /set hypervisorlaunchtype Off

    reboot two times. I did them as cold reboot (unswitching computer from mains more than 10 seconds)

    Hope it work for you too

    It really did worked for me!

    Thanks a lot man. You saved my lot of time.

    8 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-09-26T10:45:50+00:00

    I am not using Windows 10 Pro, I am using Home.

    8 people found this answer helpful.
    0 comments No comments
  5. Neil D 32,645 Reputation points Volunteer Moderator
    2019-09-26T11:26:16+00:00

    Have you tried a previous version of VirtualBox, perhaps 6.0.10 or 6.0.8. Or even go back to version 5.

    Strangely looking at you screenshot I don't have a setting for Windows Sandbox. I was under the impression that was only available with Windows 10 Pro. You could uncheck and restart that but I doubt it will make a difference.

    Do you get the error when you try to run VirtualBox initially or when you launch a new machine.

    I had to replace my graphics card a few years ago as I lost some functionality in machines in VirtualBox and more recently tried VMWare but that will not run a machine and warns me of a problem with processor support.

    Your GPU may be part of your problem and/or your processor or motherboard support. My system was custom built in 2010, an original i5 with an Nvidia GT710.

    You may never be able to run VirtualBox.

    5 people found this answer helpful.
    0 comments No comments