You can indeed run Windows Sandbox and VMWare together (or any additional hypervisor). First, you have to create a replica of your active boot entry using BCDEdit but adding trailing text to its description to make sure it's easily identifiable. For example 'No Hyper-V.' TL;DR Open an elevated command-prompt and enter: Code: bcdedit /copy {current} /d “Windows 10 – No Hyper-V” This copies your current boot entry and creates an exact replica with the 'No Hyper-V' added to its description. Once that is complete, it will create a unique GUID that is bound to that boot entry and returns it to the console. Save this GUID and then set its hypervisorlaunchtype to 'off': Code: bcdedit /set {GUID} hypervisorlaunchtype off Then reboot your PC and you will enter the Windows Boot Manager where you select your previously created “Windows 10 – No Hyper-V” boot entry. To revert this process and disable the usage of Windows Sandbox and VMWare is much easier: just press the Windows key + R and enter 'msconfig' into the search bar. Select the 'Boot' tab and delete the 'Windows 10 - No Hyper-V' entry.
That's not running them together? That's disabling one hypervisor so the other can run. VMware can't run with HyperV enabled. Sure this is a decent solution to just disabling features and rebooting, but in the end it's not running them together.
iNFO https://forums.mydigitallife.net/posts/1554274 SHA1 https://forums.mydigitallife.net/posts/1554266 all infos @ MVS Checksums #1 post
New PUBLIC 1903/1909 updates (18362/3.449): https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-467#post-1556084