[Solved] Windows 10 VM doesn't start

[Vassili]

Hi, I'm running version 5.0.12, previously I've had the same issue with 5.0.10. The Windows 10 image downloaded off modern.ie would not start - blue windows logo shows up, and the machine just sits there forever with the full CPU load. I've played around with the VM settings to no avail. Also, I've been running various Windows 7 guests on the same machine/VirtualBox installation with no issues. If you could take a look at the log to see what might be going wrong, that would be great. Thanks!

[mpack]

You are assigning more RAM to the guest than you have available on your host. Try reducing VM RAM to 2GB.

[Vassili]

Hi, thanks for the response. I've lowered it to 2GB, and still the same thing is happening. This PC has a total of 8GB ram and setting VMs to use 4 was never an issue in the past..

[loukingjr]

I don't know if this may be a factor but in the log it is apparent that there is no extension pack installed in VirtualBox. Perhaps the Windows 10 appliance needs USB support. There are no guest additions. Ditto. 2D is disabled.

I've run the Windows 10 appliance myself without issue.

[loukingjr]

I just installed the appliance for the umpteenth time and I do think it must be the lack of the extension pack. It was already installed in mine and Windows 10 started up fine even with 2D and 3D disabled. I'm not sure why the guest additions didn't show in the log because they do come pre-installed.

Audio and USB were disabled in the guest OTB.
I did assign it 2 CPUs instead of the default 1.

[Vassili]

Installed the extension pack and the issue persists.. Uploaded new log, basically looks the same as before. Anything else I could try? Thanks!

[Perryg]

I find this interesting.

Code: Select all

00:00:02.002501 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!

AFAIK NX is required for Windows 8.1 and newer

[Vassili]

I find this interesting.

Code: Select all

00:00:02.002501 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!

AFAIK NX is required for Windows 8.1 and newer

Turned on the setting in BIOS and it's working now! Thank you very much!

[mramsath]

I faced similar issue, my VMs were not started and hanging with blinking cursor even though i set all the configuration as suggested here as well as some other forums, I didn't check my logs as i was find it difficult read what's in the log files.

Anyhow my issue was because of my docker installation I have already enabled Windows hyper-v option, When I disabled this option in "Turn windows features on or off" , my VMs started successfully.

"Turn windows features on or off" and Untick following option only enough

Hyper-V -> Hyper-V Platform -> Hyper-V Hypervisor

[mpack]

The problem discussed in 2016 was unlikely to be Hyper-v related. In fact the OP already indicated what the solution was.

Hmm. I think this topic is obsolete, locking it.