virtualbox.org

Hi Guys,

I wonder if you can help with this. I'm running Win 10 Pro latest build/fully updated, the latest build of VirtualBox, trying to install Win Server 2019 trial as guest VM. The installation crashes with an error message (which says post the log here) very shortly into the installation process.

I can't post the error log here, it's too big! (340 KB).

Thanks for any advice/help on how to possibly proceed from here. I tried the install.exe on my host OS and it began the installation process just fine btw.

Cheers, Ed

Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left and second left tabs' logs, zip them, and post the zip file, using the forum's Upload Attachment tab.

Many thanks, Scott.

When I ran it (from full power off, as far as I could see), it was not possible to shut it down from the guest, I just got an error message from the program saying press OK to shut down from the error, or Ignore to debug. So I pressed OK.

Here is the zip of the two logs you requested.

Thanks, Ed

The hardening log shows an exit code of 0, so your PC has no hardening issues.

Your vbox.log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x 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

Thank you so much, Scott! It's working now!

I'm not sure exactly what made the difference, as I made several alterations, but I suspect it was doing the BCD edit that did the trick.

While I've got you here: do you recommend using separate software firewall and anti-virus on the guest OS itself, or should the stuff I have on my host OS (ZoneAlarm, Windows Defender) be OK? I am using a NAT network connection to the host.

Thanks!

Ed

Each OS that touches the internet should have its own AV & malware protection.

Host AV can by default read the guest's disk and possibly memory, so you'd get double AV scans on the same data as well as possibly host AV blocking data from guest processes that the guest OS doesn't know about, causing guest OS crashes.

So I would put AV on the internet-connected guest OS's in addition to the host, and set exceptions in the host AV to not scan Virtualbox processes or guest files on the host's disks.