- 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.
Hotfix informationA 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.
PrerequisitesTo apply this update in Windows Server 2012 R2, you must first have update 2919355 installed.
Restart requirementYou 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 informationThis hotfix does not replace any previously released hotfix.
Note This is a temporary workaround and not a recommended best practice because it has potential security implications.
Article ID: 3056053 - Last Review: Jan 19, 2016 - Revision: 1