Distinguish a Hyper-V heartbeat from a graceful guest shutdown

Source facts

The Hyper-V heartbeat service reports to the host that the guest operating system is installed and has booted; disabling it limits that host-side signal. The guest-shutdown service lets the host request an orderly shutdown inside the VM. Microsoft warns that, without that service, host-triggered shutdowns become hard power-offs with possible data loss or corruption. Microsoft Learn.

Applicability

Identify which host-side observation is being used to assess the guest and which mechanism an operator intends to use for shutdown. Keep operating-system heartbeat, application readiness, and successful shutdown as separate acceptance results. Review workload-specific handling before testing.

DSE recommendation

Update the operations runbook so each action names its intended integration service and expected guest behavior. Ask the application owner to define the transaction that demonstrates readiness after startup. For shutdown testing, schedule an approved disposable or recoverable workload and record the expected orderly sequence. Do not use a positive heartbeat as the sole evidence that an application can safely be stopped.

Verification

Observe the heartbeat state after the test VM starts, then verify the application independently. Request an approved graceful shutdown and retain guest and host observations showing how it completed. Investigate absent integration-service responses before substituting a forced power action. Record the actual service state and any exception.

Official references

Microsoft Learn: Hyper-V Integration Services. Source reviewed September 8, 2026.