Windows Server 2022 — WDAC policy enforcement causes kernel driver load failures — 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

WDAC policy enforcement causes kernel driver load failures 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.

ConvertFrom-CIPolicy -XmlFilePath C:PoliciesWDAC.xml -BinaryFilePath C:PoliciesWDAC.cip
Get-CimInstance Win32_DeviceGuard | Select CodeIntegrityPolicyEnforcementStatus

Root Cause Analysis

The defect stems from misaligned wdac 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.

Set-RuleOption -FilePath C:PoliciesWDAC.xml -Option 3
New-CIPolicy -FilePath C:PoliciesWDAC.xml -Level Publisher

Step-by-Step Diagnosis

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

Get-WinEvent -LogName 'Microsoft-Windows-CodeIntegrity/Operational' | Where Id -in 3076,3077
Get-AppLockerFileInformation -EventLog -Logname 'Microsoft-Windows-CodeIntegrity/Operational' -EventType Audited

Solution — Primary Fix

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

$rules = New-CIPolicyRule -DriverFilePath 'C:WindowsSystem32driversdriver.sys' -Level FilePublisher
Merge-CIPolicy -PolicyPaths C:PoliciesWDAC.xml -Rules $rules -OutputFilePath C:PoliciesWDAC_New.xml
ConvertFrom-CIPolicy -XmlFilePath C:PoliciesWDAC_New.xml -BinaryFilePath C:WindowsSystem32CodeIntegritySiPolicy.p7b
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.

Set-RuleOption -FilePath C:PoliciesWDAC.xml -Option 3 -Delete
ConvertFrom-CIPolicy -XmlFilePath C:PoliciesWDAC.xml -BinaryFilePath C:WindowsSystem32CodeIntegritySiPolicy.p7b

Verification & Acceptance Criteria

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

Get-CimInstance Win32_DeviceGuard | Select UsermodeCodeIntegrityPolicyEnforcementStatus
Get-WinEvent -LogName 'Microsoft-Windows-CodeIntegrity/Operational' | Where Id -eq 3099

Rollback Plan

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

Remove-Item C:WindowsSystem32CodeIntegritySiPolicy.p7b -Force
Restart-Computer -Force

Prevention & Hardening

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

Set-RuleOption -FilePath C:PoliciesWDAC.xml -Option 11
New-ScheduledTask -Action (New-ScheduledTaskAction -Execute 'powershell.exe' -Argument 'Backup-WDACPolicy.ps1')

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.