\
Unfortunately, it appears that somewhere in the flux between WSL / Hyper-V and the Virtual Machine that Windows uses to protect your credentials I can no longer run VirtualBox.
I'm very, very frustrated by this;
I've been in the bios, in bcdedit, in optionalfeatures, services.msc and I still cannot for the life of me get this thing to work!!!
BIOS:
To start off; in the bios, all the virtualization settings are turned on...except the one that seems like it would prevent it from working:
I made sure that the following were turned on:
Except for this one, I left it off as it seems like it might cause VirtualBox not to work:
BOOT LOAD CONFIG
I made a copy of the bootload configuration with Batchfile
bcdedit /copy {current} /d "Windows 10 Hyper-V"
And this resulted in a uuid and so I changed the hypervisor setting to off: Batchfile
bcdedit /set {current} hypervisorlaunchtype Off
And now when I load the computer I get two configuration to choose from, the one at the top has hypervisorlaunchtype set to off, but it still doesn't work.
WSL
I read over here that you can't use VirtualBox and WSL at the same time, I'm not sure what to do about that, though I would like to use VirtualBox and switch back to WSL when needed even if it means a reboot. (That said, I'd also like not to loose the files I have in WSL).
(Also I probably need to know if I'm using WSL 2 or WSL...I'm thinking it's WSL 2)
Hyper-V
I also tried uninstalling / installing Hyper-V via optionalfeatures. Initially I thought maybe uninstalling it would allow me to use VirtualBox, but that is not the case.
What happens when I do try to run VirtualBox?
I get the following error message, even if I run it as administrator or with the Local Administrator Account Logged in:
services.msc
Also there is a VirtualBox service listed that I am unable to start:
And I get the following error after trying to start it:
Additional interesting things:
If I try to look up basic things like the processor and how much RAM I have installed I get nothing:
But in services WMI is running; I don't know which of these many things the issue stems from, but I just want to run my Virtualization; it used to be so simple; you installed it and it worked! Then Microsoft decided to make that difficult.
The only things I can see that seems to have something to do with this that I haven't played around with is the WSL issue and the Windows hidden VM that protects credentials and I don't know how to turn either of those off or disable them.
I uninstalled WSL 1 and rebooted, and now I get a different error message regardless of if I have booted using hypervisorlaunchtype Off or hypervisorlaunchtype Auto:
And I went back to services to see that the VBoxSDS services error is still timing out (in both states), just as above:
I don't know what else I can try to fix this...apart from installing Linux.
