New
#1
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.
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.
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?
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
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
@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