Cannot run VM in VMWare on Windows 10 due to Hyper-V

Question

I have successfully installed VMWare Workstation 10 on my laptop running Windows 10. The virtualized system is CentOS.

Could install guest system and run it

I could successfully install the system and all, but after upgrading to Windows 10 Anniversary Update, I get this:

Removed Hyper-V

I have uninstalled everything from the system concerning Hyper-V. I removed it from my computer and restarted several times. No luck.

Solution 1

I had the same issue. Removing and disabling Hyper-V did not help. Turns out the problem was related to Device Guard (I have Windows 10 Enterprise). I found the answer here. But the gist of it is:

1. Download the Device Guard and Credential Guard hardware readiness tool

2. Run the tool in powershell with the correct execution policy):

   DG_Readiness_Tool_v3.2.ps1 -disable
   

3. Reboot

4. Make sure you have Hyper-V uninstalled and disabled:

   Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
   bcdedit /set hypervisorlaunchtype off
   

Solution 2

Windows 10 should have an option in the boot configuration data which determines whether Hyper-V starts during Windows startup (there is in Windows 8.1). So to disable Hyper-V from starting, in an administrator command prompt you type: bcdedit /set hypervisorlaunchtype off and reboot the computer. After that you can run VMs in Workstation.

To turn Hyper-V back on again, type in an administrator command prompt: bcdedit /set hypervisorlaunchtype auto and reboot the computer. (Source)

Solution 3

The solution to this problem is just disabling Device Guard. Below I show you how to disable it:

1. Open gpedit.msc

2. Go to Computer Configuration → Administrative Templates → System → Device Guard. On the right side double click to edit the properties of "Turn On Virtualization Based Security". Set the setting to "Disabled".

3. Open cmd as administrator and type the below commands:

   mountvol X: /s
   copy %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
   

After doing this you have to reboot and approve the changes with F3.

Solution 4

Quote from https://www.reddit.com/r/Windows10/comments/9zqbo0/running_both_hyperv_and_vmware_workstation/:

Hyper-v is a type 1 hypervisor, vmware is type 2. They cannot coexist (on any OS).

However, you can create a second boot entry so you can boot in hyper-v mode or vmware mode.

https://www.hanselman.com/blog/SwitchEasilyBetweenVirtualBoxAndHyperVWithABCDEditBootEntryInWindows81.aspx

C:\>bcdedit /copy {current} /d "No Hyper-V" 
The entry was successfully copied to {ff-23-113-824e-5c5144ea}. 

C:\>bcdedit /set {ff-23-113-824e-5c5144ea} hypervisorlaunchtype off 
The operation completed successfully.

View more solutions

Comments

[Vadzim]

Related: stackoverflow.com/questions/30496116/…

[Michael Hampton]

The downvote seems undeserved. This indeed solves the problem on Windows 10 Enterprise, and is otherwise a very hard to find solution. You should stick around during the reboot, though, as Windows will ask you to confirm you want to opt out.

[Barkermn01]

For step 4 I get Disable-WindowsOptionalFeature : A parameter cannot be found that matches parameter name 'All'.

[Andreas]

This is a good point. However, in most corporate cases, this group policy will also be forced by the company i.e. overwritten with the next GP update. Therefore, chances are rather low that this will work.

[Señor CMasMas]

These instructions suck.. even if they might work.

[Señor CMasMas]

This is what does (and has) always worked for me. I use a BCD boot option to switch between hypervisor on or off.

[Mery Ted]

There is a extra space in the last command. it should be Microsoft-Hyper-V–All

[Artemious]

For step 4 command must be: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

[ed22]

The only thing that worked after trying so many other things. Thank you.

[Edward]

This worked for me. Success after trying many other approaches.