Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You have a server that is running Windows Server 2012 R2 or Windows Server 2012.

  • You have the "Server for NFS role" service installed.

  • The NFS share that is provisioned by the server for NFS is backed by a volume that has snapshots available on it.

  • You try to use an NFS client to navigate the NFS share that is exported by the "Server for NFS role" service.

In this scenario, you cannot browse the snapshot share.

Resolution

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:

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 in Windows Server 2012 R2, you must first have update 2919355 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the NFS service. To do this, use the following commands:

nfsadmin server stop nfsadmin server start

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


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.

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows Server 2012 R2

    RTM

    GDR

  • 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 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 name

File version

File size

Date

Time

Platform

Msnfsflt.mof

Not Applicable

4,460

18-Jun-2013

15:17

Not applicable

Msnfsflt.sys

6.3.9600.17804

31,744

11-Apr-2015

02:04

x64

Nfs-servercore-ppdlic.xrm-ms

Not Applicable

2,893

11-Apr-2015

03:15

Not applicable

Nfssvc.exe

6.3.9600.17804

67,584

11-Apr-2015

01:52

x64

Nfssvr.mof

Not Applicable

6,233

18-Jun-2013

15:17

Not applicable

Nfssvr.sys

6.3.9600.17804

1,233,408

11-Apr-2015

02:02

x64

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 is 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.16 xxx

    Windows Server 2012

    RTM

    GDR

    6.2.920 0.21xxx

    Windows Server 2012

    RTM

    LDR

  • 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 Server 2012" 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 x64-based versions of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Msnfsflt.mof

Not applicable

4,460

06-Jul-2012

20:34

Not applicable

Msnfsflt.sys

6.2.9200.16453

32,256

08-Nov-2012

04:00

x64

Nfs-servercore-ppdlic.xrm-ms

Not applicable

2,893

13-Apr-2015

06:25

Not applicable

Nfssvc.exe

6.2.9200.16453

67,584

08-Nov-2012

04:22

x64

Nfssvr.mof

Not applicable

6,233

06-Jul-2012

20:34

Not applicable

Nfssvr.sys

6.2.9200.17343

1,249,792

13-Apr-2015

03:21

x64

Msnfsflt.mof

Not applicable

4,460

02-Jun-2012

14:44

Not applicable

Msnfsflt.sys

6.2.9200.16384

32,256

26-Jul-2012

02:29

x64

Nfs-servercore-ppdlic.xrm-ms

Not applicable

2,893

12-Apr-2015

22:45

Not applicable

Nfssvc.exe

6.2.9200.16384

67,584

26-Jul-2012

03:08

x64

Nfssvr.mof

Not applicable

6,233

02-Jun-2012

14:44

Not applicable

Nfssvr.sys

6.2.9200.21456

1,249,792

09-Apr-2015

22:21

x64

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File name

Amd64_42db36e703767e3001c064ad8329192a_31bf3856ad364e35_6.3.9600.17804_none_3a388d204aa4f255.manifest

File version

Not applicable

File size

706

Date (UTC)

11-Apr-2015

Time (UTC)

07:55

File name

Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.3.9600.17804_none_4cb97a94db01e54e.manifest

File version

Not applicable

File size

38,040

Date (UTC)

11-Apr-2015

Time (UTC)

03:15

File name

Package_1_for_kb3056053~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

1,838

Date (UTC)

11-Apr-2015

Time (UTC)

07:55

File name

Package_for_kb3056053_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

1,413

Date (UTC)

11-Apr-2015

Time (UTC)

07:55

File name

Package_for_kb3056053_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

1,475

Date (UTC)

11-Apr-2015

Time (UTC)

07:55

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File property

Value

File name

Amd64_13e5ede1eb981050a935759710a7d367_31bf3856ad364e35_6.2.9200.17343_none_da6a36fc1216011c.manifest

File version

Not applicable

File size

706

Date (UTC)

13-Apr-2015

Time (UTC)

11:13

Platform

Not applicable

File name

Amd64_c686ffffad1416eefd33e0868b4e1df9_31bf3856ad364e35_6.2.9200.21457_none_a582e9e4c42865e3.manifest

File version

Not applicable

File size

706

Date (UTC)

13-Apr-2015

Time (UTC)

11:13

Platform

Not applicable

File name

Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.17343_none_b498787690f0797b.manifest

File version

Not applicable

File size

38,027

Date (UTC)

13-Apr-2015

Time (UTC)

11:14

Platform

Not applicable

File name

Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.21457_none_b51b467daa129a92.manifest

File version

Not applicable

File size

38,027

Date (UTC)

13-Apr-2015

Time (UTC)

11:14

Platform

Not applicable

Workaround

To temporarily work around this problem, you can choose to disable handle signing. To do this, set the HandleSigningEnabled parameter to 0 (zero) as described in Performance Tuning Guidelines for Windows Server 2012 R2.

Note This is a temporary workaround and not a recommended best practice because it has potential security implications.

Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×