System becomes unresponsive when file system minifilter drivers are installed in Windows 8.1 or Windows Server 2012 R2

This article describes a memory leak issue that occurs when one or more file system minifilter drivers are installed in Windows 8.1 or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.
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 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: 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.

Prerequisites

To apply this hotfix, you must have the April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (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.

File information

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:
    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows RT 8.1, Windows 8.1, and Windows 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" 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 nameFile versionFile sizeDateTimePlatform
Fltmgr.sys6.3.9600.17782270,14425-Mar-201518:08x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Fltmgr.sys6.3.9600.17782354,62425-Mar-201518:03x64
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Fltmgr.sys6.3.9600.17782266,06425-Mar-201518:14Not applicable

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 propertyValue
File nameX86_3809fbaf432170dcb24cc3b4646270fb_31bf3856ad364e35_6.3.9600.17782_none_40b7602903ad9cab.manifest
File versionNot applicable
File size706
Date (UTC)25-Mar-2015
Time (UTC)18:23
PlatformNot applicable
File nameX86_microsoft-windows-filtermanager-core_31bf3856ad364e35_6.3.9600.17782_none_a5a727b546678252.manifest
File versionNot applicable
File size10,647
Date (UTC)25-Mar-2015
Time (UTC)18:27
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_cfa892e0682cf5ebf34387826842c212_31bf3856ad364e35_6.3.9600.17782_none_ccccd583bdf09cb6.manifest
File versionNot applicable
File size710
Date (UTC)25-Mar-2015
Time (UTC)18:23
PlatformNot applicable
File nameAmd64_microsoft-windows-filtermanager-core_31bf3856ad364e35_6.3.9600.17782_none_01c5c338fec4f388.manifest
File versionNot applicable
File size10,651
Date (UTC)25-Mar-2015
Time (UTC)18:32
PlatformNot applicable
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_a1cdd3874cf94c968420b7b8cea59e19_31bf3856ad364e35_6.3.9600.17782_none_880994f11965f14c.manifest
File versionNot applicable
File size706
Date (UTC)25-Mar-2015
Time (UTC)18:23
PlatformNot applicable
File nameArm_microsoft-windows-filtermanager-core_31bf3856ad364e35_6.3.9600.17782_none_a5a99a0d4664a118.manifest
File versionNot applicable
File size10,647
Date (UTC)25-Mar-2015
Time (UTC)18:23
PlatformNot applicable
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information

Cause

This issue occurs because the filter manager driver leaks nonpaged pool memory.
References
See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3051690 - Last Review: 07/28/2015 08:21:00 - Revision: 3.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows RT 8.1

  • kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB3051690
Feedback