VMware Workstation and Device/Credential Guard are not compatible

前端 未结 13 1572
别跟我提以往
别跟我提以往 2020-12-22 15:10

I have been running VMware for the last year no problems, today I opened it up to start one of my VM and get an error message, see screen shot.

I did follow

13条回答
  •  自闭症患者
    2020-12-22 15:35

    There is a much better way to handle this issue. Rather than removing Hyper-V altogether, you just make alternate boot to temporarily disable it when you need to use VMWare. As shown here...

    http://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.
    

    note: The ID generated from the first command is what you use in the second one. Don't just run it verbatim.

    When you restart, you'll then just see a menu with two options...

    • Windows 10
    • No Hyper-V

    So using VMWare is then just a matter of rebooting and choosing the No Hyper-V option.

    If you want to remove a boot entry again. You can use the /delete option for bcdedit.

    First, get a list of the current boot entries...

    C:\>bcdedit /v
    

    This lists all of the entries with their ID's. Copy the relevant ID, and then remove it like so...

    C:\>bcdedit /delete {ff-23-113-824e-5c5144ea}
    

    As mentioned in the comments, you need to do this from an elevated command prompt, not powershell. In powershell the command will error.

    update: It is possible to run these commands in powershell, if the curly braces are escaped with backtick (`). Like so...

    C:\WINDOWS\system32> bcdedit /copy `{current`} /d "No Hyper-V"
    

提交回复
热议问题