Windows Server / Hyper-V & Failover Clustering
Inspect Hyper-V heartbeat before assuming a guest is frozen
A missing heartbeat can reflect guest integration state, boot progress or a stalled OS. Inspect the integration service and guest evidence.
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-VMIntegrationService -VMName 'APP01'Read the result
The command reports integration components visible from the host. A heartbeat status is one signal and does not validate every guest service.
Resolve and verify
Compare heartbeat changes with VM uptime, console output and guest-side integration support. Restore the supported guest component or diagnose the actual hang.
Before changing production
Do not declare a VM healthy solely from heartbeat or reset it solely because one component reports a warning.