Event ID 4096 and 0x800705B4: integration services time out during VM tasks

Fix it now

The host asked the guest to do something and the guest did not answer within the time allowed. 0x800705B4 is Win32 error 1460, a plain timeout with nothing more specific in it. The useful question is not why it timed out but what stopped the guest replying, and the integration service status usually says.

Get-VMIntegrationService -VMName 'Server1'
Get-VMIntegrationService -VMName 'Server1' | Where-Object { $_.SecondaryOperationalStatus -eq 'ProtocolMismatch' }

1. Read both the enabled flag and the status. A ProtocolMismatch on any service means the guest components are out of step with the host, and that is the whole answer.
2. Inside the guest, check the components are running: Get-Service -Name vmic*. Set any that should be automatic and are not, then start them.
3. Patch the guest. On Windows guests the integration components are serviced through Windows Update; on Linux guests they ship with current kernels, so a kernel update is the equivalent.
4. If only backups and production checkpoints fail, run vssadmin list writers inside the guest and look for a writer that is not in a stable state.

Control integration services from Hyper-V rather than from inside the guest. The matching guest service starts and stops automatically when you change its state on the host, so changing both by hand is how the two ends end up disagreeing.

If the operation completes, stop here. If every service reports healthy and it still times out, the next section covers what else makes a guest slow to answer.

Why it happens

Integration services are a matched pair: a component inside the guest and a provider on the host, talking over the virtual machine bus rather than over the network. Through that channel the host asks the guest to shut down cleanly, exchanges heartbeats, synchronises time, passes key and value data, offers a guest service interface for file copy, and, most importantly for backups, asks the guest to quiesce its storage. Microsoft names the six services exactly: Guest Service Interface, Heartbeat, Key-Value Pair Exchange, Shutdown, Time Synchronization and VSS.

None of those requests waits forever. Each has a timeout, and Win32 error 1460 is what comes back when one expires: this operation returned because the timeout period expired. That is all it says. A guest that is paging heavily, waiting on slow storage, or busy with its own scheduled work can miss the window and produce exactly this while looking perfectly healthy from the inside.

Backups and production checkpoints go further than a simple request. The host asks the guest’s shadow copy service to freeze every writer so the disks are consistent at a single moment. That involves every application writer registered inside the guest, so one writer in a failed state, a volume with too little free space, or a guest under load turns into a host-side timeout. The two ends of that conversation are logged separately, on the host and in the guest, and reading only one of them is how these get misdiagnosed.

Full reference

The six services, and what each one is for

Those are the names Enable-VMIntegrationService -Name accepts. A command written with a settings-page label instead of one of these fails outright.

Checking both ends

Get-VMIntegrationService -VMName 'Server1' | Format-Table Name, Enabled, PrimaryOperationalStatus, SecondaryOperationalStatus
Enable-VMIntegrationService -VMName 'Server1' -Name VSS

Get-Service -Name vmic* | Format-Table Name, DisplayName, Status, StartType
vssadmin list writers

The host view and the guest view have to agree. A service enabled on the host with its guest counterpart stopped produces a timeout that looks like a network problem, and a service running in the guest that the host has disabled is simply never asked to do anything. Microsoft’s guidance is to control these from Hyper-V and let the guest service follow, rather than managing both.

Keeping the components current

• Windows guests: the components arrive through Windows Update inside the guest. There is nothing to install from the host.
• Linux guests: the components are built into current kernels, so a kernel update is how you update them.
• A guest whose operating system is past end of support will not receive component updates again, and the mismatch widens with each host update.
• SecondaryOperationalStatus equal to ProtocolMismatch is the published way to find guests that have fallen behind, and it is worth running across the whole host rather than only against the machine that failed.

When backups are the only thing failing

1. Confirm VSS is enabled on the host for that machine and running in the guest.
2. Run vssadmin list writers in the guest and note any writer that is not stable.
3. Check free space on every volume in the guest, not just the system volume.
4. Check whether a third-party backup agent inside the guest is also taking a freeze at the same time.
5. Retry outside the backup window with nothing else running, to separate a broken writer from contention.
6. If it succeeds outside the window and fails inside it, the fix is scheduling, not configuration.

Raising the timeout is not the fix

The host-side timeouts are not intended as tuning knobs, and lengthening a freeze window makes the guest’s applications wait longer rather than making them healthier. A freeze is a genuine pause: applications inside the guest stop writing while it lasts. Extending it to accommodate a writer that takes too long trades a failed backup for a slower application, and the writer is still broken.

Every code this article covers

Confirm the fix worked

1. Get-VMIntegrationService shows every required service enabled with no ProtocolMismatch.
2. Get-Service -Name vmic* inside the guest shows the matching services running.
3. A production checkpoint of the machine completes, and removing it merges cleanly.
4. vssadmin list writers in the guest shows every writer stable with no errors.
5. The backup job that was failing completes and reports an application-consistent result.

Questions people ask about this