Run Hyper-V and VMware virtual machines on Windows 10

I use Windows’ Hyper-V to run virtual machines for long time. Recently I need to run a VMware virtual machine to test something. I installed VMware Player, which is free for non-commercial usage. However, the virtual machine cannot started, with an error:

VMware Player and Device/Credential Guard are not compatible. VMware Player can be run after disabling Device/Credential Guard. Please visit http://www.wmware.com/go/turnoff_CG_DG for more details.

image

The link will redirect you to a document with many steps.

  1. Disable the group policy setting that was used to enable Credential Guard.

    1. On the host operating system, click Start > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.
    2. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.
    3. Select Disabled.
  2. Go to Control Panel > Uninstall a Program > Turn Windows features on or off to turn off 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:
    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
    Note: Ensure X is an unused drive, else change to another drive.
  5. Restart the host.
  6. Accept the prompt on the boot screen to disable Device Guard or Credential Guard.

Actually, this is a conflict that can be simply resolved by temporarily disabling Hyper-V hypervisor:

bcdedit /set hypervisorlaunchtype off

Restart is required. Apparently, the side effect is that Hyper-V virtual machines cannot be started after this:

image

And so is Docker:

image

To get Hyper-V back, just turn its hypervisor back on:

bcdedit /set hypervisorlaunchtype auto

25 Comments

  • https://stackoverflow.com/questions/30496116/how-to-disable-hyper-v-in-command-line

    you can chose at boot which one you want to use

    see answer from hfmanson

  • hyyyy
    <a href="http://nikepars.com/%D8%AB%D8%A8%D8%AA-%D8%B4%D8%B1%DA%A9%D8%AA/">ثبت شرکت</a>
    <a href="http://nikepars.com/%D8%AB%D8%A8%D8%AA-%D8%B4%D8%B1%DA%A9%D8%AA/">ثبت شرکت</a>
    <a href="http://nikepars.com/%D8%AB%D8%A8%D8%AA-%D8%B4%D8%B1%DA%A9%D8%AA/">ثبت شرکت</a>
    <a href="http://nikepars.com/%D8%AB%D8%A8%D8%AA-%D8%B4%D8%B1%DA%A9%D8%AA/">ثبت شرکت</a>
    <a href="http://nikepars.com/%D8%AB%D8%A8%D8%AA-%D8%B4%D8%B1%DA%A9%D8%AA/">ثبت شرکت</a>
    bybby

  • Thank you, I really like it, the article is very helpful

  • Resolveu meu problema... vlw!

  • Help a lot, thank you so much guys

  • Turning the hypervisor off will stop sandbox mode in Windows 10 1903.

  • Try running it in Oracle VirtualBox. That's what I did with mine and it ran fine without screwing around with any of this garbage. The one thing that did work for VMWare was the elevated CMD window command of 'bcdedit /set hypervisorlaunchtype off'. But this breaks WIndows 10 v1903 Sandbox capability.

    VMWare doesn't seem to be able to Dev their way out of this hole... Kick them to the curb and go Oracle.

  • Instead of uninstalling Hyper-v you can disable it in Powershell with this command: "bcdedit /set hypervisorlaunchtype off" If you ever want to reenable Hyper-v you can use "bcdedit /set hypervisorlaunchtype auto"

  • This fix worked for me... thanks! Very straight forward.

  • I struggled to disable device guard or credential guard. This solution is really helpful. Thanks for making it so easy.

  • The solution is good but everytime I switsh off my pc I have to fix it again. Every time!
    Any idea?

  • Same for me, Nicola. Don't persist on system restart

  • The problem with VirtualBox is that while it may work for now, it is an Unsupported Experimental Feature. It may or may not function with the next patch from MS, or next upgrade from Oracle.

    There is no real good way to get this to work at will, at this time. Hopefully, VMware will develop/offer VMware Workstation Pro 16 that solves this issue....but until they supply some upgrade, everyone is going to have to manually turn off/on things to get either Hyper-V or VMware to work.

  • Thank bro, it saved my day


  • Great trick! I was getting crazy trying to run a virtual machine on a Windows 10 Home host and it just wasn't working.

    VMware shows a message asking to disable Windows Defender while VirtualBox just don't run with no message.

    After disable Power Shell, Windows Virtual Platform and Hyper-V it's run now on VMware!

  • شركة تصميم مواقع وتطبيقات الجوال

  • Mounting the X: drive was the fix. Tried the other articles to no avail.

    Thank you very much!

  • Thank you so much!!!
    this is awesome

  • Thanks so much, very useful and clean solution!

  • Helped a lot.
    Thank you so much.

  • Thanks for this. Why couldn't VMware have this on the KB article?

  • I have been using this fix successfully for a while now on my company laptop to run virtualbox. Had to repeat the process now and then after updates. But now, after the windows 10 1903 update, I cant get virtualbox to run.
    Now, when starting the virtual machine, the laptop gets a BSOD with a stop code HYPERVISOR_ERROR

  • update:
    The fix I had been using, was actually the one listed above, refered to "the document with many steps"

    I did follow the link above all the way to the microsoft article. then I did (once again) apply the steps just as they was written at the microsoft webpage. The things to do in the command prompt are almost identical to the description above, but with some small changes.
    With these commands, it finally worked for me, after the following reboot:
    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
    bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
    mountvol X: /d

    bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
    bcdedit /set vsmlaunchtype off

  • Gracias. Funcionó perfectamente en mi caso. :)

  • Many thanks amyren. It worked for me. I appreciate a lot your help. Have a nice day,

Add a Comment

As it will appear on the website

Not displayed

Your website