VMware Workstation Device Credential Guard
Recently someone asked me why are they not able to open up a converted VM using VMware vCenter Converter Standalone which was migrated from Hyper-V Gen 2 VM running on their Windows 10 machine with VMware Workstation.
The error they hit was something that looks like below to Device/Credential Guard issue. Do note that this does not happen on VMware Fusion on Mac OS. You will know why later.
If you follow the KB, it is meant for Workstation 12 and below workaround. What if you are running something higher?
Typically this happens on Windows 10 machine and if you are on a joined domain, this is likely unable to be resolved if your Group Policy turns on Device/Credential Guard.
Let's understand what is this Device/Credential Guard. What this is doing is, it is running another layer of a hypervisor, in this case, Hyper-V on your Windows 10. In such, VMware workstation is unable to run any virtual machines are your machine is already been abstracted by another virtualization engine.
So if your machine is not Group Policy, what you can do is to check this setting on your Windows 10 machine to make sure it is turned off Memory integrity under Core isolation. This can be found in your Windows Settings, Security, Device Security.
The error they hit was something that looks like below to Device/Credential Guard issue. Do note that this does not happen on VMware Fusion on Mac OS. You will know why later.
If you follow the KB, it is meant for Workstation 12 and below workaround. What if you are running something higher?
Typically this happens on Windows 10 machine and if you are on a joined domain, this is likely unable to be resolved if your Group Policy turns on Device/Credential Guard.
Let's understand what is this Device/Credential Guard. What this is doing is, it is running another layer of a hypervisor, in this case, Hyper-V on your Windows 10. In such, VMware workstation is unable to run any virtual machines are your machine is already been abstracted by another virtualization engine.
So if your machine is not Group Policy, what you can do is to check this setting on your Windows 10 machine to make sure it is turned off Memory integrity under Core isolation. This can be found in your Windows Settings, Security, Device Security.
Once that is turned off, you will need to restart your machine and VMware workstation should run as per normal.
Comments