new VM won't launch

[megaabite]

trying to create new VM with 6.1.8

setup the new VM, attached Windows 10 ISO.

but the VM crashes on launch, "A critical error has occurred while running the virtual machine and the machine has been stopped".
says to upload the log and PNG. PNG attached but the log is greater than 128k.

where do I go from here?

[multiOS]

Could you 'zip' the log before attaching it, which should bring it down to an acceptable size? 'zipped' files are preferred on the Forum, even if the original is less than 128k

[megaabite]

doh!

'zipped' log attached

[scottgus1]

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

If your Virtualbox does not start successfully, zip and post another vbox.log. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

[megaabite]

Thanks. That worked.

Tried Hyper-V but it couldn't do what I needed. Uninstalled it. But had to execute commands and shutdown before VirtualBox would run as expected.

Thanks again!