Check both ends of a Hyper-V integration service

Source facts

Hyper-V integration services coordinate functions between the host and guest operating systems; the individual services can be controlled separately. For a service to function fully, its host-side setting must be enabled and the corresponding service must run inside the guest. Microsoft recommends controlling integration services from Hyper-V. Outdated guest integration services can prevent features from working correctly; Microsoft documents checking their Windows version from inside the guest. Microsoft Learn.

Applicability

Use this review for one named integration feature, not as a reason to enable every available service. Identify the guest operating system and its documented service-management method. Separate the virtual machine setting from the service state observed within that guest.

DSE recommendation

Ask the workload owner which integration functions the guest requires. For a failing function, pair the host setting with the corresponding guest service and version evidence before changing either side. Keep unnecessary services outside the approved scope. If an update or service change is proposed, arrange a guest maintenance window and preserve the previous setting so the owner can reverse that individual change.

Verification

Exercise the selected function from its normal management path. Record the host enablement state, guest service state, guest integration version, and observed result together. If the result still fails, retain the two-sided evidence for investigation rather than repeatedly toggling unrelated integration features.

Official references

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