Windows Server 2022 — Credential Guard fails to enable due to incompatible drivers — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Credential Guard fails to enable due to incompatible drivers on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the security subsystem is in use, typically following configuration drift or recent updates.

DG_Readiness_Tool.ps1 -Capable
Get-WinEvent -LogName 'Microsoft-Windows-DeviceGuard/Operational' -MaxEvents 50

Root Cause Analysis

The defect stems from misaligned credential guard settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

msinfo32 /report C:Tempsysinfo.txt
Get-CimInstance Win32_DeviceGuard | Select SecurityServicesRunning,VirtualizationBasedSecurityStatus

Step-by-Step Diagnosis

Walk the security stack from configuration to runtime, collecting logs and counters that point at the failing component.

DG_Readiness_Tool.ps1 -Ready
Get-WinEvent -LogName 'Microsoft-Windows-Hyper-V-Hypervisor-Operational' | Select -First 20
driverquery /v | findstr /I 'unsigned'

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the credential guard component re-initialises cleanly.

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor -All -NoRestart
Set-ItemProperty -Path 'HKLM:SYSTEMCurrentControlSetControlDeviceGuard' -Name EnableVirtualizationBasedSecurity -Value 1 -Type DWord
Set-ItemProperty -Path 'HKLM:SYSTEMCurrentControlSetControlLsa' -Name LsaCfgFlags -Value 1 -Type DWord
Restart-Computer -Force

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

DG_Readiness_Tool.ps1 -Enable -CG
bcdedit /set hypervisorlaunchtype auto

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

Get-CimInstance Win32_DeviceGuard | Select -ExpandProperty SecurityServicesRunning
Get-WinEvent -LogName System | Where Id -eq 7026

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

DG_Readiness_Tool.ps1 -Disable -CG
bcdedit /set hypervisorlaunchtype off

Prevention & Hardening

Bake the validated credential guard configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Get-WindowsDriver -Online | Where Inbox -eq $false
Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindowsDeviceGuard' -Name RequirePlatformSecurityFeatures -Value 1

Related Errors & Cross-Refs

Related: other security failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.