Cluster validation fails in the "Validate Simultaneous Failover" test in a Windows Server 2012 R2-based failover cluster

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

This article describes an issue that occurs when cluster validation is run to validate cluster configuration in Windows Server 2012 R2. A hotfix is available to fix this issue. The hotfix has a prerequisite.

About this hotfix

This hotfix changes some timing of the "Validate Simultaneous failover" test to more accurately verify the storage compatibility with the failover cluster. This cluster validation test is intended to test and verify that the storage functionality is compatible with the failover cluster and other errors that are the test results. It will indicate an incompatibility that needs to be fixed.

For more information about the support policy for the failover cluster, see: The Microsoft support policy for Windows Server 2012 or Windows Server 2012 R2 failover clusters.

Issue fixed in this hotfix

When you run failover cluster validation, the validation may fail during the storage validation tests. It may occur by using Validate a Configuration Wizard from Failover Cluster Manager or by initiating validation that uses the "Test-Cluster" PowerShell cmdlet.  

The following is an example of the error message that may occur during this issue:

Failure seen in the Validation Report.

Validate Simultaneous Failover
Description: Validate that disks can fail over simultaneously with data intact.
Validate Simultaneous Failover
Start: Date and Time.
Node holds the SCSI PR on Test Disk 0 but has failed in its attempt to bring the disk online. The system cannot find the file specified.
Stop: Date and Time.
Node holds the SCSI PR on Test Disk 0 but has failed in its attempt to bring the disk online. The system cannot find the file specified.

Corresponding error in the ValidateStorage.log found on the failing node in the c:\windows\cluster\reports directory:

00000d80.000012a0::Date-Time CprepDiskOnline: ERROR: Failed to open device \Device\Harddisk1\Partition1\, status 2

00000d80.000012a0::Date-Time CprepDiskOnline: EXIT hr 0x80070002
Note The disk number and harddisk\partition may be different in each failure.

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


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.

Registry information

To use the hotfix in this package, you don't 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 doesn't replace a previously released hotfix.


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


See the terminology that Microsoft uses to describe software updates.