Hyper-V storage migration failure and "ERROR_BAD_COMMAND" error in Windows Server 2012 R2 or Windows Server 2012

Symptoms
Assume that you install the Hyper-V role in Windows Server 2012 R2 or Windows Server 2012. In this situation, you may encounter one of the following issues:

Issue 1

Hyper-V storage migration fails when you try to migrate virtual hard disk (VHD) and configuration files to Cluster Shared Volumes (CSV) volumes in Windows Server 2012 R2. When this issue occurs, you receive an error message that looks something like this:

Migration did not succeed. Not enough disk space at '\'.

Note This issue also occurs, and has been fixed in Windows Server 2012. For detailed information, see hotfix 2913461.

Issue 2

Hyper-V replication stops with an ERROR_BAD_COMMAND error in Windows Server 2012 R2 or Windows Server 2012. The Hyper-V primary server treats this as an unrecoverable error. Therefore, the Hyper-V replication (HVR) enters a suspended state unexpectedly, and never sends delta again.

Note Only a manual restart of the replication could restore it.
Cause
Issue 1

This issue occurs because the target CSV volumes are incorrectly identified as being a system drive volume instead of multiple separate CSV volumes.

Issue 2

This issue occurs because the exclusive write lock for virtual hard disks (.vhd or .vhdx files) can't be obtained. Then, the VHD Miniport (VHDMP) driver indeed returns a STATUS_LOCK_NOT_GRANTED (C0000055) error. However, it's overridden by the STATUS_INVALID_DEVICE_STATE/ERROR_BAD_COMMAND error from another call to VHDMP.

How to obtain this hotfix

To fix this issue, we have released a hotfix for Windows Server 2012 R2 and Windows Server 2012.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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 don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix on Windows Server 2012 R2, you must install April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355).

Registry information

To use the hotfix in this package, you don't 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 doesn't replace a previously released hotfix.
More information

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 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's 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.17 xxxWindows Server 2012 R2RTMGDR
    6.3.960 0.18xxxWindows 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 for Windows Server 2012 R2" 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 aren't listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Rdvgpuinfo.dll6.3.9600.1739661,44008-Oct-201405:58x64
Vmms.exe6.3.9600.1800813,785,60008-Aug-201514:22x64

Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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's listed under "Windows 8/Windows Server 2012" 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:
    Version Product Milestone Service branch
    6.2.920 0.16xxxWindows Server 2012RTMGDR
    6.2.920 0.17xxxWindows Server 2012RTMGDR
    6.2.920 0.21xxxWindows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" 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 aren't listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Rdvgpuinfo.dll6.2.9200.1638460,41626-Jul-201201:28x64
