OmniGuard nsite.tech
← All articles
· 3 min read

Credential Guard is Enterprise-only — and what to do if you are not

A protection you cannot enable is not a finding you can fix. What Credential Guard does, who can actually run it, and the equivalent protections available on Home and Pro.

hardeningcredentialslicensing

Credential Guard is genuinely excellent. It uses virtualisation to isolate the part of Windows that holds authentication secrets, so that even code running with full administrator rights on the machine cannot read them out of memory.

It also requires Windows Enterprise or Education. On Home and Pro it will never start, no matter what policy you write.

The unsatisfiable finding

This causes a specific and frustrating failure mode in security tooling. A scanner checks whether Credential Guard is running, finds it is not, and reports a finding. You follow the remediation, write the policy, reboot — and it still is not running, because the edition does not license it.

The check never passes. The score never reaches 100. Nothing is wrong with the machine.

We shipped exactly this bug in our own product and had to fix it: the check now gates on the Windows edition, because a finding that cannot be satisfied is not a finding, it is a defect in the checker. Any scanner that reports Credential Guard on a Home machine without mentioning the edition is wasting your time.

Confirm what you have:

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' |
  Select-Object EditionID, ProductName

EditionID of Core is Home. Professional is Pro. Neither can run Credential Guard.

There is a second, independent signal in the LSA log: Licensed for Credential Guard: 0 means exactly what it says, and it is authoritative.

What you can run instead

The point of Credential Guard is to make stored credentials unreadable. Several other protections attack the same problem and are available on every edition.

Memory integrity (HVCI) is the big one. It runs on Home, uses the same virtualisation foundation, and protects the kernel from unsigned or malicious drivers. If you enable one thing from this article, make it this.

RunAsPPL runs LSASS as a Protected Process Light, which blocks ordinary processes — including administrative ones — from opening a handle to read its memory:

Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa' -Name RunAsPPL -Value 2 -Type DWord

A value of 2 enables it without a UEFI lock, so it remains reversible from Windows. Requires a reboot.

The LSASS ASR rule blocks credential-dumping attempts at the behavioural level and works on every edition.

Disable WDigest, which on older configurations caches credentials in a reversible form:

Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest' `
  -Name UseLogonCredential -Value 0 -Type DWord

Together these cover a substantial share of what Credential Guard defends against. Not all of it — nothing else provides the same hardware-isolated secret store — but enough that a Home machine is far from defenceless.

The wider lesson

Before chasing a hardening recommendation, check whether your platform can satisfy it. Edition, hardware, firmware and driver compatibility all gate real protections, and guidance written for enterprise fleets routinely assumes capabilities that consumer Windows does not have.

A security checklist that does not account for that produces a permanent list of failures, which trains people to ignore the list. That is worse than having no list at all.

OmniGuard puts this on autopilot — threats, network, Bluetooth and hardening in one console.
Download OmniGuard