While this is supposed to allow 3rd party virtualization to access the hardware virtualization on the host, it doesn’t seem to work for either Workstation or VirtualBox. Please note that removing Hyper-V could affect the functionality of other features of Windows 10 such as Docker. Go to Control Panel–> Programs and Features, select Turn Windows features on or off.Įxpand Hyper-V, then expand Hyper-V Platform. (To re-enable Hyper-V, open an elevated prompt and enter: bcdedit /set hypervisorlaunchtype auto and reboot.) Remove Hyper-V Open an elevated command prompt or PowerShell (right-click and select Run as Administrator)Įnter: bcdedit /set hypervisorlaunchtype off Disable or Remove Hyper-V Disable Hyper-V Disabling or removing and a reboot should resolve this. This is great info, but what do you do about getting Workstation or VirtualBox to work?Īgain, the most likely culprit is Hyper-V. It is a feature only in Enterprise, Education, and IoT Enterprise versions of Windows 10. If you have Windows 10 Home or Pro you do not have Credential Guard enabled. If you’ve got Windows 10 Home, then you don’t have Hyper-V enabled. First, if you’ve got Hyper-V installed, that is the most likely culprit here and disabling or removing that feature should solve your issue.
It’s frustrating if you’re seeing the the message from VMware Workstation about Device Guard or Credential Guard or the similar one from VirtualBox.īut, there are a few thing to clarify before going off on a search for those devices.
0 kommentar(er)
