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

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials


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.


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.


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


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


See the terminology that Microsoft uses to describe software updates.