Windows Server / Hyper-V & Failover Clustering
Distinguish a Hyper-V VM state problem from a guest application failure
A virtual machine can be running while its guest OS or application is unavailable. Capture host-side state before cycling power.
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-VM -Name 'APP01' | Select-Object Name, State, Status, Uptime, CPUUsage, MemoryAssignedRead the result
With Hyper-V tools on the intended host, this shows VM state and summary metrics. Running does not prove guest responsiveness or application readiness.
Resolve and verify
Compare the host state with console access, heartbeat and guest logs. Repair the failing layer and validate the business service rather than only the power state.
Before changing production
Do not turn off a VM as a first test; abrupt power loss can interrupt writes and require recovery.