KB2855336 – WS2012 Update Rollup For July 2013

A number of people have reported here and on the TechNet forum that there is a problem with this update.  It appears to cause bluescreens of death on hosts that have NIC teams supporting VLAN tagging.  Please do not approve/install this update until further notice.

EDIT:

An alleged fix was included with an updated version of the July 2013 update rollup.

Microsoft has released another update rollup for July 2013 for Windows Server 2012.  There are a number of fixes included that are relevant to Hyper-V.  This update rollup is available through Windows Update: make sure you have WS2012 and Update Rollups enabled and deployed, and please use Cluster Aware Updating to update your clusters!

KB2847176: File system is recognized incorrectly after you extend a CSVFS volume on a Windows Server 2012-based cluster.

Assume that you run the Diskpart.exe command prompt utility to extend a Cluster Shared Volumes File System (CSVFS) volume on a Windows Server 2012-based cluster. The volume extends beyond the size limit of the file system. In this scenario, Disk Manager and Diskpart.exe recognize the file system as a RAW file system instead of as a CSVFS file system.

For example, assume that a file system that was formatted by using an 8 KB cluster size has a size limit of 32 TB. When you extend a CSVFS volume beyond 32 TB, Disk Manager and Diskpart.exe recognize the file system as a RAW file system.

KB2854362: Vmms.exe processes freeze on certain nodes in a Windows Server 2012-based Hyper-V failover cluster.

Assume that you deploy a Windows Server 2012-based Hyper-V failover cluster that is based on a scale-out file server cluster. When a failover starts, the Vmms.exe process freezes on some of the failover cluster nodes. Therefore, several virtual machines are in the offline state.

KB2845653: “0x0000000A” Stop error when you perform a live migration of a virtual machine on a Windows Server 2012-based cluster

Assume that you have a Windows Server 2012-based multiple-node cluster. You try to perform a live migration of a virtual machine that has a duplicated (cloned) MAC address. In this situation, the host computer crashes. Additionally, you receive the following Stop error message:

STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)

Notes

• This Stop error describes an IRQL_NOT_LESS_OR_EQUAL issue.
• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all “Stop 0x0000000A” errors are caused by this issue

KB727972: Cluster node freezes when you restart a computer in a Windows Server 2008 R2 or Windows Server 2012 environment.

Consider the following scenario:

• You deploy a failover cluster in a Windows Server 2008 R2 or Windows Server 2012 environment.
• You enable the Volume Shadow Copy Service on a cluster disk.
• You replace a host bus adapter (HBA) on a cluster node.
• You restart the cluster node.

In this scenario, the cluster node freezes.

KB853952: Active Directory database becomes corrupted when a Windows Server 2012-based Hyper-V host server crashes.

Assume that you have a Windows Server 2012-based virtualized domain controller on a Windows Server 2012-based Hyper-V host server. When the Hyper-V host server crashes or encounters a power outage, the Active Directory database may become corrupted.

This issue occurs because the guest system requests the Hyper-V server to turn off disk caching on a disk. However, the Hyper-V server misinterprets the request and keeps disk caching enabled.