Microsoft KB Archive Search

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.

  1. Home
  2. "Invalid device" error when you try to rename a file on a Network File System client that is running Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2

"Invalid device" error when you try to rename a file on a Network File System client that is running Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Network File System (NFS) client that is running Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2.
  • You access a file share and then try to rename a file.

In this scenario, the file is not renamed, and you receive the following error message:

Invalid device

↑ Back to the top

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=support
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

There are no prerequisites for installing this hotfix in Windows 8 or Windows Server 2012.

To apply this update in Windows 8.1 or 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.

↑ Back to the top

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 8 and Windows Server 2012 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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" 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.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.21 xxxWindows 8 and Windows Server 2012RTMLDR
  • 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 and Windows Server 2012" 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 x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Nfs-clientcore-ppdlic.xrm-msNot Applicable2,89319-Dec-201400:22Not Applicable
Nfsclnt.exe6.2.9200.1638483,96826-Jul-201203:20x86
Nfsnp.dll6.2.9200.1638481,40826-Jul-201203:19x86
Nfsrdr.mofNot Applicable4,49002-Jun-201214:44Not Applicable
Nfsrdr.sys6.2.9200.21336210,43218-Dec-201423:22x86
For all supported x64-based versions of Windows 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Nfs-clientcore-ppdlic.xrm-msNot Applicable2,89319-Dec-201402:08Not Applicable
Nfsclnt.exe6.2.9200.16384101,37626-Jul-201203:08x64
Nfsnp.dll6.2.9200.1638495,74426-Jul-201203:06x64
Nfsrdr.mofNot Applicable4,49002-Jun-201214:44Not Applicable
Nfsrdr.sys6.2.9200.21336262,65618-Dec-201423:22x64

Windows 8.1 and 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 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 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 x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Nfs-clientcore-ppdlic.xrm-msNot applicable2,89308-Jan-201500:21Not applicable
Nfsclnt.exe6.3.9600.1762784,99207-Jan-201503:41x86
Nfsnp.dll6.3.9600.1762781,92007-Jan-201503:41x86
Nfsrdr.mofNot applicable4,49018-Jun-201312:53Not applicable
Nfsrdr.sys6.3.9600.17627210,94407-Jan-201503:50x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Nfs-clientcore-ppdlic.xrm-msNot applicable2,89308-Jan-201500:48Not applicable
Nfsclnt.exe6.3.9600.17627100,86407-Jan-201505:03x64
Nfsnp.dll6.3.9600.1762796,76807-Jan-201505:03x64
Nfsrdr.mofNot applicable4,49018-Jun-201315:17Not applicable
Nfsrdr.sys6.3.9600.17627261,12007-Jan-201505:14x64

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File namePackage_1_for_kb3025097~31bf3856ad364e35~x86~~6.2.1.0.mum
File versionNot Applicable
File size1,833
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File namePackage_2_for_kb3025097~31bf3856ad364e35~x86~~6.2.1.0.mum
File versionNot Applicable
File size2,046
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File namePackage_for_kb3025097_rtm~31bf3856ad364e35~x86~~6.2.1.0.mum
File versionNot Applicable
File size1,956
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File nameX86_4f0b932836c8a9ad055182aa0e7d4a36_31bf3856ad364e35_6.2.9200.21336_none_bbba008c1ef37d07.manifest
File versionNot Applicable
File size702
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File nameX86_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.2.9200.21336_none_aa4f1ce32cee3e22.manifest
File versionNot Applicable
File size28,372
Date (UTC)19-Dec-2014
Time (UTC)07:53
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012
File nameAmd64_6da559f7aac370fcdaa784aa258f23c6_31bf3856ad364e35_6.2.9200.21336_none_f6efb363120a1434.manifest
File versionNot Applicable
File size706
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File nameAmd64_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.2.9200.21336_none_066db866e54baf58.manifest
File versionNot Applicable
File size28,376
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File namePackage_1_for_kb3025097~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,063
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File namePackage_2_for_kb3025097~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,058
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable
File namePackage_for_kb3025097_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum
File versionNot Applicable
File size2,188
Date (UTC)19-Dec-2014
Time (UTC)07:50
PlatformNot Applicable

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_6f0906422072e65800783c48f153ea24_31bf3856ad364e35_6.3.9600.17628_none_6f51a7d5c35e825b.manifest
File versionNot applicable
File size702
Date (UTC)10-Jan-2015
Time (UTC)02:49
File nameX86_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.3.9600.17628_none_41c710d65df97a2e.manifest
File versionNot applicable
File size28,369
Date (UTC)08-Jan-2015
Time (UTC)00:38
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_b2b48da0acae81d33438134b28a854da_31bf3856ad364e35_6.3.9600.17628_none_d6a294c78728940f.manifest
File versionNot applicable
File size706
Date (UTC)10-Jan-2015
Time (UTC)02:49
File nameAmd64_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.3.9600.17628_none_9de5ac5a1656eb64.manifest
File versionNot applicable
File size28,373
Date (UTC)08-Jan-2015
Time (UTC)02:12

↑ 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

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

↑ Back to the top

Keywords: kb, kbqfe, kbfix, kbexpertiseinter, kbsurveynew, kbbug, kbautohotfix, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 3025097
Revision : 1
Created on : 1/7/2017
Published on : 3/19/2015
Exists online : False
Views : 180