Windows 10 Build 18917 Breaks VB 6.08

[TomL12953]

After upgrading to the latest build of Windows 10 (18917) I now get an error when opening a VM:

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}

[TomL12953]

I tried using Portable VB but the result was the same.

[BillG]

That is almost always caused by something blocking hardware virtualization.

viewtopic.php?f=6&t=93270
viewtopic.php?f=6&t=93476

[TomL12953]

Yes and that's the problem. It seems like Microsoft has not allowed virtual services (VMware and Hyper-V) to be disabled in the latest preview build (18917). I have disabled all of them in services.msc and the problem remains.

[zhangqi]

Yes I meet with the same problem.
My host is Windows 10 1903 18362.175
I am sure hyper-v and windows sandbox is turned off.
I remember that my vbox was running correctly before I upgrade to 6.08

[BillG]

There are no such problems with version 1903 (which you are running). I have been running it for months now with VirtualBox.You have missed something which is blocking hardware virtualization.

The same applies to the latest Insider build (18917). I have just upgraded my test machine and VirtualBox still runs fine.

[BitBuilder]

As a long time developer let me suggest "There are no such problems with version 1903" is not a constructive comment, there are never any problems until the first problem is discovered. Just because there are no issues on your setup, does not necessarily mean given the right set of actions it would not break as well. I think in this case the problem is that windows is not properly altering some underlying settings when using GUI (Turn Windows features on or off).

Please note I too ran into this problem on 1903 ONLY after enabling Windows Sandbox. The problem persisted AFTER DISABLING the Sandboxing feature. My thought is there is something in (1903) that is not being properly disabled when switching this setting (possibly others), this would be an inherent issue with 1903 that requires a workaround if true.. The resolution for me was to disable hypervisor launch via the ELEVATED cli using the command previously mentioned in other posts regarding the error [ERROR_SUCCESS (Last=0xc000000d/87)]:

bcdedit /set hypervisorlaunchtype off

I hope this works for you as well...

[socratis]

This should not have been in the "Windows Hosts" section, but in the "Windows Pre-Releases" section, moving it.