Hyper-V guest may freeze when it is running failover cluster service together with shared VHDX in Windows Server 2012 R2
Content provided by Microsoft
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard
Windows Server 2012 R2 Essentials
Windows Server 2012 R2 Foundation
Windows 8.1 Enterprise
Windows 8.1 Pro
This article describes an issue that occurs when a Hyper-V guest is running failover cluster service together with a shared virtual hard disk (VHDX) in Windows Server 2012 R2. Before you install this update, see the Prerequisites section.
When this issue occurs, the Hyper-V guest is still registered as running in both Hyper-V manager and Failover Cluster manager. Therefore, the service in the cluster role doesn't failover to the passive guest cluster node correctly.
How to get this update
Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
For more information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
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:
6.3.960 0.18 xxx
Windows 8.1 and Windows Server 2012 R2
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 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.