VBox 6.1.8 and Windows 10 Pro 2004 host

[chrisb9]

Error as follows:

Failed to open a session for the virtual machine Win10 Test.

VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2).

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Happens on 2 guest machines - win10 pro and Ubunto Linux
Both worked prior to recent VBox update

M/B: Asus WS X299 Pro
CPU: Intel core i9 10920X
VT-x present and enabled

Windows Hyper-V, Virtual Machine Platform and Hypervisor Platform are installed
Kaspersky Internet Security has Hardware Virtualisation disabled
HWINFO64 shows CPU features shows VMX and V T-x3 enabled

any help would be appreciated.







HWINFO64 reports

[mpack]

Obviously, your host is not yet supported at all (1910 is the most recent supported Win10 release). But the best chance of getting VirtualBox to work would be to disable Hyper-v. Relevant FAQ (especially posts #2 and beyond): FAQ: I have a 64bit host, but can't install 64bit guests.

IMO, ditching Kasperski would be a good move too. Win10 is not Win98, it doesn't need third party help to be secure. Quite the opposite in fact.

[operation420.net]

1910, do you mean 1909?

I know enabling Hyper-V causes issues (I guess it they conflict with each other), but is WSL ok? I have machines with WSL enabled running VirtualBox...

[mpack]

Yes, I meant 1909.

WSL1 is fine, it was not a VM and hence doesn't enable Hyper-v.