Windows 10: HMR3Init: Attempting fall back to NEM: VT-x is not available on VirtualBox

​

VirtualBox failed to launch a virtual machine, and when investigating a bit, we found that vbox.log throws either of the following error messages. {timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available {timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work… or {timestamp} HM: HMR3Init: Attempting fall back to NEM: AMD-V is not […]

This article HMR3Init: Attempting fall back to NEM: VT-x is not available on VirtualBox first appeared on TheWindowsClub.com.

read more...

 

Windows VM stucks on Virtualbox but not on VMWare

Create a new VM again, windows 10 64bit and attempt to fire it up. Then right click on it, and get the logs. Looking for a line similar to this

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

Feel free to post your log and I can look at it.
{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

 

Windows VM stucks on Virtualbox but not on VMWare

Yeah, you're right. there is a log with the statement above. So what could I do?

- - - Updated - - -

Well, now I'm even more confused. I kept the vm with win 10 you wanted running, I was even able to complete the setup and boot into the desktop. When I'm adding one addition core (4 cores to be assigned are marked green in VBOX) the same issue occurs like before. The win7 vm with one core stuck as we know already. The image shouldn't be the problem, VMWare can handle it.

 

VirtualBox is saying that VT-x is not available, but it is?

So this is my first thread on this site! :3 Nice to meet you all. I'm a Linux user who's started to come back to Windows to learn more about it (I need to, if I truly call myself a Geek). So, a bit of context. VirtualBox works just fine under Linux (Ubuntu), with VT-x, Nested Paging and everything working just fine. But under Windows, despite having VT-x enabled in the UEFI, I still can't seem to get my VMs up and running. :\ VirtualBox complains about VT-x not being available, thought it's enabled in the UEFI on this HP EliteBook 8470p... I checked Hyper-V in the features and settings Program (I'm using Windows 10 Pro with a Windows 7 Pro License linked to my Microsoft Account, which surprisingly worked). But alas, to no avail. :\ What am I missing here? Is it something deep in the Windows Registry, or is it some more general setting? Before I enabled Hyper-V, it didn't work either. Currently, I'm under Ubuntu (yes, I like Ubuntu despite all the other Distros I've used. *Wink) VirtualBox is also the latest stable version, version 6... I also like Windows 10 and WSL with Debian, so I can Compile Programs without having to octa-boot between Operating Systems. Well, this is my first post. It's very nice to meet you all. *Biggrin I'll reboot into Windows 10 now, so I can further provide any info. Thanks for any suggestions and help! *Wink