VSS task schedule is not created as you configure if shadow copy storage is on another share disk in Windows

Symptoms

Consider the following scenario:

  • You have a cluster that is running Windows Server 2012 R2 or Windows Sever 2012.

  • You set the shadow copy storage area of one cluster disk to another share disk.

  • You create a Volume Shadow Copy Service (VSS) task for the cluster disk.

In this scenario, the trigger of the newly created shadow copy task is not set as expected in the task scheduler. It still uses the default trigger.

How to obtain the hotfix

To resolve this issue, we have released a hotfix for Windows Server 2012 R2 and Windows Server 2012. This hotfix has a prerequisite.

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 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 Server 2012 R2.

There is no prerequisite for Windows Server 2012 to apply this hotfix.

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

    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 for Windows Server 2012 R2" 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

Vssui.dll

6.3.9600.17670

212,480

30-Jan-2015

02:08

x64

Vssuirun.exe

6.3.9600.17670

67,072

30-Jan-2015

02:45

x64

Vssui.dll

6.3.9600.17670

159,744

30-Jan-2015

01:44

x86

Vssuirun.exe

6.3.9600.17670

56,320

30-Jan-2015

02:12

x86

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

    Windows Server 2012

    RTM

    GDR

    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 for Windows Server 2012" 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

Vssui.dll

6.2.9200.17130

216,064

28-Sep-2014

06:29

x64

Vssuirun.exe

6.2.9200.16384

67,072

26-Jul-2012

03:08

x64

Vssui.dll

6.2.9200.21247

216,064

28-Sep-2014

04:33

x64

Vssuirun.exe

6.2.9200.16384

67,072

26-Jul-2012

03:08

x64

Vssui.dll

6.2.9200.17130

165,376

28-Sep-2014

01:53

x86

Vssuirun.exe

6.2.9200.16384

58,880

26-Jul-2012

01:56

x86

Vssui.dll

6.2.9200.21247

165,376

28-Sep-2014

01:36

x86

Vssuirun.exe

6.2.9200.16384

58,880

26-Jul-2012

01:56

x86

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_3c19fe9d65bc8689d9a20f42ee4e4111_31bf3856ad364e35_6.3.9600.17673_none_ec722735cf7dc138.manifest

File version

Not applicable

File size

700

Date (UTC)

05-Feb-2015

Time (UTC)

20:08

Platform

Not applicable

File name

Amd64_d9930b00e1c370d1ad134cb24c30e401_31bf3856ad364e35_6.3.9600.17673_none_9d21e9ff6c3da5a8.manifest

File version

Not applicable

File size

702

Date (UTC)

05-Feb-2015

Time (UTC)

20:08

Platform

Not applicable

File name

Amd64_microsoft-windows-timewarpui_31bf3856ad364e35_6.3.9600.17673_none_4e9b2979a0ee1259.manifest

File version

Not applicable

File size

14,694

Date (UTC)

04-Feb-2015

Time (UTC)

17:40

Platform

Not applicable

File name

X86_microsoft-windows-timewarpui_31bf3856ad364e35_6.3.9600.17673_none_f27c8df5e890a123.manifest

File version

Not applicable

File size

14,688

Date (UTC)

04-Feb-2015

Time (UTC)

03:52

Platform

Not applicable

Additional file information for Windows Server 2012

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

File name

Amd64_05a5baa4856bc643dde59fb44bc76699_31bf3856ad364e35_6.2.9200.17130_none_9a9fdfd9aa8d932b.manifest

File version

Not Applicable

File size

1,044

Date (UTC)

28-Sep-2014

Time (UTC)

16:43

Platform

Not Applicable

File name

Amd64_bb5722a74fc82c94af55310be46abf90_31bf3856ad364e35_6.2.9200.21247_none_4654e931e68e48fd.manifest

File version

Not Applicable

File size

1,044

Date (UTC)

28-Sep-2014

Time (UTC)

16:43

Platform

Not Applicable

File name

Amd64_microsoft-windows-timewarpui_31bf3856ad364e35_6.2.9200.17130_none_b6cea627569d9450.manifest

File version

Not Applicable

File size

14,697

Date (UTC)

28-Sep-2014

Time (UTC)

16:43

Platform

Not Applicable

File name

Amd64_microsoft-windows-timewarpui_31bf3856ad364e35_6.2.9200.21247_none_b754750c6fbd016c.manifest

File version

Not Applicable

File size

14,697

Date (UTC)

28-Sep-2014

Time (UTC)

16:43

Platform

Not Applicable

File name

X86_microsoft-windows-timewarpui_31bf3856ad364e35_6.2.9200.17130_none_5ab00aa39e40231a.manifest

File version

Not Applicable

File size

14,691

Date (UTC)

28-Sep-2014

Time (UTC)

16:43

Platform

Not Applicable

File name

X86_microsoft-windows-timewarpui_31bf3856ad364e35_6.2.9200.21247_none_5b35d988b75f9036.manifest

File version

Not Applicable

File size

14,691

Date (UTC)

28-Sep-2014

Time (UTC)

16:43

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?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×