Run both Hyper-V and VMware on same Windows10

Techies who mostly use Hyper-V may require to run VMware to run Legacy Windows or Linux Operating Systems on the same Windows 10 PC. Moreover VMware Player is free for Non-Commercial Use.

I tried installing it on the pc with Hyper-V installed and got an error message: “VMware Player and Device/Credential Guard are not compatible. VMware Player can be run after disabling Device/Credential Guard. Please visit for more details”.

The above link opens the VMware Article but doesn’t show any major steps to resolve it. I found a lot of users on internet facing the same issue. Let’s quickly go ahead and see the fix by following below easy steps:

1) Disable Credential Guard using Group Policy settings:

On the host operating system, click Start > Run, type gpedit.msc, and click Ok.

The Local Group Policy Editor will open. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security. Select Disabled – Apply – Ok.

2) Go to Control Panel > Programs & Features > Turn Windows features on or off to Uninstall Hyper-V.

3) Select Do not Restart.

4) Delete the related EFI variables by launching a command prompt on the host machine using an Administrator account and run these commands:


The above command will show the Volume Names assigned. Look for the volume Guid showing  *** NO MOUNT POINTS ***.

mountvol X: \\?\Volume{00091e78-0000-0000-0000-100000000000}\

Note: \\?\Volume{00091e78-0000-0000-0000-100000000000}\” is the Guid of No Mount Points from Mountvol command.

XCopy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d

Note: Make sure X: should not be used with any drives.

Restart the host machine (Main machine on which Vmware & Hyper V will be running).

During the reboot, you will be prompted to accept Disable Device Guard and Credential Guard. Proceed with Yes.

After reboot, disable Hyper-V Hypervisor by running the below command in the command prompt with admin rights:

bcdedit /set hypervisorlaunchtype off

After Reboot, try opening Vmware and it should open successfully.

Note: Hyper-v is a type 1 hypervisor and Vmware is type 2. They cannot coexist (on any OS) at the same time. One has to be turned off in order for other Virtualization platform to function.

Use VmWare and if you need Hyper V back without loosing any of your old VM’s, follow the below two steps:

a) Try re-installing VMWare from Control Panel – Programs & Features – Turn Windows Features On or Off (left pane) – Select Hyper V.

b) Enable Hyper-V Hypervisor  from the command prompt with admin rights:

bcdedit /set hypervisorlaunchtype auto

Reboot the host machine and you will find both Hyper V running fine, however Vmware would not work.

Remember only one will work at a single point of time.Thanks a ton for reading my blog, don’t leave without mentioning your comments. Any friend facing an issue following the above steps, kindly reach out to me at ajey@localhost. Please do Subscribe our Youtube Channel.

Ajey Kumar Gupta
(Exchange Admin)

Must Read: Fix Ads.txt Earnings warning message in Google AD Sense with proof

Subscribe Us


Total Page Visits: 7740 - Today Page Visits: 1

Add a Comment

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.