Windows Server 2022 — Performance Monitor counters missing after server role install — 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

Performance Monitor counters missing after server role install 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 monitoring subsystem is in use, typically following configuration drift or recent updates.

typeperf -q | findstr /I 'memory'
Get-CimInstance Win32_PerfRawData_PerfOS_Memory

Root Cause Analysis

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

Get-Counter -Counter 'Processor(_Total)% Processor Time' -SampleInterval 2 -MaxSamples 5
lodctr /q:Memory

Step-by-Step Diagnosis

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

lodctr /q
Get-WinEvent -LogName 'Microsoft-Windows-Diagnosis-PLA/Operational' -MaxEvents 30

Solution — Primary Fix

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

lodctr /r
winmgmt /resyncperf
Restart-Service WinMgmt -Force
lodctr /e:Memory

Solution — Alternative Approaches

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

lodctr /R C:WindowsSystem32PerfStringBackup.ini
New-PerformanceCounterCategory -CategoryName 'CustomCounters' -CategoryType SingleInstance

Verification & Acceptance Criteria

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

Get-Counter -Counter 'MemoryAvailable MBytes'
typeperf 'Processor(_Total)% Processor Time' -sc 3

Rollback Plan

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

lodctr /s:C:BackupPerfStringBackup.ini
Restart-Service WinMgmt

Prevention & Hardening

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

Export-Counter -Path C:Logsbaseline.blg -InputObject (Get-Counter -ListSet * | Get-Counter)
New-ScheduledTask -Action (New-ScheduledTaskAction -Execute 'lodctr.exe' -Argument '/q > C:Logscounters.log')

Related Errors & Cross-Refs

Related: other monitoring 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.