This issue can also occur if cluster nodes shut down unexpectedly in Windows 8.1 or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite

Symptoms

This issue occurs when one of the following conditions is true:

  • A cluster has a storage area network (SAN) attached.

  • System tries to mount a volume on a cluster, and the node is not the owning node of the disk.

  • The disk is put online accidentally, and the node is not the owning node and it does not own the disk reservation.

  • Windows PE runs on a system that has drivers being online and reserved by another cluster node.


Note The Hyper-V host should enter an automatic repair process after the unexpected shutdown (also known as a dirty shutdown) if the shutdown is unexpected. As a temporary workaround, start the system in safe mode, and then restart it immediately.

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 apply this update, you must have update 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 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

Ntfs.sys

6.3.9600.17631

1,687,872

14-Jan-2015

20:06

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

Ntfs.sys

6.3.9600.17631

2,022,720

14-Jan-2015

20:12

x64

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_a5d431249bef2b5984ca7827a947e986_31bf3856ad364e35_6.3.9600.17633_none_b0057fc0d2074ef4.manifest

File version

Not applicable

File size

692

Date (UTC)

14-Jan-2015

Time (UTC)

22:21

Platform

Not applicable

File name

X86_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_3b45ec80385d9adb.manifest

File version

Not applicable

File size

16,008

Date (UTC)

14-Jan-2015

Time (UTC)

22:24

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_c6023eb259ca802b99b3e661e37dc48b_31bf3856ad364e35_6.3.9600.17633_none_bd094807436c299f.manifest

File version

Not applicable

File size

696

Date (UTC)

14-Jan-2015

Time (UTC)

22:21

Platform

Not applicable

File name

Amd64_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_97648803f0bb0c11.manifest

File version

Not applicable

File size

16,014

Date (UTC)

14-Jan-2015

Time (UTC)

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

More Information

How to insert hotfix 3027110 into WinRE.wim

  1. Create a folder C:\WindowsUpdate.

  2. Download the following .msu files to C:\WindowsUpdate:

    Note Update 2919355 is a prerequisite for update 3027110 so that you do not have to add both update 2919442 and update 2919355 packages if the WinRE image already includes update 2919355 package. To confirm it, type the following command right after step 6:

    dism /image:C:\winre\mount /Get-packages

  3. Open Command Prompt.

  4. Type the following command to disable WinRE:

    REAgentC /disable

  5. Create the following local folder:

    C:\WinRE\Mount

  6. Type the following command to mount the Winre.wim file:

    dism /Mount-Wim /WimFile:C:\Windows\System32\Recovery\WinRE.wim /Index:1 /MountDir:C:\WinRE\Mount

  7. Type the following commands in order to integrate the packages into WinRE image:

    • dism /image:C:\Winre\mount /Add-Package /Packagepath:C:\WindowsUpdate\Windows8.1-KB2919442-x64.msu

    • dism /image:C:\Winre\mount /Add-Package /Packagepath:C:\WindowsUpdate\Windows8.1-KB2919355-x64.msu

    • dism /image:C:\Winre\mount /Add-Package /Packagepath:C:\WindowsUpdate\Windows8.1-KB3027110-v2-x64.msu


    Note Update 2919355 is a prerequisite for update 3027110. You do not have to add both update 2919442 and update 2919355 packages if the WinRE image already includes update 2919355 package. To confirm it, you can type the following command:

    dism /image:C:\winre\mount /Get-packages

  8. Type the following command to verify that the security package was integrated successfully:

    dism /image:C:\winre\mount /Get-Packages

  9. Type the following command to commit the changes to the Winre.wim file:

    dism /unmount-wim /MountDir:C:\Winre\mount /commit

  10. Type the following command to enable WinRE:

    REAgentC /enable

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!

×