How to Diagnose High CPU Usage on Windows Server
Applies to: Windows Server 2019, 2022 and 2025.
CPU diagnosis identifies the process and time window responsible for sustained pressure before an administrator restarts anything.
Monitoring should collect enough evidence to diagnose trends without overwhelming storage or exposing sensitive logs. Visit networkmanager.info.
Prerequisites
- Record complaint time.
- Use separate admin access.
- Preserve evidence.
- Know application ownership.
Procedure
Step 1: Measure total CPU
Collect multiple samples.
Get-Counter '\Processor(_Total)\% Processor Time' -SampleInterval 2 -MaxSamples 10Step 2: List processes
Sort cumulative CPU.
Get-Process | Sort CPU -Descending | Select -First 15 Name,Id,CPU,WorkingSetStep 3: Check queue
Measure scheduling pressure.
Get-Counter '\System\Processor Queue Length' -SampleInterval 2 -MaxSamples 10Step 4: Review interrupts
Use Performance Monitor to compare privileged, interrupt and DPC time.
Step 5: Correlate events
Check applications, tasks, backup and security scans.
Verification
Compare process evidence with total CPU over a representative period.
Get-Counter '\Processor(_Total)\% Processor Time','\System\Processor Queue Length' -SampleInterval 2 -MaxSamples 10Rollback
Diagnostics are read-only. Restart or terminate only through the application recovery plan.
Operational notes
A brief peak may be normal; sustained saturation and queue growth are stronger evidence.
Official references
Explore Netcloud24 Canada.
