Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Virtualization » Fix VMware Workstation and Credential Guard are not compatible

Fix VMware Workstation and Credential Guard are not compatible

Posted on 23/01/202425/05/2025 IT Expert By IT Expert No Comments on Fix VMware Workstation and Credential Guard are not compatible
Vmware-workstation-player-and-devicecredential-guard-not-compatible

The Credential Guard uses virtualization-based security to isolate secrets so that only privileged system software can access them. Unauthorized access to these secrets can lead to credential theft attacks, such as Pass-the-Hash or Pass-The-Ticket. In this article, we will learn how to fix VMware Workstation and Device/Credential Guard are not compatible with VMware Workstation. Please see How to disable side-channel mitigations on VMware Workstation, and How to install ESXi on VirtualBox.

Note: The steps described in this article also apply to VirtualBox and KVMs. Here is an article from Broadcom as referenced by Microsoft.

You may also want to see Enable or disable Windows Defender Credential Guard, How to fix VMware and HyperV are not compatible, and how to Protect Remote Desktop credentials with Windows Defender Remote Credential Guard or Restricted Admin Mode.

Why was the error “VMware Workstation and Device/Credential Guard not compatible” prompted?

At the time of writing this article. According to VMware, VMware Workstation 12.5 or later displays an error when you power on a virtual machine on Windows under the following conditions.

  • Credential Guard/Device Guard is enabled.
  • Windows Sandbox is enabled.
  • A Virtual machine platform, such as VirtualBox, is enabled.
  • When WSL2 is enabled.
  • When Hyper V is enabled.

Note, with the Virtual Machine Platform and Hyper Virtualization Platform. You may not not encounter any issues. This behaviour might not be the same for you. See this hyperlink to learn more about VBS.

Disable Hyper-V

Ensure you take a backup of your data. This ensures you have the system restore points as a safety measure.

Note: The following features would not work anymore once the Hyper-V is disabled

  • Credential Guard/Device Guard
  • Windows Sandbox
  • Virtual machine platform
  • WSL2
  • Hyper-V

Is Virtualization-based Security (VBS) enabled?

First, you have to verify if VBS is enabled.

To do this, open msinfo32/system information. Under System Summary on the Right-hand page, scroll down to Virtualization-based Security and ensure the Value is set to running as shown below.

Virtualization-based-Security

As you can see above. The value is set to running and we have to disable this.

Turn Off Hyper-V

As suggested by VMware, the steps below will help you resolve this issue. Launch Windows “Turn Windows features on or off” features.

Launch-Windows-features-On-or-Off

Make sure Hyper-v is not ticked. If it is Ticked, untick it and click “OK”.

Untick-Hyper-V-platform

As you can see below. The Windows Hypervisor Platform is unchecked.

HyperV-feature-removed

You will be required to restart your device to apply changes.

Reboot-1

Disable the Hypervisor launch Type

To do this, open the command prompt window as an administrator. Run “bcdedit /enum {current}”

hypervisorlaunchtype
As you can see above, this is set to auto currently.

Run “bcdedit /set hypervisorlaunchtype off” to disable hypervisor Close the command prompt after   executing the commands and restart the system.

Disabled-Hypervisorlaunchtype

We should be able to power on the Virtual Machine in Workstation now.

Can-now-access-VM-again

Turn off VBS

The below steps can be followed to turn off virtualization-based Security via GPO and Windows Registry.

Navigate to the key below in the left pane of Local Group Policy Editor.

 Computer Configuration\Administrative Templates\System\Device Guard

On the right-hand side, double-click on Turn off virtualization-based Security

turn-off-virtualization-based-Security

Double-click on “Turn On Virtualization Security”.

This is set to "Not Configured", Select "Disable" and click "Ok"
Disable-Virtualization-based-security

As shown below, the turn off virtualization based security has been disabled.

Disabled

Close the Group Policy Editor. Restart the system.

Disable via Windows Registry

In case you wish to try this via the Windows Registry. Please follow the steps below.

Open Registry Editor
Go to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > DeviceGuard
On the right-hand side, write a new key
a. Right Click > New > DWORD (32-bit) Value

b. Name this Value "EnableVirtualizationBasedSecurity"

By default, it should be 0, Double click, and confirm the value

4. Go to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Lsa
5. On the right-hand side, write a new key

a. Right Click > New > DWORD (32-bit) Value

b. Name this Value "LsaCfgFlags"

By default, it should be 0, Double click, and confirm the value

I hope you found this guide useful “Fix VMware Workstation and Device/Credential Guard are not compatible with VMware Workstation”. Please feel free to leave a comment below.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:Microsoft Windows, Windows 10, Windows 11, Windows Server 2016

Post navigation

Previous Post: How to disable side-channel mitigations on VMware Workstation
Next Post: How to Make Your Taskbar Completely Transparent on Windows 11

Related Posts

  • maxresdefault
    How to extend a VM Hard Disk on VMware Workstation Virtualization
  • Enable Nexted Virtualization on VirtualBox
    ESXi VMB 411 Halting: Virtualbox Nested VT-X/AMD-V greyed out Virtualization
  • proxmox ve 6.1 released
    Installing Proxmox VE: Fix Volume Group Creation Error Virtualization
  • Slide2 2
    Oracle VirtualBox: Installing Windows 11 without TPM Support Virtualization
  • 1723152 3cc3 2 750x405 1
    Cluster creation in Proxmox VE Virtualization
  • Windows Server 2019
    The virtual machine has terminated unexpectedly during startup with exit code 1 (1×0): Failed to open a session for the virtual machine Windows Server 2019 Virtualization

More Related Articles

maxresdefault How to extend a VM Hard Disk on VMware Workstation Virtualization
Enable Nexted Virtualization on VirtualBox ESXi VMB 411 Halting: Virtualbox Nested VT-X/AMD-V greyed out Virtualization
proxmox ve 6.1 released Installing Proxmox VE: Fix Volume Group Creation Error Virtualization
Slide2 2 Oracle VirtualBox: Installing Windows 11 without TPM Support Virtualization
1723152 3cc3 2 750x405 1 Cluster creation in Proxmox VE Virtualization
Windows Server 2019 The virtual machine has terminated unexpectedly during startup with exit code 1 (1×0): Failed to open a session for the virtual machine Windows Server 2019 Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • WSUS Post deployment Configuration Failed
    The schema version of the database is from a newer version of wsus Windows Server
  • 785509289 780x439
    Errors associated with Pleasant Password Password Manager
  • Password Migration to ICloud Keychain
    How to import your Chrome or Firefox passwords into your iCloud Keychain Mac
  • images copy
    HA-Proxy Configuration File: Copy Between Nodes on Proxmox VE Virtualization
  • Screenshot 1
    Fix SMB Freezes That Break Backups on Critical Linux Servers Network | Monitoring
  • Slide1 3
    Azure Virtual Networks: Preparing Azure and On-Premises Virtual Networks with Azure CLI Commands AWS/Azure/OpenShift
  • screenshot 2020 05 11 at 20.25.01
    How to remove (uninstall) a printer on a macOS Mac
  • fghj
    MDT deployment failed and Stuck at Command Prompt: Windows installation does not proceed via PXE boot Windows Server

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,804 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.