10,861
edits
Changes
Jump to navigation
Jump to search
→Hyper-V feature conflict issue: I tested it myself and it's still giving error if you try to launch VM with VT-x even with latest vmware, Windows OS and WHP windows feature.
There was a major change in VMware 16.x in how virtual graphics were handled (sandboxed) and it also added support for DX11 in Windows VMs. But due to these changes users reported lots of crashes lately especially with "3D Acceleration". For more information about these type of errors see [https://communities.vmware.com/t5/VMware-Workstation-Pro/ISBRendererComm-Lost-connection-to-mksSandbox-and-MKS/td-p/2838888 this thread].
===<s>Hyper-V feature conflict issue</s>===
<s>[https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v Many third-party Type 2 virtualization applications don't work together with Hyper-V feature from 'Control Panel/Windows Features']. Affected applications include "VMware Workstation" and "VirtualBox". These applications might not start virtual machines, or they may fall back to a slower, emulated mode ('''no''' VT-x and nested paging etc.)</s>
Even though some reports consider this issue fixed via [https://www.ubackup.com/enterprise-backup/vmware-workstation-and-hyper-v-are-not-compatible.html Recent recent updates (with VMware 15.5.6 and Windows 10 20H1) this issue solved], user reports shows that it's still there.
==See also==
