Enable Credential Guard if your organization handles sensitive credentials and you use supported Windows versions; disable it if you rely on older drivers, unsupported hardware, or specific management tools that conflict with it. This article explains what Credential Guard does, how it works, how to decide, and how to enable or disable it safely.
What Is Credential Guard?
Credential Guard is a Windows security feature introduced in Windows 10 Enterprise and Windows Server 2016. It uses virtualization-based security (VBS) to isolate and protect domain credentials, such as NTLM password hashes and Kerberos tickets, from malware that runs with administrative privileges. By storing secrets in a separate virtualized environment that the operating system cannot directly access, Credential Guard makes it significantly harder for attackers to extract credentials from memory (e.g., via pass-the-hash or pass-the-ticket attacks).
It is not a standalone antivirus or endpoint detection tool; it is a mitigation that reduces the impact of credential theft if a system is compromised.
How Credential Guard Works
Credential Guard relies on two core technologies:
- Virtualization-Based Security (VBS): Uses the Hyper-V hypervisor to create an isolated region of memory where security processes run.
- Local Security Authority (LSA) Protection: The LSA process (lsass.exe) that handles logon and credential validation is split. One part runs in the normal kernel, another (called LSAIso.exe) runs inside the VBS isolation. The isolated part stores and protects secrets, and the normal part only requests operations, not the secrets themselves.
When a user logs on, the domain password hash or Kerberos ticket is stored in the isolated LSA. Even if an attacker gains SYSTEM privileges on the main OS, they cannot directly read that memory because the hypervisor enforces isolation. They would need to break the hypervisor itself, which is far harder than reading lsass.exe memory with a tool like Mimikatz.
Benefits of Enabling Credential Guard
- Reduces credential theft: Blocks many well-known attacks that dump password hashes or tickets from memory.
- Protects against pass-the-hash/ticket: Even if hashes are stolen, they cannot be replayed on other machines because the secrets are not accessible in plaintext.
- Lowers attack surface: Malware running as admin cannot directly interact with the isolated LSA.
- Recommended by Microsoft: It is part of the Microsoft Security Baseline for Windows 10/11 Enterprise and Windows Server.
Drawbacks and Compatibility Issues
Credential Guard is not free of costs. Common issues include:
- Hardware requirements: Needs a 64-bit CPU with virtualization extensions (Intel VT-x or AMD-V), a TPM 2.0 (recommended), UEFI Secure Boot, and at least 4 GB RAM (more for VBS overhead).
- Driver incompatibility: Some older drivers, especially those that interact with the security subsystem (e.g., certain VPN, smart card, or biometric drivers), may fail or crash.
- Management tool conflicts: Tools that directly modify or read LSA secrets (like some password managers or legacy domain join utilities) may stop working.
- Performance impact: VBS adds a small overhead, typically 1-5% CPU usage, which can matter on low-end hardware.
- No support for non-Microsoft hypervisors: If you use a third-party hypervisor (e.g., VMware, VirtualBox) on the same machine, Credential Guard may conflict because it requires Hyper-V to be active.
- Windows versions: Only Enterprise and Education editions (and Server) support it. Pro and Home do not have the feature.
How to Decide: Enable or Disable?
Ask these questions before making a change:
- Do you manage domain-joined computers? If yes, Credential Guard is strongly recommended.
- Are all drivers and applications compatible? Check with your vendors; run a pilot test.
- Does your hardware support VBS? Use the System Information tool (msinfo32) to check “Virtualization-based security” status.
- Do you use any legacy authentication protocols? NTLMv1 or other deprecated protocols may fail; Credential Guard does not support them.
- Is your IT team prepared to troubleshoot? If you lack expertise, disabling might be safer than enabling incorrectly.
If you are a home user on Windows Pro/Home, you cannot enable Credential Guard anyway. For enterprise environments, the default should be to enable unless a specific incompatibility forces you to disable.
How to Enable Credential Guard
Enabling requires administrative rights and a reboot. The recommended method is via Group Policy or the registry. Here are the steps for Windows 10/11 Enterprise:
- Open the Group Policy Management Console (gpmc.msc) or Local Group Policy Editor (gpedit.msc).
- Navigate to Computer Configuration > Administrative Templates > System > Device Guard (or “Credential Guard” in newer versions).
- Open the policy “Turn on Virtualization Based Security”.
- Set it to Enabled and choose “Enabled with UEFI lock” (recommended) or “Enabled without lock”.
- In the “Credential Guard” drop-down, select “Enabled with UEFI lock”.
- Apply the policy and reboot the machine.
Alternatively, you can use the registry: create a DWORD named Enabled under HKLM\SYSTEM\CurrentControlSet\Control\Lsa and set it to 1 (or 2 for UEFI lock). Then reboot.
After reboot, verify that Credential Guard is running by opening Task Manager > Performance and checking the “Virtualization-based security” line, or by running msinfo32 and looking for “Credential Guard” in the “Virtualization-based security” section.
How to Disable Credential Guard
Disabling is the reverse. You must remove the policy or registry key and reboot. If you used Group Policy, set the policy to Not Configured or Disabled. If you used the registry, delete the Enabled value. Then reboot.
Important: If you enabled with UEFI lock, you must first disable the lock by setting the policy to “Enabled without lock” and rebooting, then disable entirely. Otherwise, the UEFI lock will prevent you from turning it off.
After reboot, verify that Credential Guard is off by checking msinfo32 – it should no longer list “Credential Guard” as running.
Common Problems and Misconceptions
- “Credential Guard blocks all credential attacks” – No, it blocks many, but not all. For example, it does not protect against keyloggers or phishing.
- “It works on Windows 10 Home” – No, only Enterprise/Education and Server editions.
- “I can enable it on any PC” – No, hardware must support VBS and Secure Boot.
- “Disabling is as simple as unchecking a box” – Often, but UEFI lock can complicate it.
- “It causes blue screens” – Rare, but driver incompatibilities can cause crashes. Test in a pilot group first.
Frequently Asked Questions
Will Credential Guard slow down my computer?
Typically, the performance impact is minimal (1-5% CPU) because VBS runs in the background. On modern hardware with 8 GB RAM or more, you likely won’t notice it. On older or low-spec devices, it might be more noticeable, but the security benefit usually outweighs the cost.
Can I enable Credential Guard on Windows 10 Pro?
No, Credential Guard is only available in Enterprise and Education editions of Windows 10/11, and Windows Server. Pro versions do not include the feature. If you need it, you must upgrade to Enterprise.
Does Credential Guard work with third-party antivirus?
Yes, generally. Most antivirus products are compatible, but some that hook deeply into the LSA might conflict. Check with your vendor for compatibility statements. If you experience issues, you may need to disable Credential Guard or switch to a supported AV.
What happens if I disable Credential Guard?
Your system will revert to storing credentials in the normal LSA process, making them more vulnerable to memory-dumping attacks. If you are in a high-security environment, disabling is not recommended without a compensating control.
Can I enable Credential Guard on a virtual machine?
Yes, if the VM supports nested virtualization and has the necessary hardware features exposed. However, it is more complex and may not be fully supported by all hypervisors. Check your hypervisor documentation.
How do I check if Credential Guard is running?
Open System Information (msinfo32), scroll to “Virtualization-based security”, and look for “Credential Guard” in the “Services running” line. Alternatively, run the PowerShell command Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard and check the SecurityServicesRunning property.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Reliable Subaru vs New Honda Civic Cost
- Pokemon Bookmark Corner Designs & Pokemon GO DIY
- Forgotten Games That Created Your Favorite Genres
- Lexus vs Genesis Luxurious Compact SUV0.075 hp/lb
- Uber VW Robotaxi LA Launch Date
- Notebook vs Tablet: Which Saves You More Money?