So I upgraded my lab workstation recently and it is running Windows 10 Professional. I installed VMware Workstation 16 PRO and it works fine. It is great for a lab, especially when you need to install a entire vSphere environment. This is because VMware Workstation is great at nested virtualization.<\/p>\n\n\n\n
My problem started when I installed Windows Sandbox environment on the physical Windows workstation. It created a slew of errors when trying to boot vm\u2019s that used the nested virtualization flags or hardware assisted virtualization flags. Errors upon errors pop up with the ultimate result of the vm failing to boot.<\/p>\n\n\n\n
I didn\u2019t want to uninstall Hyper-V or Windows Sandbox and the thought of uninstalling VMware Workstation never even entered my mind because frankly it is awesome. <\/p>\n\n\n\n
The Solution<\/span><\/strong> <\/p>\n\n\n\n Turn off the one you are not using. <\/p>\n\n\n\n To use VMware Workstation:<\/p>\n\n\n\n bcdedit \/set hypervisorlaunchtype off<\/p>\n\n\n\n If u want use hyper-v:<\/p>\n\n\n\n bcdedit \/set hypervisorlaunchtype auto<\/p>\n\n\n\n It is very important that you reboot after running either of these commands or it will not work.<\/p>\n\n\n\n I know this is not optimal but until VMware and Microsoft work out their differences it looks like we are the ones paying the price.<\/p>\n\n\n\n\n","protected":false},"excerpt":{"rendered":"