How to use Windows Sandbox and VirtualBox VMs simultaneously
Many users recently reported on various forums they encountered issues when trying to use Windows Sandbox and VirtualBox VMs at the same time.
The severity of this issue is further backed by the fact that many users consider that:
Some of us upgraded for one reason and one reason only — Windows Sandbox. However, as someone who uses VirtualBox on a daily basis for a literal plethora of reasons, this update was a nightmare until quite recently.
After much research which involved visiting several useful threads, they found a viable solution.
Steps to run Windows Sandbox and VirtualBox VMs simultaneously on PC
This solution is more of a workaround and is in no way backed by any official sources, and has the following steps:
bcdedit /copy {current} /d “Windows 10 – No Hyper-V”
This will create a new boot entry that is an exact copy of your active boot entry, but without Hyper-V.
- Copy the GUID that was just issued you, and paste it somewhere safe, since losing it will just complicate things
- Take the new GUID and paste it withing the following command line and execute it:
bcdedit /set {[NEW_GUID]} hypervisorlaunchtype off
- Reboot your PC so that the changes can take effect
The difference now is that instead of just simply booting your Windows, you will enter the Windows Boot Manager.
- You now have to choose the No-Hyper-V option.
This is how you can properly configure Windows Sandbox [EASY STEPS]
Reverting these changes
In case you want to revert the changes, the steps needed to be taken are a whole lot simpler:
- Press the Windows Key + R
- Type in msconfig in the search box
- Proceed to the Boot Tab
- Find the “No Hyper-V” boot entry, select it and then click Delete.
This won’t delete the boot entry altogether, instead, it will make it so it no longer appears in the Windows Boot Manager as an option.
You may also want to check out this article on how to use VirtualBox on Windows 10 May 2019 Update: