Windows 10: Device and Crudential guard not Compatible

AlanZaharia · Jan 29, 2019

Hi,

So I got a Mac OS X 10.4 Mojave on a host computer with Windows 10 and I got an error that says "Device and Crudential guard are not compatible with VMware 15. Is there any way to fix it.

All the Best

:)

rdmueller · Jan 29, 2019

Device Credential Guard

When I install Docker on windows (with Hyper-V enabled) and try to run the VM-Ware player, I get the following error message:

VMware Workstation and Device/Credential Guard are not compatible.
VMware Workstation can be run after disabling Device/Credential Guard.
Click to expand...

It seems that is the standard way to handle this situation, but I try to be security aware Questions like VMware Player and Device/Credential Guard are not compatible and What are these VMWare instructions actually doing? (Disabling device guard and removing EFI variables) don't explain the background

So what is the Device/Credential Guard and what impact does it have if I disable it?

Brink · Jan 29, 2019

Credential Guard lab companion

If you have heard about Credential Guard in Windows Server 2016 (and in Windows 10), but do not have an environment to try it out, here is a lab environment we built for you to play.

Lab access

The link will lead you to a sign up page, after that, you will see the following labs listed for Windows Server 2016:

Windows Server 2016 labs

There are 3 exercises in the “Implementing Breach Resistance Security in Windows Server 2016”:

Credential Guard

Remote Credential Guard

Device Guard

This blogpost will walk you through the Credential Guard lab details.

After click on the link of Breach Resistance lab, you be required to sign in and then you can launch the lab:

Sign-in

Launch page

It takes a few minutes to create the VMs, and once it has done, you will see the following machines prepared:

Initialize

DC: domain controller, which is not used for this exercise.

SRV01 and SRV02: both are Windows Server 2016, and used for the lab exercise.

Lab exercise – Explained

The steps are listed in the Content section:

Content

This lab is structured to cover the following in sequence:

Understand how attackers can use the hash in memory to gain access to domain controllers

Configure Credential Guard

Verify the hash in memory is protected using Credential Guard

You can follow the steps listed under the content section to complete the lab, the intent of the blog, is to break the procedures into groups, to help you understand the exercise better.

Prep the hash

Lsass.exe is the process which handles user logon, it stores the user credential information in its memory. The memory is cleared when the machine starts up. In this lab environment, all the virtual machines start at the time lab launches, when you logon to the machine, you will only have the logon user credential information in memory. In order to demonstrate an attacker gaining user access using other account’s hash, the first part of the lab is to simulate a server which has been running for a while, different users had remotely or locally connected to it, therefore, lsass memory stored many different user credential information.
This is accomplished by step 1-8.

Retrieving credential hash

Mimikatz is a popular tool for retrieving lsass memory information. The tool has been copied to the lab machines, step 9-13 walk you through the process of dumping lsass memory using Mimikatz.

Pass the Hash

Pass the hash is a hacking technique that allows an attacker to authenticate by using the underlying NTLM, instead of specifying the user password. In step 14 to 24, you will extract LabAdmin hash from lsass using Mimikatz, and use the hash to open a PowerShell console, and perform a couple of operations using the LabAdmin privilege:

Add a user to the domain admin group

Open remote PowerShell connection to a domain controller

Both operations could not be performed by the logon user. But using the hash of the LabAdmin, an attacker will be able to do it using the information retrieve from Lsass memory.

Configure and verify Credential Guard

Step 25 to 36 illustrate the steps to configure credential guard, then verify its status using msinfo32.exe and PowerShell.

Step 37 to 43 goes further to use Mimikatz to show the hash in Lsass is now encrypted using Credential Guard.

More info

The exercise illustrated the benefit of Credential Guard in Windows Server 2016 as well as Windows 10. For more information, you can find here.
Click to expand...

Source: Credential Guard lab companion Datacenter and Private Cloud Security Blog

See also:

Enable or Disable Credential Guard in Windows 10 Windows 10 Security System Tutorials

Verify if Credential Guard is Enabled or Disabled in Windows 10 Windows 10 Security System Tutorials

MultiformeIngegno · Jan 29, 2019

Unable to activate Credential Guard on Windows 10: Unknown OS, OS Architecture failure

I am trying to enable Credential Guard on my copy of Windows 10 Pro v1809.
I downloaded the DG_Readiness_Tool_v3.5 from Microsoft's website, I run it on Powershell but this is the result:

###########################################################################
Readiness Tool Version 3.4 Release.
Tool to check if your device is capable to run Device Guard and Credential Guard.
###########################################################################
###########################################################################
OS and Hardware requirements for enabling Device Guard and Credential Guard
1. OS SKUs: Available only on these OS Skus - Enterprise, Server, Education, Enterprise IoT, Pro, and Home
2. Hardware: Recent hardware that supports virtualization extension with SLAT
To learn more please visit: https://aka.ms/dgwhcr
###########################################################################

Checking if the device is DG/CG Capable
====================== Step 1 Driver Compat ======================
Driver verifier already enabled
====================== Step 2 Secure boot present ======================
Secure Boot is present
====================== Step 3 MS UEFI HSTI tests ======================
Copying HSTITest.dll
HSTI Duple Count: 0
HSTI Blob size: 0
String:
HSTIStatus: False
HSTI is absent
====================== Step 4 OS Architecture ======================
Unknown architecture
====================== Step 5 Supported OS SKU ======================
This PC edition is Supported for DeviceGuard
====================== Step 6 Virtualization Firmware ======================
Virtualization firmware check passed
====================== Step 7 TPM version ======================
TPM 2.0 is present.
====================== Step 8 Secure MOR ======================
Secure MOR is absent
====================== Step 9 NX Protector ======================
NX Protector is absent
====================== Step 10 SMM Mitigation ======================
SMM Mitigation is absent
====================== End Check ======================
====================== Summary ======================
Machine is not Device Guard / Credential Guard compatible because of the following:
Unknown OS, OS Architecture failure..

HSTI is absent
Secure MOR is absent
NX Protector is absent
SMM Mitigation is absent
Click to expand...

Why does it say "Unknown OS, OS Architecture failure"?
I found this on the Microsoft forum but it doesn't have a solution.

Windows 10: Device and Crudential guard not Compatible

Device and Crudential guard not Compatible

Device and Crudential guard not Compatible

Device and Crudential guard not Compatible

Device and Crudential guard not Compatible - Similar Threads - Device Crudential guard

Windows 10 Device Guard and Credential Guard Demystified

VMware Workstation and Device/Credential Guard not compatible in Windows 10

Device/Credential Guard are not compatible.

Error: device credential guard are not compatible when launching VMware after installing...

VMware Player and Device/Credential Guard are not compatible

Device/Credential Guard are not Compatible - Virtualization

Windows 10 Device Guard and Credential Guard Demystified

Turn off Credential Guard or Device Guard

Turn off Credential Guard of Device Guard

Users found this page by searching for:

dgreadniess tool : Step 3 MS UEFI HSTI tests HSTIStatus: False HSTI validation failed

https://aka.ms/dgwhcr

hstistatus: False