﻿id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
19804	VM fails to start with VERR_NEM_MISSING_KERNEL_API_2 when using Hyper-V => fixed in SVN/next 6.1.x maintenance release	Wisent		"Error message:
""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).

Fehlercode: E_FAIL (0x80004005)
Komponente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""

VirtualBox COM Server 6.1.12 r139181 win.amd64 (Jul 10 2020 22:02:01)
OS Product: Windows 10
OS Release: 10.0.18363
Secure Boot: VERR_PRIVILEGE_NOT_HELD
Host RAM: 16131MB (15.7GB) total
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

It is independent of the created virtual machines like Ubuntu, Fedora etc.

In my opinion it is due to the VirtualBox Manager itself. The error describes that a session is already running and therefore cannot open another one. After installing and setting up the above mentioned virtual machines I closed the session and the VirtualBox Manager correctly.

When I completely uninstall VirtualBox Manger, everything runs without error message. When I log off or shut down the PC, I get the above error message.

I really hope there's a solution to this. Since I am still a beginner myself, I ask for detailed recommendations. Thank you.
"	defect	closed	GUI	VirtualBox 6.1.10	fixed	VirtualBox Manager		Linux	Windows
