OSF fails to boot image with VirtualBox - Error VBoxManage VERR_NEM_VM_CREATE_FAILED

[David (PassMark)]

If the host system you are using to boot a disk image into a virtual machine with OSForensics isn't setup correctly you can get the following error

Booting virtual machine using Virtual Box
Starting virtual machine with VBoxManage: "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm "<image_name>""
Waiting for VM <image_name> to power on...
[B]VBoxManage.exe[/B]: error: Call to [B]WHvSetupPartition failed[/B]: ERROR_SUCCESS (Last=0xc000000d/87) ([B]VERR_NEM_VM_CREATE_FAILED[/B])
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

The solution is detailed here, https://superuser.com/questions/1442...-create-failed

In summary,

1. Turn off Hyper-v
2. Turn off Windows sandbox

This can be done by navigating to "Turn windows features on or off". Restart the machine twice and then try to Start vm in virtualbox.

This seems is a new "feature" in Windows 10 v1903 that uses Hyper-V on the backend (even if it's not enabled in Windows Features), which makes this feature not compatible with VirtualBox.