Hey guys, I noticed a big change in Hyper-V Requirements as reported by systeminfo.exe BEFORE and AFTER enabling the Windows Sandbox feature. Enabling Windows Sandbox caused a change in Hyper-V which persisted even after removing the Windows Sandbox feature which seems to be at the root cause of VirtualBox failure to load Virtual Machines. My findings are below, what do you think?
AFTER updating Windows 10 to 1903
Oracle VM VirtualBox worked as normal with no problems. Virtual machine loaded successfully.
AFTER adding the Windows Sandbox feature
Oracle VM VirtualBox failed to load Virtual Machine.
Error: Failed to open session…
(VERR_NEM_MISSING_KERNEL_API).
VT-x is not available (VERR_VMX_NO_VMX).
Subsequently
REMOVED the Windows Sandbox feature
Oracle VM VirtualBox again failed to load Virtual Machine, outputting the same error message as noted above.
TEST
Run systeminfo.exe from the command prompt:
BEFORE adding Windows Sandbox feature
Hyper-V Requirements:
VM Monitor Mode Extensions: Yes
Virtualization Enabled In Firmware: Yes
Second Level Address Translation: Yes
Data Execution Prevention Available: Yes
AFTER adding Windows Sandbox feature
Hyper-V Requirements:
A hypervisor has been detected. Features required for Hyper-V will not be displayed
AFTER removing the Windows Sandbox feature
Hyper-V Requirements:
A hypervisor has been detected. Features required for Hyper-V will not be displayed