After installing Hyper-V, VirtualBox works not

[MIRKOSOFT]

Hi!

I'm long time using VirtualBox in Windows. I wanted to compare embedded Hyper-V and added this feature to Windows 10 Pro.
Used and later decided to use VirtualBox.
Problem: I tried to start VBox in many possibilities, it starts not.
Then I removed Hyper-V feature away from Windows, tried to start again - no change.
Summary: Why VirtualBox starts not after testing Hyper-V? Means this that Microsoft makes barrier or so?
Thank you all for each help.

Miro

[Martin]

Make sure you have removed the Hyper-V feature. Just disabling it isn't enough.

[MIRKOSOFT]

Hm,
I tried to remove it, but there's only option to Enable or Disable.
I was searching for any files of Hyper-V - nothing found in Advanced Uninstaller, Device Manager - I know not how to remove it.

Can you help me?

[BillG]

How did you enable Hyper-V? The normal method is from Programs and Features. You use the reverse process to remove it ( ie you clear the checkmark from the box).

If Hyper-V is installed, the boot process locks hardware virtualization to its hypervisor, so VirtualBox or any other program cannot use it if Hyper-V is installed.

[MIRKOSOFT]

Yes, true, I did it so and never again was VirtualBox running.
In first post was written that disabling is not enough, it needs remove - so if is meaning remove by Add/Remove Windows Features, I did it and nothing more, VBox is not running

Miro

[Perryg]

It also requires a reboot of the host just in case you didn't do that.

[MIRKOSOFT]

Boys, really it's not problem of reboot or some similar things.

I did reboot many times, in all - did all what is normally available, even started VirtualBox directly from Program Files folder and with admin rights...
I don't know really what it causes andI'm not newbie in Windows, so if it needs reinstall, I'll do it, but only when I'll see thatreally nothing other is possible
Now I see what does Microsoft with its own free Hyper-V: liquidates concurent

Miro

[BillG]

If you are familiar with Windows, do a bcdedit /enum and have a look at the value in hypervisorlaunchtype. If it says off, Hyper-V is not active.

If it is off and VirtualBox will not run, it is not Hyper-V causing you problems.

[MIRKOSOFT]

I did.

Value: Auto

What with?

Miro

[BillG]

Auto means the hypervisor is active. Either you have not uninstalled Hyper-V or the uninstall did not work properly.

What happens if you manually set hypervisorlaunchtype to off?

[MIRKOSOFT]

I opened cmdline and tried command set of bcdedit - never success.
I mean value is boolean and turning off is 0.
But now I'm not sure - boolean cannot have value Auto...if is it meaning other than ON...
What a type it is?

Miro

[BillG]

The command is bcdedit /set {current} hypervisorlaunchtype off

[MIRKOSOFT]

Sadly didn't help.
Is else anything to do, or only reinstall?

Miro

[MIRKOSOFT]

For to be sure - I did reboot...

[BillG]

Then your problems have nothing to do with Hyper-V. If the hypervisor does not load, VirtualBox should run normally under Windows.

I have this morning disabled the hypervisor on my Windows 10 Pro Hyper-V host and reinstalled VirtualBox. It runs perfectly.