How to get VMs being created (again) in VirtualBox 6.1 on a Windows 10 host?

[automatix1311]

Hey guys!

Since I upgraded my host system from Windows 7 Ultimate to Windows 10 Pro, I cannot create any VMs anymore. I've already updated (remove and installed again) my VirtualBox to the very recent version (Version 6.1.14 r140239 (Qt5.6.2)) and also repeated the Windows 10 installation process, in order to repair the system, if somethind went wrong during the upgrade. But no effect: The installation of Ubuntu, Debian, or Windows guests cannot be completed. Here is an example, where I was trying to install Ubuntu 20.04 Server:

Already on the very first installation screen I was greeted by errors:

errro-screen-1.png (19.75 KiB) Viewed 1226 times

Then I got the language choice, keyboard layout, and some further installation steps. But the last station is always the "Profile setup" screen. After fill in the form and click on "Done", the installation process breaks:

errro-screen-2.png (30.02 KiB) Viewed 1226 times

How to get it working (again)?

[scottgus1]

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 tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

[automatix1311]

Thank you very much for the step-by-step instruction! Just restarted the complete process, run into the error, and shut down ("Power Off...") the machine. Please find the log attached.

[scottgus1]

Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

[automatix1311]

I'm running VirtualBox 6.1, which should be able to work with activated Hyper-V. But anyway, Hyper-V is disabled on my system:

Hyper-V.png (16.69 KiB) Viewed 1218 times

Docker-Hyper-V-alert.png (13.46 KiB) Viewed 1211 times

And WSL2 is currently disabled as well (just in case):

WSL2.png (20.97 KiB) Viewed 1218 times

[scottgus1]

The log does not lie.

Did you read the linked tutorial?

Did you read the original tutorial linked in the above tutorial? There's other stuff besides "Hyper-V" that uses Hyper-V.

And yes Virtualbox is supposed to and in a few rare cases does work with Hyper-V. It's still a work in progress.

[automatix1311]

Did you read the linked tutorial?

At first not, because I knew, that Hyper-V is definitely deactivated on my host. But now I've read it and... hm, no idea, what to do now. Since there seem to be Windows features, which "implicitly enable Hyper-V":

• Application Guard
• Credential Guard (see https://www.microsoft.com/en-us/downloa ... x?id=53337)
• Device Guard (see https://www.microsoft.com/en-us/downloa ... x?id=53337)
• <any> * Guard
• Containers
• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Sandbox
• Windows Server Containers
• Windows Subsystem for Linux 2 (WSL2) (WSL1 does not enable Hyper-V)

Does this mean, that a feature, that is blocking VirtualBox, e.g. Hyper-V, can be being kind of "half-enabled" (implicitly), even if it seems to be disabled? If so, I'm giving up for now, since I don't know, how to check all that features, and even if I check them, it's a bit too dangerous for me to make such experiments on my host system. So it seems to be more sensible (for me) to let to issue be and try again later.

Anyway -- thank you very much for your time and help!

[scottgus1]

no idea, what to do now

If you want Virtualbox running, follow the link I posted.

"You can bring the horse to water, but..."

[automatix1311]

no idea, what to do now

If you want Virtualbox running, follow the link I posted.

"You can bring the horse to water, but..."

I didn't read the whole linked article: Instead I read it from begin to the link to the original post and then the original post itself. And after it I just thought, that I have to check every single feature, that might enable Hyper-V implicitly, separately and turn it off, without to know exactly, what it does, which might break my host system. Anyway, now I read the first (short) post to the end and tried the steps out. And... it worked!

Short version:

1. I opened CMD as admin.

2. I executed the command

Code: Select all

bcdedit /set hypervisorlaunchtype off

3. I shut the computer down by executing

Code: Select all

shutdown -s -t 2

Now I've started the host again. It' still no "V" icon displayed in the system tray. (Why?) But I can now complete the Ubuntu Server 20.04 on my VM.

Thank you very much!

[scottgus1]

It' still no "V" icon displayed in the system tray.

Please zip and post another guest vbox.log.

[automatix1311]

It' still no "V" icon displayed in the system tray.

Please zip and post another guest vbox.log.

Here we go...

[scottgus1]

Hyper-V is fully off now:

00:00:02.729558 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support

It' still no "V" icon displayed in the system tray. (Why?)

The "V" icon is displayed in the guest's Virtualbox window status bar, not in the host's or guest's system tray.

Glad you're up and running!