Live migration fails when you perform a live migration of a Hyper-V virtual machine in Windows Server 2008 R2

When you try to perform a live migration of a Hyper-V virtual machine in Windows Server 2008 R2, the live migration may fail. Additionally, an event that resembles the following is logged in the event log on the source node:

Log Name: System
Source:        Microsoft-Windows-Hyper-V-High-Availability
Event ID:      21502
Level:         Error
'VMname' live migration did not succeed at the source.

'VMname' failed to migrate. (Virtual machine ID F42A67DF-E912-4FC7-A867-802ADDE5E0D6)

The request for a live migration of the Virtual Machine failed because of an unsupported protocol version at the target host (Virtual Machine ID F42A67DF-E912-4FC7-A867-802ADDE5E0D6).

Note The virtual machine ID in this example is just for your reference. When this issue occurs, the ID is different.
This issue occurs because the internal time-out for pre-migration tasks is too short. Additionally, the system does not retry this step after the live migration fails.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760 1.22xxxWindows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_79714b37c0d80118a645ae0f9b5a22e1_31bf3856ad364e35_6.1.7601.22034_none_f531df350d79d8f7.manifest
File versionNot applicable
File size702
Date (UTC)29-Jun-2012
Time (UTC)16:27
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-clustering_31bf3856ad364e35_6.1.7601.22034_none_0acd18d21575e50a.manifest
File versionNot applicable
File size42,561
Date (UTC)29-Jun-2012
Time (UTC)10:41
PlatformNot applicable

Article ID: 2705759 - Last Review: 08/15/2012 07:53:00 - Revision: 1.0

Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Standard

  • kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2705759