problems with win10 1803 and virtualbox

[Userpog]

After upgrading to Win10 1803, I can not load the virtual operating system into VirtualBox 5.2.16 I have a message:

VT-x is not available (VERR_VMX_NO_VMX). E_FAIL (0x80004005) Компонент: ConsoleWrap Интерфейс: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Can you help me?

[Mihai Hanor]

Disable or uninstall the Hyper-V hypervisor. Disable Memory integrity in Windows Defender - Device security - Core isolation. Reboot. Use the VirtualBox Forums to get help, not the bugtracker.

[VBH]

I do see the same at my Windows 10 x64 machine. VirtualBox was running fine till some recent Windows (or maybe McAfee?) patch which seems to cause this behavior. Latest patches I have installed before I saw the issue: KB4338832 KB4339420 KB4284219

And sure: all the typical suspects are checked (VT on, Hyper-V off, Defender off)

[Socratis]

That error means that something is using exclusively VT-x, and that would be Hyper-V or components that rely on Hyper-V. There's no way on this side of the universe for anyone (but the author) to know which app that is.

And @VBH, McAfee is a strong contender, along with the other characteristics that "mhanor" mentioned. It's not simply a checkbox. Search the webs on how to disable them. MS is adding constantly components that rely on Hyper-V, and although it might be unchecked, it's used under the hood, which makes it even more difficult to find the offender. Search the forums...

I believe this ticket to be [Invalid].

[Socratis]

BTW, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".