run script with parameter -disable (see image below).start powershell as admin in the directory that contains the unzipped archive contents.
Thanks to my colleague, André van Winssen, I learned about these steps that finally resolved my situation: And sometimes to be sure a cold reboot and even more than one. Make sure none of these Windows Programs or Features are running:Īnd to disable Hyper-V from starting the following command can be used:Ī reboot of Windows 10 is necessary. When I tried to open a VM in the Oracle Virtual Box GUI that used to run fine before the Windows Update (to Windows 1903), I got a similar error.įollowing the instructions in the Forum Thread (and ) to disable absolutely everything in Windows that has any connection with Hyper-V, I was not able to solve the issue – although I guess these steps are required too – and they seem to be enough for many users: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).Result Code: E_FAIL (0x80004005)Component: ConsoleWrapInterface: IConsole When running vagrant to provision a VM, I ran into messages such as:įailed to open a session for the virtual machine. Like so many colleagues and fellow developers around the world, the latest Windows Update also messed up my machine’s ability to successfully run Oracle Virtual Box.