This article describes an issue that occurs when Disk Control Manager(DCM) can't query volumes in Windows Server 2012 R2. A hotfix is available to fix this issue. Before you install this hotfix, see the Prerequisites section.

Symptoms

When this issue occurs, DCM clears volume information in System Center 2012 R2 Configuration Manager. It results in CSV path being changed automatically. Also, users can't use virtual machines (VMs) when this issue occurs.

Note CSV represents Clustered Shared Volume.


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's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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 don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, install update 2975061 first, and then install update 2919355 in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You must restart the computer to make the changes effective.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Notes

  • 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.18 xxx

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

x64 Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Clusres.dll

6.3.9600.18048

1,997,312

04-Sep-2015

18:24

x64

Clussvc.exe

6.3.9600.18048

7,521,280

04-Sep-2015

18:38

x64


x64 Windows Server 2012 R2

File property

Value

File name

Amd64_94d2963614bcb0c9cc16e23664dce53f_31bf3856ad364e35_6.3.9600.18048_none_f5cb29644d48c424.manifest

File version

Not applicable

File size

1,072

Date (UTC)

05-Sep-2015

Time (UTC)

07:36

Platform

Not applicable

File name

Amd64_c3f5c73e53f65dcda62fb2a3c283890d_31bf3856ad364e35_6.3.9600.18048_none_5e81bf43ed417169.manifest

File version

Not applicable

File size

715

Date (UTC)

05-Sep-2015

Time (UTC)

07:36

Platform

Not applicable

File name

Amd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.3.9600.18048_none_b1c80ccc70ce80e1.manifest

File version

Not applicable

File size

2,732

Date (UTC)

04-Sep-2015

Time (UTC)

20:55

Platform

Not applicable

File name

Amd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.3.9600.18048_none_aaaf16ee755f0579.manifest

File version

Not applicable

File size

9,346

Date (UTC)

04-Sep-2015

Time (UTC)

20:55

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,595

Date (UTC)

05-Sep-2015

Time (UTC)

07:36

Platform

Not applicable

File name

Wow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.3.9600.18048_none_b503c140a9bfc774.manifest

File version

Not applicable

File size

6,410

Date (UTC)

04-Sep-2015

Time (UTC)

19:28

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?

Thank you for your feedback!

×