VMware refuses to run Windows 10


  1. Posts : 7,254
    Windows 10 Pro 64-bit
       #1

    VMware refuses to run Windows 10


    I have been trying to run Windows 10 on Vmware Player on the latest insider build but I keep running into this error:

    VMware refuses to run Windows 10-vmwareerror.png

    I have played about with Group Policy to change the status of Device Guard but the error still appears.
      My Computers


  2. Posts : 208
    Win 10
       #2

    swarfega said:
    I have been trying to run Windows 10 on Vmware Player on the latest insider build but I keep running into this error:

    VMware refuses to run Windows 10-vmwareerror.png

    I have played about with Group Policy to change the status of Device Guard but the error still appears.
    I ran into this yesterday trying to fix my copy/paste issue. What gave me that error was I tried to add a feature in win10 host "Virtual Machine platform" after adding that I got that error, so removed it and still got error.
    Searching around I tried GPE, that did not help, what helped was a BCDedit to disable device guard.
    let me try and find the exact line.

    https://docs.microsoft.com/en-us/win...l-guard-manage
    bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
    bcdedit /set vsmlaunchtype off

    The first line errored out but the second one was good after reboot.
      My Computer


  3. Posts : 7,254
    Windows 10 Pro 64-bit
    Thread Starter
       #3

    Hi Ed, thanks for the reply. I tried what you suggested and also on MIcrosoft's page, restarted but I am still getting that error.

    Two thoughts that have come to me so far are 1. redo the Windows 10 vm, 2. clean install host Windows.
      My Computers


  4. Posts : 208
    Win 10
       #4

    swarfega said:
    Hi Ed, thanks for the reply. I tried what you suggested and also on MIcrosoft's page, restarted but I am still getting that error.

    Two thoughts that have come to me so far are 1. redo the Windows 10 vm, 2. clean install host Windows.
    Hmm, did you run CMD in admin mode and after "bcdedit /set vsmlaunchtype off" did it say successful?
    Then reboot the host.
    Yes, A clean host install of the OS would put it back to stock settings but that is last resort IMO.
      My Computer


  5. Posts : 7,254
    Windows 10 Pro 64-bit
    Thread Starter
       #5

    Yea I did and it reported successful then I rebooted.

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

    one line or two?
      My Computers


  6. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #6

    Looks like 2, Nick. 2 separate bcdedit commands.

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

    bcdedit /set vsmlaunchtype off
      My Computers


  7. Posts : 17,661
    Windows 10 Pro
       #7

    swarfega said:
    I have been trying to run Windows 10 on Vmware Player on the latest insider build but I keep running into this error:.
    Device Guard has nothing to do with your issue. Your error message, although VMware has made it about as confusing and misleading as possible, tells that you have hypervisor enabled. It is required when running type 1 hypervisors like Hyper-V.

    To be able to run type 2 hypervisors like VMware or VirtualBox, you need to turn hypervisor off with following command in an elevated Command Prompt:

    bcdedit /set {current} hypervisorlaunchtype off

    Restart, you are now able to run virtual machines in VMware and VirtualBox.

    When hypervisor is turned off, and you want to turn it on in order to run Hyper-V virtual machines, enter following command in elevated Command Prompt:

    bcdedit /set {current} hypervisorlaunchtype auto

    Restart, you are now able to run virtual machines in Hyper-V, but not in VMware and VirtualBox.

    Hypervisor - Wikipedia

    Kari
      My Computer


  8. Posts : 7,254
    Windows 10 Pro 64-bit
    Thread Starter
       #8

    wow! Talk about confusing on VMware and Microsoft's part. I would never have guessed. Thanks @Kari. Thanks also go to @f14tomcat and @EdKiefer for the help.
      My Computers


  9. Posts : 11,247
    Windows / Linux : Arch Linux
       #9

    swarfega said:
    Hi Ed, thanks for the reply. I tried what you suggested and also on MIcrosoft's page, restarted but I am still getting that error.

    Two thoughts that have come to me so far are 1. redo the Windows 10 vm, 2. clean install host Windows.
    @swarfega

    This comes up if you have either enabled the Sandbox and / or HYPER-V.

    Disabling them again doesn't eliminate the error. I had only actually enabled the sandbox.

    the bcedit thing didn't work for me -- anyway a restore only took me 10 mins.

    The only way to get this to work (or at least as far as I've found) is to restore to a backup where you haven't enabled sandbox or hyper-v.

    Otherwise it's a Windows (and VMware) re-install again. Even if you go through the Windows re-install again you can save the VM before doing it so after re-install you don't have to re-create the VM. Back it up simply with file explorer - copy the VM folder to an external drive etc.

    Cheers
    jimbo
      My Computer


  10. Posts : 65
    Windows 10 Pro 1909 18363.959
       #10
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:02.
Find Us




Windows 10 Forums