Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Live migration of virtual machine to another host fails on a Windows Server 2012 R2-based Hyper-V host server


View products that this article applies to.

This article describes an issue that occurs when the live migration of a virtual machine to another host fails on a Windows Server 2012 R2 Hyper-V host server. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top


Resolution

To resolve this issue, we have released a hotfix. Even though this issue has been observed only in Windows Server 2012 R2, the hotfix also applies to Windows 8.1 and Windows RT 8.1.

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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 this specific problem.

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, submit a request to 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.


Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to 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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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.3.960 0.16 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
    6.3.960 0.17xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Winmgmt.exe6.3.9600.1741579,36029-Oct-201400:46x86
Wmiaprpl.dll6.3.9600.1741593,69629-Oct-201400:58x86
Wmisvc.dll6.3.9600.17818185,85602-May-201523:21x86
Wmiprov.dll6.3.9600.17818169,47202-May-201523:22x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Winmgmt.exe6.3.9600.1741581,40829-Oct-201400:57x64
Wmiaprpl.dll6.3.9600.17415133,12029-Oct-201401:18x64
Wmisvc.dll6.3.9600.17818230,40003-May-201500:40x64
Wmiprov.dll6.3.9600.17818228,35203-May-201500:40x64
Winmgmt.exe6.3.9600.1741579,36029-Oct-201400:46x86
Wmiaprpl.dll6.3.9600.1741593,69629-Oct-201400:58x86
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Winmgmt.exe6.3.9600.1638478,33622-Aug-201301:55Not applicable
Wmiaprpl.dll6.3.9600.1638498,81622-Aug-201302:12Not applicable
Wmisvc.dll6.3.9600.17818173,05602-May-201522:31Not applicable
Wmiprov.dll6.3.9600.17818161,79202-May-201522:31Not applicable

Additional file information

Additional file information for Windows 8.1 and Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_0c7d3c23ebf86e0e7c9d4e6763d206d8_31bf3856ad364e35_6.3.9600.17818_none_7cdcc0c671837f5a.manifest
File versionNot applicable
File size700
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameX86_dc849443b063a426a80b2d836521e97b_31bf3856ad364e35_6.3.9600.17818_none_281f7baa61e2e71a.manifest
File versionNot applicable
File size704
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameX86_microsoft-windows-wmi-core-svc_31bf3856ad364e35_6.3.9600.17818_none_35a223a9124e60f5.manifest
File versionNot applicable
File size10,946
Date (UTC)03-May-2015
Time (UTC)06:41
PlatformNot applicable
File nameX86_microsoft-windows-wmi-wdm-provider_31bf3856ad364e35_6.3.9600.17818_none_0f2233de7d6cf3e7.manifest
File versionNot applicable
File size5,578
Date (UTC)03-May-2015
Time (UTC)01:15
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_9a9f946d318d0551ca5cb47fb677ea7d_31bf3856ad364e35_6.3.9600.17818_none_a77f6dfc0b8e0695.manifest
File versionNot applicable
File size708
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameAmd64_b3ce6d7e6cd1ace973eb1a0dad3bf33d_31bf3856ad364e35_6.3.9600.17818_none_7e26617853216e04.manifest
File versionNot applicable
File size704
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameAmd64_c4ceab99c3aa92fd1102897dd99c3db2_31bf3856ad364e35_6.3.9600.17818_none_43877e484017ef73.manifest
File versionNot applicable
File size704
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameAmd64_microsoft-windows-wmi-core-svc_31bf3856ad364e35_6.3.9600.17818_none_91c0bf2ccaabd22b.manifest
File versionNot applicable
File size10,966
Date (UTC)03-May-2015
Time (UTC)06:44
PlatformNot applicable
File nameAmd64_microsoft-windows-wmi-wdm-provider_31bf3856ad364e35_6.3.9600.17818_none_6b40cf6235ca651d.manifest
File versionNot applicable
File size5,582
Date (UTC)03-May-2015
Time (UTC)02:56
PlatformNot applicable
File nameWow64_microsoft-windows-wmi-core-svc_31bf3856ad364e35_6.3.9600.17818_none_9c15697eff0c9426.manifest
File versionNot applicable
File size7,412
Date (UTC)03-May-2015
Time (UTC)06:44
PlatformNot applicable
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_61f864f23ed9a731e64cb896e8a0e009_31bf3856ad364e35_6.3.9600.17818_none_23da4be28cba5a67.manifest
File versionNot applicable
File size700
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameArm_cd137a54cbc4f522308fdd36a077ee0d_31bf3856ad364e35_6.3.9600.17818_none_3f0f0aaf279afcc2.manifest
File versionNot applicable
File size704
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameArm_microsoft-windows-wmi-core-svc_31bf3856ad364e35_6.3.9600.17818_none_35a49601124b7fbb.manifest
File versionNot applicable
File size10,946
Date (UTC)03-May-2015
Time (UTC)06:36
PlatformNot applicable
File nameArm_microsoft-windows-wmi-wdm-provider_31bf3856ad364e35_6.3.9600.17818_none_0f24a6367d6a12ad.manifest
File versionNot applicable
File size5,578
Date (UTC)02-May-2015
Time (UTC)23:59
PlatformNot applicable

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

This issue occurs because the old World Wide Port Name (WWPN) is not deleted from the Virtual Fibre Channel (VFC) of the source Hyper-V host server. This is caused by a known issue in Windows Management Instrumentation (WMI) in which the host bus adapter (HBA) driver never receives the corresponding WMI call.

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3049443
Revision : 1
Created on : 1/7/2017
Published on : 6/11/2015
Exists online : False
Views : 245