Hyper-V Heartbeat failed to connect to virtual machine '%1' because the version does not match the version expected by Hyper-V ...

Hyper-V Heartbeat failed to connect to virtual machine '%1' because the version does not match the version expected by Hyper-V (Virtual machine ID %2). Framework version: %3; Message version: %4. To fix this problem, you must upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Hyper-V failed to start the virtual machine '%1' because it was unable to determine if replication was configured for this ... Hyper-V Guest Shutdown connected to virtual machine '%1', but the version does not match the version expected by Hyper-V ... Hyper-V Guest Shutdown failed to connect to virtual machine '%1' because the version does not match the version expected ... Hyper-V Heartbeat connected to virtual machine '%1', but the version does not match the version expected by Hyper-V (Virtual ... Hyper-V Heartbeat failed to connect to virtual machine '%1' because the version does not match the version expected by Hyper-V ... Hyper-V logical processor %2 exposes the following power management capabilities: Idle state type: %4 (%3 state(s)) Performance ... Hyper-V management tools were not found on the system. Creation and management of Virtual Machines will be disabled in Failover ... Hyper-V paused virtual machine '%1' because the Replica virtual machine was found to be failed over on the Replica server. ... Hyper-V prevented starting the virtual machine because replication is ongoing. The virtual machine can be started after performing ...