Symptoms
Assume that you connect to a Distributed File System (DFS) namespace that is located on a Windows Server 2012-based or Windows Server 2008 R2-based server from a Windows 8-based or Windows Server 2012-based client computer. You try to rename or save files that are located in the secondary subdirectory. In this situation, the operation fails and you receive an error message that resembles the following:
The file or folder does not exist.
Additionally, if a file is saved in a secondary subdirectory, the file later appears in the root directory.
For example, you try to perform the following actions to rename or save files:
-
You map the DFS namespace to drive Z.
-
You create a folder that is named d1 on drive Z, and then create another folder that is named d2 inside the d1 folder.
-
You try to rename or save files in the "Z:\d1\d2" directory.
In this situation, the operation fails and you received the error message. Additionally, if a file is saved in "Z:\d1\d2" directory, the file later appears in the "Z:" directory.
Note This issue occurs when the name resolution from the client computer to the DFS server is not available.
Cause
This issue occurs because the Windows 8-based or Windows Server 2012-based client computer connects to the DFS share by using the following syntax:
\\ipaddress\SHARENAMEThe Windows 8-based or Windows Server 2012-based client computer uses its own IP address to connect to the DFS share. When the computer connects to the DFS share, the server indicates that the share name is a DFS namespace. The client computer internally uses the DFS server name to track the location of the network connection. However, when the name resolution from the client computer to the DFS server is not available, the folder path is not tracked correctly.
Resolution
Hotfix information
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:
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 hotfix, you must be running Windows 8 or Windows Server 2012.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 and Windows Server 2012 file information notesImportant Windows 8 hotfixes 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:
Version
Product
Milestone
Service branch
6.2.920 0.20 xxx
Windows 8 or 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 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 name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Mrxsmb20.sys |
6.2.9200.20667 |
168,448 |
24-Mar-2013 |
22:13 |
x86 |
For all supported x64-based versions of Windows 8 and of Windows Server 2012
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Mrxsmb20.sys |
6.2.9200.20667 |
213,504 |
24-Mar-2013 |
22:13 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
2703610 "The file or folder does not exist" when renaming or saving to DFS share from a Windows 7 computer
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
