virtualbox.org

On a Windows 10 64bit host machine, I create a new VM for windows 10 64bit, allocate RAM and set up a virtual disk, then point the CD drive to my ISO file and start the VM. Nothing happens. I have looked at the log files and think it might have something to do with hardening - can anyone help me? I have already done a complete remove and re-install to no avail.

SHH wrote: I have looked at the log files and think it might have something to do with hardening - can anyone help me?

You treated yourself to a reading of the logs... How about extending the courtesy to us as well? We don't really like to "think it might", especially when we haven't looked at the logs.

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

Oh, and BTW, that VBoxHardening.log too. ZIPPED as well...

Sorry, here are the log files...

The log wrote:

00:00:21.740389 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:21.767674 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

The guest is running. Ought to be ready for use around 2024...

Microsoft Hyper-V is on, which makes Virtualbox guests glacially slow. You might see the green turtle icon with the V on its back in the guest window status bar: The choice of animal is not accidental When Virtualbox has full-speed capability not interfered by Hyper-V, this is the icon you'll see:

To turn off Hyper-V, see I have a 64bit host, but can't install 64bit guests Carefully go through each command in the 2nd & 3rd posts. Based on my perusal of successful fixes for this problem, the silver bullet appears to be the "bcdedit" command & complete power-down in post 2 point 1. Two full power-down shut-down & restart cycles may also be needed.

Thanks, turning off Hyper-V did the trick.

Very good! Glad you're running!

Marking as [Resolved].