This article describes a hotfix that improves the optimization schedule and addresses resiliency to hardware failure issues in Windows Server 2012 R2 in a Cloud Platform System environment. The hotfix has prerequisites.

Fixes and Improvements

This update contains fixes for the following issues:

  • If an ongoing optimization job is canceled, the job may not process necessary files when it is restarted. This fix only applies to Cloud Platform System workloads.

  • Deduplication jobs may be falsely reported as not-scheduled by System Center Operations Manager.

This update also improves the management of resources to avoid the kernel stack space exhausting during certain file operations considering hardware failure, and the update improves resiliency to hardware failures when data deduplications run on a system with storage spaces.

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 apply this update, you must have update 2919355 installed in 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 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.17xxx

    Windows Server 2012 R2

    RTM

    GDR

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

File name

File version

File size

Date

Time

Platform

Dedup.sys

6.3.9600.17630

465,216

10-Jan-2015

09:25

x64

Ddppipeline.dll

6.3.9600.17630

2,219,008

10-Jan-2015

07:37

x64

Ddpscan.dll

6.3.9600.17630

548,352

10-Jan-2015

07:37

x64

Ddpstore.dll

6.3.9600.17630

2,356,224

10-Jan-2015

07:39

x64

Ddpcli.exe

6.3.9600.17630

272,896

10-Jan-2015

07:46

x64

Ddpeval.exe

6.3.9600.17630

2,275,840

10-Jan-2015

09:05

x64

Ddpsvc.dll

6.3.9600.17630

1,125,888

10-Jan-2015

07:38

x64

Ddpwmi.dll

6.3.9600.17630

464,896

10-Jan-2015

07:48

x64

Dedupfilemetadata.cdxml

Not applicable

1,446

18-Jun-2013

15:13

Not applicable

Dedupjob.cdxml

Not applicable

8,851

19-Aug-2014

22:13

Not applicable

Deduplication.format.ps1xml

Not applicable

29,987

18-Jun-2013

15:13

Not applicable

Deduplication.psd1

Not applicable

1,241

18-Jun-2013

15:13

Not applicable

Deduplication.types.ps1xml

Not applicable

5,459

18-Jun-2013

15:13

Not applicable

Deduplicationprovider.mof

Not applicable

18,030

18-Jun-2013

15:13

Not applicable

Dedupmetadata.cdxml

Not applicable

1,075

18-Jun-2013

15:13

Not applicable

Dedupschedule.cdxml

Not applicable

12,547

18-Jun-2013

15:13

Not applicable

Dedupstatus.cdxml

Not applicable

2,238

18-Jun-2013

15:13

Not applicable

Dedupvolume.cdxml

Not applicable

9,552

18-Jun-2013

15:13

Not applicable

Additional file information

Additional file information for Windows Server 2012 R2

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

File property

Value

File name

Amd64_404868dee2b7dce1e0d77e791bb3b173_31bf3856ad364e35_6.3.9600.17630_none_944bb99010697873.manifest

File version

Not applicable

File size

704

Date (UTC)

10-Jan-2015

Time (UTC)

19:03

File name

Amd64_cd317bcb9a6f2e9c5a17fe27a9846915_31bf3856ad364e35_6.3.9600.17630_none_c6c8f2e731983239.manifest

File version

Not applicable

File size

706

Date (UTC)

10-Jan-2015

Time (UTC)

19:03

File name

Amd64_d3cfa0ad54b2b2c5febcfa3e846ec4e3_31bf3856ad364e35_6.3.9600.17630_none_9c6b0bfbde0db5a8.manifest

File version

Not applicable

File size

705

Date (UTC)

10-Jan-2015

Time (UTC)

19:03

File name

Amd64_microsoft-windows-dedup-filter_31bf3856ad364e35_6.3.9600.17630_none_f901effd2b8a22c8.manifest

File version

Not applicable

File size

7,824

Date (UTC)

10-Jan-2015

Time (UTC)

09:32

File name

Amd64_microsoft-windows-dedup-pipeline_31bf3856ad364e35_6.3.9600.17630_none_4a4c2b79949c9298.manifest

File version

Not applicable

File size

15,120

Date (UTC)

10-Jan-2015

Time (UTC)

09:33

File name

Amd64_microsoft-windows-dedup-service_31bf3856ad364e35_6.3.9600.17630_none_bfeab62f3d4684f1.manifest

File version

Not applicable

File size

27,123

Date (UTC)

10-Jan-2015

Time (UTC)

09:33


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!

×