[NotSupported] Can's start VMs with Hyper-V and Win10 < 1809

[JungleBoogie]

Hi All,

I have an issue where I cannot start any VM's.

I get the following error:
The native API dll was not found (C:\WINDOWS\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).

I checked my BIOS, and virtualization settings are set correctly.

Furthermore, In the VM's settings I get a 'Invalid settings detected' warning. It states that HW virtualization is enabled in the acceleration section, but not supported by the host system.
But for some reason, I can not disable this feature.

I have attached a log from one of the VM's.

Hope you can help

[socratis]

00:00:02.189884 OS Release: 10.0.16299    <-- That's 1709
00:00:02.359510 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.359667 NEM: NEMR3Init: Native init failed: VERR_NEM_NOT_AVAILABLE

It seems that you have Hyper-V enabled, but your Win10 1709 doesn't have the necessary capabilities, see the sticky "VirtualBox 6.0 and Hyper-V". You can tell if this is true from the status bar where the "slow" icon () shows. Look in the "Control Panel" » "Programs and Features" » "Turn Windows features on or off", and make sure that the none of the following are active:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform

If VirtualBox is running without Hyper-V enabled, where proper, hardware virtualization is actually available, then the standard virtualization icon () would show. Disable Hyper-V in your host and see what happens...

[ayoobn89]

I've the exact problem! Hyper-V is disabled
anyone ?

[mpack]

I've the exact problem! Hyper-V is disabled

If you have the problem then Hyper-v is not disabled.

These days there are a whole load of Windows security features which implicitly enable Hyper-v (or the Windows Hypervisor Platform as it has begun calling itself). I don't know them all: every day there seems to be another.

[socratis]

I don't know them all: every day there seems to be another.

Tell me about it, it's a pain, a royal one. For example, since my previous post the list is quite longer and getting more and more so:

• Application Guard
• Credential Guard
• Device Guard
• <any> * Guard
• Containers
• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Sandbox

[sunny2187]

Hi All,

I am also getting the same error. I went through the earlier posts, but unfortunately could not identify the solution.

Attached the log file.
Any help would be appreciated.

[socratis]

00:00:02.409294 OS Release: 10.0.15063

That's Windows 10 1703, which means from 2017-03. You need to update your Windows, it's 2 1/2 years old. And the answer to your question is in a sticky on the "Windows Hosts" section, "VirtualBox 6.0 and Hyper-V", the red letters part...

00:00:02.636057 HM: HMR3Init: Attempting fall back to NEM: VT-x is disabled in the BIOS for all CPU modes
00:00:02.636214 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1299) int __cdecl nemR3NativeInit(struct VM *,bool,bool); rc=VERR_NEM_NOT_AVAILABLE
00:00:02.636310 VMSetError: The native API dll was not found (C:\WINDOWS\system32\WinHvPlatform.dll)
00:00:02.636353 NEM: NEMR3Init: Native init failed: VERR_NEM_NOT_AVAILABLE.
00:00:02.636361 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\HM.cpp(599) int __cdecl HMR3Init(struct VM *); rc=VERR_VMX_MSR_ALL_VMX_DISABLED
00:00:02.636378 VMSetError: VT-x is disabled in the BIOS for all CPU modes

Let me try and explain what's going on here, I'm going to analyze the red lines from your log above...

00:00:02.636057 HM: HMR3Init: Attempting fall back to NEM: VT-x is disabled in the BIOS for all CPU modes

VirtualBox doesn't see VT-x as being available. It will try to switch to the "NEM mode", that's Native Execution Manager, which means use Hyper-V as its virtualization engine.

00:00:02.636310 VMSetError: The native API dll was not found (C:\WINDOWS\system32\WinHvPlatform.dll)

But VirtualBox can't use Hyper-V as its engine. That's because the Hyper-V API was not available with that version of Win10, Microsoft released it later.

00:00:02.636378 VMSetError: VT-x is disabled in the BIOS for all CPU modes

And now VirtualBox discovered that it simply can't run, VT-x (for one reason or another) is not there. Check your BIOS BTW for hardware virtualization being enabled or not. If not, enable it, shut down the computer, pull the plug (literally) for 30". Try again...


BTW, changing the thread title from "Error when starting hosts" to something that actually makes sense and marking it as [NotSupported]...

PS. For future reference you should ZIP your logs. It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...

[computer-tech]

hi,
im on windows 7. does someone have a fix with this?

[mpack]

If you're on Windows 7 then you don't have Hyper-v, so you don't need a fix for this.

For the generic problem of VT-x/AMD-v not being enabled, please read: FAQ: I have a 64bit host, but can't install 64bit guests.

I'm going to lock this old topic. If you need to discuss some more then create your own topic, describe the problem (not your diagnosis), and attach a zipped VM log.