Symptoms

This problem occurs when the Windows Management Instrumentation (WMI) service freezes on a node that has the quorum installed. In this situation, all other nodes restart their cluster services automatically, and during this process, the quorum moves to a node on which the WMI service is working. However, Failover Cluster Manager does not connect to the cluster from any node in Windows Server 2012 R2 or Windows Server 2012.

Cause

This problem occurs because, when the WMI service freezes on the node, the system leaks the mutex handle instead of closing the mutex handle.

Resolution

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Prerequisites

To install this hotfix, you must haveĀ April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2..

Registry information

To use the hotfix in this package, you do not 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 does not replace a previously released hotfix.

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 8.1 and 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 is 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:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

  • 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" 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.

For all supported x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.3.9600.17669

393,024

29-Jan-2015

12:53

x86

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.3.9600.17669

487,232

29-Jan-2015

12:57

x64

Netcfgx.dll

6.3.9600.17669

393,024

29-Jan-2015

12:53

x86

For all supported ARM-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.3.9600.17669

358,216

29-Jan-2015

12:48

Not applicable

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 is 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.21xxx

    Windows Server 2012

    RTM

    LDR

  • 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" 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.


For all supported x64-based versions of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.2.9200.21311

351,232

26-Nov-2014

23:36

x86

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1

File property

Value

File name

X86_5bcee83f24ae5e443ff36dcb2790ba39_31bf3856ad364e35_6.3.9600.17669_none_31badd815cf15207.manifest

File version

Not applicable

File size

710

Date (UTC)

29-Jan-2015

Time (UTC)

13:09

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.3.9600.17669_none_d2cf3c1f410cb3b3.manifest

File version

Not applicable

File size

13,224

Date (UTC)

29-Jan-2015

Time (UTC)

13:12

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File property

Value

File name

Amd64_5bcee83f24ae5e443ff36dcb2790ba39_31bf3856ad364e35_6.3.9600.17669_none_8dd97905154ec33d.manifest

File version

Not applicable

File size

712

Date (UTC)

29-Jan-2015

Time (UTC)

13:09

Platform

Not applicable

File name

Amd64_f19406a99d174d53207fcf0872c70f7b_31bf3856ad364e35_6.3.9600.17669_none_22c83b391b0d953b.manifest

File version

Not applicable

File size

714

Date (UTC)

29-Jan-2015

Time (UTC)

13:09

Platform

Not applicable

File name

Amd64_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.3.9600.17669_none_2eedd7a2f96a24e9.manifest

File version

Not applicable

File size

13,230

Date (UTC)

29-Jan-2015

Time (UTC)

13:16

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.3.9600.17669_none_d2cf3c1f410cb3b3.manifest

File version

Not applicable

File size

13,224

Date (UTC)

29-Jan-2015

Time (UTC)

13:16

Platform

Not applicable

Additional files for all supported ARM-based versions of Windows 8.1

File property

Value

File name

Arm_94b17a8378920eec26e378f0f84b591e_31bf3856ad364e35_6.3.9600.17669_none_6808afcff4933f53.manifest

File version

Not applicable

File size

710

Date (UTC)

29-Jan-2015

Time (UTC)

13:09

Platform

Not applicable

File name

Arm_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.3.9600.17669_none_d2d1ae774109d279.manifest

File version

Not applicable

File size

13,224

Date (UTC)

29-Jan-2015

Time (UTC)

13:09

Platform

Not applicable

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012

File property

Value

File name

Amd64_a8b764f3f38c505b68d910618008d83f_31bf3856ad364e35_6.2.9200.21312_none_453311ffdadb30e2.manifest

File version

Not applicable

File size

714

Date (UTC)

01-Dec-2014

Time (UTC)

23:50

Platform

Not applicable

File name

Amd64_f8f56b7d84a4366fe9ccaac0c6363a98_31bf3856ad364e35_6.2.9200.21312_none_7318762ab32c1105.manifest

File version

Not applicable

File size

1,068

Date (UTC)

01-Dec-2014

Time (UTC)

23:50

Platform

Not applicable

File name

Amd64_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.21312_none_97b1c1c5c832c284.manifest

File version

Not applicable

File size

13,196

Date (UTC)

27-Nov-2014

Time (UTC)

01:57

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.21312_none_3b9326420fd5514e.manifest

File version

Not applicable

File size

13,190

Date (UTC)

27-Nov-2014

Time (UTC)

00:29

Platform

Not applicable


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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×