“You can’t (reasonably) expect the latest build of Windows 10 to play well with an ancient version of another manufacturer’s hypervisor – or vice-versa.” If you’ve never had a hyper-v-related component turned on, then never mind 🙂 But please let us know what you find. you don’t have to turn components off) but I haven’t gotten around to trying that. It’s possible that turning the hyper-v hypervisor stuff off with the bcdedit command is sufficient by itself (i.e. If you want to turn hyper-v stuff back on, you can use:

Then reboot (again) and try your vmware tests. If you find anything to turn off, you’ll probably have to reboot. YMMV, but it’s worth a shot with vmware if you don’t find a better idea.įirst, in the Turn Windows features on or off panel, turn off everything which uses hyper-v, including the hyper-v feature, the new windows sandbox, and everything with “guard” in the name. I did the following to get virtualbox guests working. I suspect that this problem would affect vmware as well. The new sandbox feature, in particular, uses hyper-v, and hyper-v components remain active even after you’ve turned the sandbox off again. Windows components which use hyper-v prevent virtualbox guests from starting in 1903.

I might mention that the incompatibility issue referred to is present in the latest version of VMware (V15) according to reports elsewhere on the Web. I have been testing Windows using the Insider program from within VMware for several years, and would like to continue doing so. The link suggests that this can be resolved by preventing Hyper-V from running (however, in my case, hyper-V is not enabled). Occasionally, VMware produces an error window indicating that “VMware workstation and Device/Credential Guard are not compatible …” and provides a link for further information. The only way to resolve the issue is to reboot the (Host) desktop PC. This results in an inability to pause, suspend, shut down or restart the guest OS (Windows Insider). Initially, Windows Insider opens and I am able to log in, and then about 3-5 minutes later Windows 10 Insider freezes, and about 30 seconds later the parts of VMware dedicated to the open virtual machine also freeze. Since upgrading to Windows 10 (Version 1903) I am unable to access Windows 10 Insider from within my VMware V12.5.9 virtual machine.

Vmware player for windows 7 32 bit