Virtual machines freeze at the "Stopping" state after you shut down the virtual machines in Windows Server 2012

Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 Standard More


Consider the following scenario:
  • You create some failover cluster nodes on computers that are running Windows Server 2012.
  • You have the Hyper-V server role installed on the cluster nodes.
  • You create virtual machines on one cluster node, and you configure the virtual machines as cluster resources.
  • You enable Quality of Service (QOS) on the virtual machines, and you set the QOS to the minimum allowed value.
  • You send lots of network traffic from the virtual machines to another cluster node.
  • After the virtual machines run for a while, you shut down the virtual machines.
In this scenario, one or more virtual machines freeze at the "Stopping" state. Therefore, you cannot perform any actions on the virtual machines. For example, you cannot perform a live migration or a backup.


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.


To apply this hotfix, you must be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to 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.


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 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_09203340dd44b40bb42a8ae9ff6e8eb3_31bf3856ad364e35_6.2.9200.20653_none_ff6a24046d6e3504.manifest
File versionNot applicable
File size708
Date (UTC)05-Mar-2013
Time (UTC)15:53
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.2.9200.20653_none_c27df0f922e74b56.manifest
File versionNot applicable
File size162,594
Date (UTC)05-Mar-2013
Time (UTC)15:53
PlatformNot applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.20653_none_bc584ad3942cc44a.manifest
File versionNot applicable
File size3,379
Date (UTC)05-Mar-2013
Time (UTC)15:53
PlatformNot applicable