Windows Server / Hyper-V & Failover Clustering
Review virtual processor allocation before adding vCPUs
A slow VM may be limited by host contention, guest workload or storage rather than insufficient virtual processors.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-VMProcessor -VMName 'APP01'Read the result
The query shows processor allocation and scheduling-related settings. It does not measure host scheduler delay or identify the guest process using CPU.
Resolve and verify
Correlate host and guest CPU metrics over the same interval, then adjust workload or processor allocation through a tested capacity plan.
Before changing production
Adding vCPUs can worsen scheduling or licensing constraints. Do not equate allocated processor count with guaranteed physical capacity.