virtualbox.org

Hi there

get this error since a few days. Was working fine since weeks. Think it has to do with another update on Insider builds.
I'm running on

Windows 10 Enterprise
Version 1809
Build 18252.1000

I checked that Hyper-V is still deactivated/uninstalled and tried the

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

command, rebooted but still the same.

I also repaired the installation.

Help is highly appreciated.

Thanks and best
Udo

There isn't much room for doubt there. Either Hyper-v or one of the security features based on Hyper-v has been enabled by the update.

Related FAQ: I have a 64bit host, but can't install 64bit guests.

Hi there

Thanks for fast reply. I did another test: creating a new machine it just showed me 32-bit versions available - what?? So I configured a Linux Ubuntu 32bit one and started it with the image. I got the message "Raw-mode is unavailable courtesy of Hyper-V" - ok, so some more HyperV stuff is still active as you mentioned. I searched for and found that one I CANNOT POST URLS

Solution:
STEP 1:
Open the command prompt as an Administrator.

STEP 2:
Run the command with no argument: bcdedit

After you run the above command, you will see that the property hypervisorlaunchtype is set Auto by default.

STEP 3:
Disable Hyper-V by running the command: bcdedit /set hypervisorlaunchtype off

STEP 4:
Restart your PC system to use VirtualBox.

With me the auto launch type was still on auto, I deactivated, rebootet et voila - VirtualBox is running fine again, also offers me to create 64-bit versions again

Best
Udo

I imagine that a common mistake is to confuse stopping a program with disabling a program. In the former case it will simply start up again on next boot.

Thanks for reporting back.

Quick addendum in case any one else gets here with the same problem. If the above solution does not work; please check the thread titled: "I have a 64bit host, but can't install 64bit guests"
(Sorry, can't post direct links yet as I just created my account to write this).

If you are running Windows 10 and enabled core isolation without thinking, like me, you'll find yourself running around mad..

Great work @mpack !!! Thanks for the help

Hmm. That's the FAQ that my first reply should have pointed to, instead I accidentally pointed to the other most needed FAQ. Don't worry future readers: I just corrected it for you.

After trying everything else:

bcdedit /set hypervisorlaunchtype off

Worked for me: Win10 1903 Insider Preview 18932.1000

Thanks a lot

The FAQ already has that. It's point 1 in "Additional Notes for Windows Hosts" (second post).