This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can trysigning in orchanging directories.
Access to this page requires authorization. You can trychanging directories.
This article describes how to configure Credential Guard using Microsoft Intune, Group Policy, or the registry.
Starting in Windows 11, 22H2 and Windows Server 2025, Credential Guard isenabled by default on devices which meet the requirements.
System administrators can explicitlyenable ordisable Credential Guard using one of the methods described in this article. Explicitly configured values overwrite the default enablement state after a reboot.
If a device has Credential Guard explicitly turned off before updating to a newer version of Windows where Credential Guard is enabled by default, it will remain disabled even after the update.
Important
For information about known issues related to default enablement, seeCredential Guard: known issues.
Credential Guard should be enabled before a device is joined to a domain or before a domain user signs in for the first time. If Credential Guard is enabled after domain join, the user and device secrets may already be compromised.
To enable Credential Guard, you can use:
The following instructions provide details about how to configure your devices. Select the option that best suits your needs.
To configure devices with Microsoft Intune,create a Settings catalog policy and use the following settings:
| Category | Setting name | Value |
|---|---|---|
| Device Guard | Credential Guard | Select one of the options: -Enabled with UEFI lock -Enabled without lock |
Important
If you want to be able to turn off Credential Guard remotely, choose the optionEnabled without lock.
Assign the policy to a group that contains as members the devices or users that you want to configure.
Tip
You can also configure Credential Guard by using anaccount protection profile in endpoint security. For more information, seeAccount protection policy settings for endpoint security in Microsoft Intune.
Alternatively, you can configure devices using acustom policy with theDeviceGuard Policy CSP.
| Setting |
|---|
| Setting name: Turn On Virtualization Based Security OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceGuard/EnableVirtualizationBasedSecurityData type: int Value: 1 |
| Setting name: Credential Guard Configuration OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceGuard/LsaCfgFlagsData type: int Value: Enabled with UEFI lock: 1Enabled without lock: 2 |
Once the policy is applied, restart the device.
Checking Task Manager ifLsaIso.exe is running isn't a recommended method for determining whether Credential Guard is running. Instead, use one of the following methods:
You can useSystem Information to determine whether Credential Guard is running on a device.
msinfo32.exe, and then selectSystem InformationYou can use PowerShell to determine whether Credential Guard is running on a device. From an elevated PowerShell session, use the following command:
(Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard).SecurityServicesRunningThe command generates the following output:
Perform regular reviews of the devices that have Credential Guard enabled, using security audit policies or WMI queries.
Open the Event Viewer (eventvwr.exe) and go toWindows Logs\System and filter the event sources forWinInit:
Event ID
Description
13 (Information)
Credential Guard (LsaIso.exe) was started and will protect LSA credentials.14 (Information)
Credential Guard (LsaIso.exe) configuration: [**0x0** | **0x1** | **0x2**], **0**15 (Warning)
Credential Guard (LsaIso.exe) is configured but the secure kernel isn't running;continuing without Credential Guard.16 (Warning)
Credential Guard (LsaIso.exe) failed to launch: [error code]17
Error reading Credential Guard (LsaIso.exe) UEFI configuration: [error code]There are different options to disable Credential Guard. The option you choose depends on how Credential Guard is configured:
The following instructions provide details about how to configure your devices. Select the option that best suits your needs.
If Credential Guard is enabled via Intune and without UEFI Lock, disabling the same policy setting disables Credential Guard.
To configure devices with Microsoft Intune,create a Settings catalog policy and use the following settings:
| Category | Setting name | Value |
|---|---|---|
| Device Guard | Credential Guard | Disabled |
Assign the policy to a group that contains as members the devices or users that you want to configure.
Alternatively, you can configure devices using acustom policy with theDeviceGuard Policy CSP.
| Setting |
|---|
| Setting name: Credential Guard Configuration OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceGuard/LsaCfgFlagsData type: int Value: 0 |
Once the policy is applied, restart the device.
If Credential Guard is enabled with UEFI lock, follow this procedure since the settings are persisted in EFI (firmware) variables.
Note
This scenario requires physical presence at the machine to press a function key to accept the change.
Follow the steps inDisable Credential Guard
Delete the Credential Guard EFI variables by using bcdedit. From an elevated command prompt, type the following commands:
mountvol X: /scopy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Ybcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloaderbcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISObcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:mountvol X: /dRestart the device. Before the OS boots, a prompt appears notifying that UEFI was modified, and asking for confirmation. The prompt must be confirmed for the changes to persist.
From the host, you can disable Credential Guard for a virtual machine with the following command:
Set-VMSecurity -VMName <VMName> -VirtualizationBasedSecurityOptOut $trueWas this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?
Was this page helpful?
Want to try using Ask Learn to clarify or guide you through this topic?