Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

NFS service freezes on a Windows Server 2012 cluster and a client computer can't access NFS share


View products that this article applies to.

This issue occurs because of a deadlock that occurs when multiple threads try to run different tasks on the Network File System (NFS) share.

↑ Back to the top


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.


Prerequisites

There's no prerequisite to apply this hotfix.

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.

↑ Back to the top


File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows 8 and 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's 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.16xxx Windows Server 2012RTMGDR
    6.2.920 0.21xxxWindows Server 2012RTMLDR
  • 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 aren't listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 8

Windows Server 2012

x64 Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Msnfsflt.mofNot applicable4,46002-Jun-201214:44Not applicable
Msnfsflt.sys6.2.9200.1638432,25626-Jul-201202:29x64
Nfs-servercore-ppdlic.xrm-msNot applicable2,89330-Sep-201515:55Not applicable
Nfssvc.exe6.2.9200.1638467,58426-Jul-201203:08x64
Nfssvr.mofNot applicable6,23302-Jun-201214:44Not applicable
Nfssvr.sys6.2.9200.216471,252,35230-Sep-201513:26x64

Additional file information

x64 Windows Server 2012
File propertyValue
File nameAmd64_c6c85bcdccf2363c40e676c8b596e014_31bf3856ad364e35_6.2.9200.21647_none_699b721dae28de46.manifest
File versionNot applicable
File size706
Date (UTC)30-Sep-2015
Time (UTC)23:14
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.21647_none_b5261a35aa0a78ef.manifest
File versionNot applicable
File size38,027
Date (UTC)30-Sep-2015
Time (UTC)23:14
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,609
Date (UTC)30-Sep-2015
Time (UTC)23:14
PlatformNot applicable

↑ Back to the top


Status

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

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbqfe, kbsurveynew, kbfix, kbexpertiseadvanced, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 3078414
Revision : 1
Created on : 1/7/2017
Published on : 11/11/2015
Exists online : False
Views : 151