Join Stack Overflow to learn, share knowledge, and build your career. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. 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 the link and went through the steps, on step 4 I need to mount a volume using "mountvol". I even created a partition with 2GB and still the same message.
The protections are hardware assisted, since the hypervisor is requesting the hardware treat those memory pages differently. From here, we now have a protected mode where we can run security sensitive operations. While this Trustlet-specific communication is allowed, having malicious code or users in the Host OS attempt to read or manipulate the data in VSM will be significantly harder than on a system without this configured, providing the security benefit.
This is to allow all of the standard calls to LSA to still succeed, powering on a vm in vmware workstation on windows 10 host where credential guard/device guard free d excellent legacy and backwards compatibility, even for services or capabilities that require direct communication with LSA. This means changing our VMM to run at user level instead of in privileged mode, as well modifying it to use the WHP APIs to manage the execution of a guest instead of using the underlying hardware directly.
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 Don't just run it verbatim.
This lists all of the entries with their ID's. Copy the relevant ID, and then remove it like so As mentioned in the comments, you powering on a vm in vmware workstation on windows 10 host where credential guard/device guard free d to do this from an elevated command prompt, not powershell.
In powershell the command will error. Like so I'm still not convinced that Hyper-V is The Thing for me, even with last year's Docker trials and tribulations and I guess you won't want to switch very frequently, so rather than creating a new boot and confirming the boot default or waiting out the timeout with every boot I switch on demand in the console in admin mode by.
Another reason for this post -- to save you some headache: You thought you switch Hyper-V on with the "on" argument again?
Too simple for MiRKoS. It's auto! Just download this script directly from Microsoft. For those who might be encountering this issue with recent changes to your computer involving Hyper-V, you'll need to disable it while using VMWare or VirtualBox.
They don't work together. You'll need to reboot after that. I've written a PowerShell script that will toggle this for you and confirm it with dialog boxes. It even self-elevates to Administrator using this technique so that you can just right click and run the script to quickly change your Hyper-V mode.
It could easily be modified to reboot for you as well, but I personally didn't want that to happen. Save this as hypervisor. I don't know why but version 3. After I restarted my laptop problem still persisted. I was looking for solution and finally I came across version 3.
Here you can find latest powershell script:. I also struggled a lot with this issue. The answers in this thread were helpful but were not enough to resolve my error. You will need to disable Hyper-V and Device guard like the other answers have suggested.
More info on that can be found in here. I am including the changes needed to be done in addition to the answers provided above. The link that finally helped me was this. My answer is going to summarize only the difference between the rest of the answers i. Disabling Hyper-V and Device guard and the following steps :. Important : If you manually remove these registry settings, make sure to delete them all.
If you don't remove them all, the device might go into BitLocker recovery. From an elevated command prompt powering on a vm in vmware workstation on windows 10 host where credential guard/device guard free d in admin modetype the following commands:. Alternatively, you can disable the virtualization-based security features to turn off Windows Defender Credential Guard.
As you may know, this is a joint project from both Microsoft and VMware. While trying docker I installed and enabled wsl2. After uninstalling wsl from control panel and disabling it from powershell my vmware started working again.
With the above in place you just type "hpvenb" [ hypervisor enabled at boot ], "hpvdis" [ hypervisor disabled at boot ] and "bcdl" [ boot configuration devices list ] commands to execute the on, off, list commands. Well Boys and Girls after reading through the release notes for build in the wee small hours of the night, I have found the change point that affects my VMware Workstation VM's causing them not to work, it is the Core Isolation settings under Device Security under windows security new name for windows defender page in settings.
By default it is turned on, however when I turned it off and restarted my pc all my VMware VM's resumed working correctly. I had the same problem. I had VMware Workstation Powering on a vm in vmware workstation on windows 10 host where credential guard/device guard free d VMware Guide said in this link.
If your Host has Windows 10 20H1 build If your Host has Windows 10 or earlier, disable Hyper-V on the host to resolve this issue. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 4 years, 9 months ago. Active 4 months ago. Viewed k times. My Questions: How can I mount the volume that is not empty even though it is? Nicholas K Gman Gman 2, 3 3 gold badges 22 22 silver badges 32 32 bronze badges. Add a comment. Powering on a vm in vmware workstation on windows 10 host where credential guard/device guard free d Oldest Votes.
How does VMware Workstation work before version What does this mean to you? My Windows 10 Anniversary Update is at version There's no need to disable Hyper-V this way, or to install any 3rd party utilities.
Hyper-V can be turned on and off as required simply using alternate boot options with the builtin bcdedit command see my answer.
The solution doesn't seem to work for Win10 Creators Update. I also needed to uninstall windows feature "Linux sub-system" and reboot to make this error go away. Show 13 more comments. When you restart, you'll then just see a menu with two options If you want to remove a boot entry again.
First, get a list of the current boot entries Note: Run commands in administrators command line, in PowerShell it does not work. This worked for me, but how can I rollback the action above? I'm updated my answer above. SomethingSomething You need to run the command from an elevated command prompt. Right click and choose "Run as administrator". Show 5 more comments. Have fun! It works, specially if you need to have both instead of uninstalling the whole Hyper-V Hypervisor.
I keep on switching between the two for playing around with both technologies. That's why I prefer this way. I needed to reboot to be able to run VM. This is the most simple and sweet solution, Thanks a lot. To make it super easy: Just download this script directly from Microsoft. Siddhant Rimal 1 1 gold badge 11 11 silver badges 27 27 bronze badges.
Sharpowski Sharpowski 6 6 silver badges 20 20 bronze badges. Would be more helpful if you provided information on how to properly use the script that you say to download. Every time someone posts a script for Powershell, they never explain properly how to use it.
