Symptoms

Assume that you have a Windows Server 2008 R2 Service Pack 1 (SP1)-based failover cluster. When a cluster node is shutting down, the Resource Host Monitor (rhs.exe) process that hosts IP address resource crashes with the STATUS_ACCESS_VIOLATION error, and the cluster resources do not fail over to another node.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

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 apply this hotfix, you must install Service Pack 1 for Windows Server 2008 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 Server 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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.1.760 1.23xxx

    Windows Server 2008 R2

    SP1

    LDR

  • 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 2008 R2

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.1.7601.23120

1,295,360

09-Jul-2015

18:03

x64

Clusapi.dll

6.1.7601.23120

315,392

09-Jul-2015

18:03

x64

Resutils.dll

6.1.7601.23120

86,016

09-Jul-2015

18:03

x64

Clusapi.dll

6.1.7601.23120

231,424

09-Jul-2015

17:39

x86

Resutils.dll

6.1.7601.23120

71,168

09-Jul-2015

17:39

x86

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.1.7601.23120

2,142,720

09-Jul-2015

17:06

IA-64

Clusapi.dll

6.1.7601.23120

569,344

09-Jul-2015

17:06

IA-64

Resutils.dll

6.1.7601.23120

184,832

09-Jul-2015

17:06

IA-64

Clusapi.dll

6.1.7601.23120

231,424

09-Jul-2015

17:39

x86

Resutils.dll

6.1.7601.23120

71,168

09-Jul-2015

17:39

x86

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File property

Value

File name

Amd64_5d9e55cc0df81b97d9d16bf8ab187208_31bf3856ad364e35_6.1.7601.23120_none_a16c688af0f0b5d7.manifest

File version

Not applicable

File size

1,076

Date (UTC)

09-Jul-2015

Time (UTC)

22:54

Platform

Not applicable

File name

Amd64_bfc318b23435d91affc72e2dd4b48d0c_31bf3856ad364e35_6.1.7601.23120_none_440e65b9dbfd84dd.manifest

File version

Not applicable

File size

718

Date (UTC)

09-Jul-2015

Time (UTC)

22:54

Platform

Not applicable

File name

Amd64_d40508de591bc4c06a2804c1e194e32c_31bf3856ad364e35_6.1.7601.23120_none_53ef65b019d44070.manifest

File version

Not applicable

File size

715

Date (UTC)

09-Jul-2015

Time (UTC)

22:54

Platform

Not applicable

File name

Amd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.23120_none_1f7b3943ccc46b27.manifest

File version

Not applicable

File size

2,693

Date (UTC)

09-Jul-2015

Time (UTC)

18:30

Platform

Not applicable

File name

Amd64_microsoft-windows-f..rcluster-clientcore_31bf3856ad364e35_6.1.7601.23120_none_efe822846828be52.manifest

File version

Not applicable

File size

3,444

Date (UTC)

09-Jul-2015

Time (UTC)

18:32

Platform

Not applicable

File name

X86_microsoft-windows-f..rcluster-clientcore_31bf3856ad364e35_6.1.7601.23120_none_93c98700afcb4d1c.manifest

File version

Not applicable

File size

3,440

Date (UTC)

09-Jul-2015

Time (UTC)

18:07

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File property

Value

File name

Ia64_1e9db56551e84ca11bccda3ddf9adafe_31bf3856ad364e35_6.1.7601.23120_none_9560ae760cff749a.manifest

File version

Not applicable

File size

1,074

Date (UTC)

09-Jul-2015

Time (UTC)

22:54

Platform

Not applicable

File name

Ia64_60b7d767d22028125dfec4e106d8bbaa_31bf3856ad364e35_6.1.7601.23120_none_9e56149cbfefac8d.manifest

File version

Not applicable

File size

713

Date (UTC)

09-Jul-2015

Time (UTC)

22:54

Platform

Not applicable

File name

Ia64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.23120_none_c35e41b6146502ed.manifest

File version

Not applicable

File size

2,691

Date (UTC)

09-Jul-2015

Time (UTC)

18:13

Platform

Not applicable

File name

Ia64_microsoft-windows-f..rcluster-clientcore_31bf3856ad364e35_6.1.7601.23120_none_93cb2af6afc95618.manifest

File version

Not applicable

File size

3,442

Date (UTC)

09-Jul-2015

Time (UTC)

18:16

Platform

Not applicable

File name

X86_microsoft-windows-f..rcluster-clientcore_31bf3856ad364e35_6.1.7601.23120_none_93c98700afcb4d1c.manifest

File version

Not applicable

File size

3,440

Date (UTC)

09-Jul-2015

Time (UTC)

18:07

Platform

Not applicable

Status

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

More Information

CauseThis issue occurs because of a race condition between the background worker thread and the thread that takes last cluster IP version 4 (IPv4) addresses offline. The race condition causes rhs.exe process to crash.

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!

×