"An unrecoverable failure occurred inside the filter manager" error on a failover cluster node that hosts shared VHDx files

When you have a failover cluster node in a Windows Server 2012 R2 environment, and this node hosts VHDx files that are configured to be shared by more than one virtual machine, you may receive a Stop error message that resembles the following:

FLTMGR_FILE_SYSTEM (f5) An unrecoverable failure occurred inside the filter manager.
This problem occurs on the node where the Cluster Shared Volume (CSV) that's hosting the VHDx file is owned. The node might be either a Scale Out File Server or Hyper-V cluster node.
This problem occurs because of a problem with the filter driver that implements the shared VHDx functionality.
To resolve this problem, apply this hotfix to all nodes of the failover cluster.

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to the following Microsoft website: Note 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.


To apply this update in Windows Server 2012 R2, you must first have update 2919355 installed.

Restart requirement

You may have to restart the computer after you apply this hotfix. 

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

The English (United States) 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 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" 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.
    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows Server 2012 R2RTMGDR
  • 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 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 nameFile versionFile sizeDateTimePlatform

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_c725910b19f53477aaec88571a847143_31bf3856ad364e35_6.3.9600.17891_none_dc347b9c22d26dbd.manifest
File versionNot Applicable
File size721
Date (UTC)29-May-2015
Time (UTC)09:12
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-f..uster-svhdxflt-core_31bf3856ad364e35_6.3.9600.17891_none_cb7b7d331a3c8de2.manifest
File versionNot Applicable
File size4,505
Date (UTC)29-May-2015
Time (UTC)04:15
SHA-1 hashNot Applicable
MD5 hashNot Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.

Article ID: 3068444 - Last Review: 09/17/2015 01:25:00 - Revision: 2.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows Server 2012 R2 Standard

  • kbqfe kbsurveynew kbautohotfix kbhotfixserver kbfix kbexpertiseinter kbbug KB3068444