Windows 10: DG Readiness Tool - Unable to Disable Device Guard

Paulo_RicardoAU · Mar 4, 2020

I am trying to disable Device Guard since it is preventing me from running my VMs in VMWare Workstation Player.

When I open a command window in the DGReadiness folder and type in 'DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot' all that happens is that the DG_Readiness_Tool_v3.6.ps1 script opens in a Notepad window. The script does not run.

Is there a solution to this problem?

Thanks

:)

Ramhound · Mar 4, 2020

VMware Workstation can be run after disabling Device/Credential Guard

I try to install windows sandbox in my windows 10 home
Click to expand...

Windows Sandbox cannot be enabled on Windows 10 Home. The workaround you most likely used, does not even work, and has never actually worked. However, when you attempted to enable Windows Sandbox, it also enabled Credential Guard and Device Guard.

The first thing you need to backup any critical files you cannot live without. Depending on the state of your system you might decide it's time to simply reinstall Windows 10 Home. An alternative is to upgrade to Windows 10 Professional so you can Enable Windows Sandbox then disable it properly. The following suggestion was written against an assumption that Windows Sandbox was properly enabled and not left in a broken state due to a workaround solution on Windows 10 Home.

Windows Security -->> Device Security -->> Core Isolation -->> Memory Integrity -->> Select Off

Since you are using Windows 10 Home you will have to install the group policy editor to perform next step.

Set Local Computer Policy ->> Computer Configuration ->> Administrative Templates ->> System - Device Guard ->> Turn on
Virtualization to Disabled

Be sure Enabled with UEFI lock is not enabled.

Download the Device Guard and Credential Guard Hardware Readiness Tool and run the following command as an Administrator.

DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot

You also need to disable both Hyper-V and Windows Sandbox. The following commands assume you are running Windows 10 Professional or Windows 10 Enterprise.

Dism /online /Enable-Feature /FeatureName:”Containers-DisposableClientVM” -All

Dism /online /Disable-Feature /FeatureName:”Containers-DisposableClientVM”

Dism /Online /Disable-Feature:Microsoft-Hyper-V

You should reboot your machine at this point

Click to expand...

Source:

Windows Sandbox Feature enables windows defender credential guard feature sets. Does not play well with VMware Workstation

Manage Windows Defender Credential Guard

VMware Player and Device/Credential Guard are not compatible

MultiformeIngegno · Mar 4, 2020

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.

Brink · Mar 4, 2020

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

Windows 10: DG Readiness Tool - Unable to Disable Device Guard

DG Readiness Tool - Unable to Disable Device Guard

DG Readiness Tool - Unable to Disable Device Guard

DG Readiness Tool - Unable to Disable Device Guard

DG Readiness Tool - Unable to Disable Device Guard - Similar Threads - Readiness Tool Unable

Disable DDoS Guard

Disabling Windows Device/Credential Guard in Windows 10 Home

diginnos dg-w10m

Windows 10 Device Guard and Credential Guard Demystified

Turn off Credential Guard or Device Guard

Turn off Credential Guard of Device Guard

How to disable "Device Guard"

Verify if Device Guard is Enabled or Disabled in Windows 10

Enable or Disable Device Guard in Windows 10

Users found this page by searching for:

dg readinesss

dg_readiness_tool not an admin

DG_Readiness_Tool