Vmms.exe6.2.9200.1716411,204,60830-Oct-201403:01x64
Rdvgpuinfo.dll6.2.9200.1638460,41626-Jul-201201:28x64
Vmms.exe6.2.9200.2128111,205,63229-Oct-201403:29x64

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_0529e7d01a5d1f62f045935b4e160122_31bf3856ad364e35_6.3.9600.18008_none_2beebf73923e8693.manifest
File versionNot applicable
File size703
Date (UTC)08-Aug-2015
Time (UTC)23:00
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.3.9600.18008_none_27aeb4f1329f7dd1.manifest
File versionNot applicable
File size1,296,191
Date (UTC)08-Aug-2015
Time (UTC)23:00
PlatformNot applicable
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_124ca1ecac781f369314f3b053e3ead0_31bf3856ad364e35_6.2.9200.21282_none_c9f94e45bc6a88ce.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_1776f3184d9f9722486a382fb11b86c9_31bf3856ad364e35_6.2.9200.21282_none_6aab60e137e7faff.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_205afc4f85078e216f5eab3ab1c0c31d_31bf3856ad364e35_6.2.9200.21282_none_ebeafb6426bca34c.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_24e3e18ade351c9502d5c7709e524941_31bf3856ad364e35_6.2.9200.21282_none_c22262a4bd459efc.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_2c06736332e0a699e217ba8d1ff83a1f_31bf3856ad364e35_6.2.9200.21282_none_ceaa711e7616a752.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_2e1f158a5bb6a28741279bc4fb541be5_31bf3856ad364e35_6.2.9200.21282_none_3aaceaf3b2305b0b.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_324d35193946aa065b3106daad6383bc_31bf3856ad364e35_6.2.9200.21282_none_dc715b674706051e.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_35d74d03f69059d1bc3014d31939a119_31bf3856ad364e35_6.2.9200.21282_none_409bd056f89568ff.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_35df3cb6774e4b185e474c1d72e6ab1d_31bf3856ad364e35_6.2.9200.21282_none_02fc4759a05b889c.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_3da57dfd73d145b72ea2df2c5cc9a29b_31bf3856ad364e35_6.2.9200.21282_none_13572f6025816721.manifest
File versionNot applicable
File size703
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_42bf2a90027f370f80452aeb09fb7068_31bf3856ad364e35_6.2.9200.21282_none_0b719e11fea877ff.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_64bbb2ca251762dad7985be39a1872b0_31bf3856ad364e35_6.2.9200.21282_none_cd16717e7786ee04.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_6a23d356962dea7084ba86b0d375a5e3_31bf3856ad364e35_6.2.9200.21282_none_9a8d52f6746e3429.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_6bb718e8c6fe34c7fa90bc7bffd9dfd5_31bf3856ad364e35_6.2.9200.21282_none_5347642e585fc7ed.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_6cfc9d9fbdb131890f08f2655b17966c_31bf3856ad364e35_6.2.9200.21282_none_dec9dcdacbb568f1.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_7cb508ac8dbb8b03b3c161f17b824e18_31bf3856ad364e35_6.2.9200.21282_none_cfcbe95e3b4cd5ef.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_89819daafe0e8da1e67580b5bfef0de5_31bf3856ad364e35_6.2.9200.21282_none_83783eb13e5f57ad.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_acc89c004353a285112cff224f4e1556_31bf3856ad364e35_6.2.9200.21282_none_9c93cf9f86714d56.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_b7882c28c059ab0c16ff48a6254b4b79_31bf3856ad364e35_6.2.9200.21282_none_f98b997e15e377a9.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_b907b70e6bfe4fd5a88513a0635ee0d1_31bf3856ad364e35_6.2.9200.21282_none_a3f8b4cd6385c085.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_bdb0fdcf837914172032466f367dbec1_31bf3856ad364e35_6.2.9200.21282_none_5154d072f0efc2d4.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_d010b6ae2981babc913a0b570f3dc48a_31bf3856ad364e35_6.2.9200.21282_none_b580bc9aaecd9c57.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_d2c234ad1c384c8f0c9cde14ad7a99df_31bf3856ad364e35_6.2.9200.21282_none_1f6abc7bfb51f60a.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_e25c13c65010fc1a5e2e78455f13a224_31bf3856ad364e35_6.2.9200.21282_none_55f5104e24dfbccd.manifest
File versionNot applicable
File size711
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_f47cb1dc713120527e0116bfda7d642a_31bf3856ad364e35_6.2.9200.17164_none_fd978c2ec71c5a2f.manifest
File versionNot applicable
File size703
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.2.9200.17164_none_8f753448e8a0d324.manifest
File versionNot applicable
File size1,134,338
Date (UTC)31-Oct-2014
Time (UTC)19:46
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.2.9200.21282_none_8fe730a801d07822.manifest
File versionNot applicable
File size1,136,126
Date (UTC)31-Oct-2014
Time (UTC)19:46
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3012714 - Last Review: 09/08/2015 21:34:00 - Revision: 2.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Essentials, Windows Server 2012 Foundation

  • kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB3012714
Feedback