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.

A copy or move operation is unsuccessful if a symbolic link is included in Windows 7 or Windows Server 2008 R2


View products that this article applies to.

Symptoms

When you try to copy or move items in Windows 7 or Windows Server 2008 R2, the operation is unsuccessful if a symbolic link is included. Additionally, you receive an error message that resembles the following:

There is not enough space on location. You need an additional n.nn MB to copy these files.
Note In this error message, location represents the actual target drive and n.nn represents the actual indicated size in megabytes of required space.

↑ 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: 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

To apply this hotfix, you must have Service Pack 1 for Windows 7 or Windows Server 2008 R2 installed.

Restart requirement

You do not 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 7 and Windows Server 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 R2 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 7/Windows Server 2008 R2" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductSR_LevelService branch
    6.1.760
    1.
    23xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important 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 for Windows 7 and Windows Server 2008 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 7
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.1.7601.2304912,878,33609-May-201505:41x86
Shlwapi.dll6.1.7601.23049350,72009-May-201505:41x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.1.7601.2304914,181,37609-May-201506:05x64
Shlwapi.dll6.1.7601.23049450,04809-May-201506:05x64
Shell32.dll6.1.7601.2304912,878,33609-May-201505:41x86
Shlwapi.dll6.1.7601.23049350,72009-May-201505:41x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.1.7601.2304921,201,92009-May-201505:02IA-64
Shlwapi.dll6.1.7601.23049866,30409-May-201505:02IA-64
Shell32.dll6.1.7601.2304912,878,33609-May-201505:41x86
Shlwapi.dll6.1.7601.23049350,72009-May-201505:41x86

Additional file information for Windows 7 and Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_1b62f0c00ba04ad730696282d865163a_31bf3856ad364e35_6.1.7601.23049_none_23e91461296a2a4d.manifest
File versionNot applicable
File size695
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_86f69981396455d74a3610bd9c0e7813_31bf3856ad364e35_6.1.7601.23049_none_fd7ced35cfa2ab1d.manifest
File versionNot applicable
File size695
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.23049_none_6e9e8a4e896fbd72.manifest
File versionNot applicable
File size962,918
Date (UTC)09-May-2015
Time (UTC)06:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-shlwapi_31bf3856ad364e35_6.1.7601.23049_none_fc4f11751c22bafd.manifest
File versionNot applicable
File size2,718
Date (UTC)09-May-2015
Time (UTC)06:09
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameAmd64_10400dfc88f2f56a5f6fedc1f37444d5_31bf3856ad364e35_6.1.7601.23049_none_e7fb3c179125aeb3.manifest
File versionNot applicable
File size1,038
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_1b62f0c00ba04ad730696282d865163a_31bf3856ad364e35_6.1.7601.23049_none_8007afe4e1c79b83.manifest
File versionNot applicable
File size697
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_2929283aa4cc2da77d5cb6f77dd398b6_31bf3856ad364e35_6.1.7601.23049_none_ba7d6ff782619df0.manifest
File versionNot applicable
File size699
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_74ce67442a14846336e0936bd1048a60_31bf3856ad364e35_6.1.7601.23049_none_53294b64752043d7.manifest
File versionNot applicable
File size699
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_75398a2082a1db4faf719384d9a41213_31bf3856ad364e35_6.1.7601.23049_none_d5965a31ab5c0a77.manifest
File versionNot applicable
File size1,040
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.23049_none_cabd25d241cd2ea8.manifest
File versionNot applicable
File size961,784
Date (UTC)09-May-2015
Time (UTC)06:30
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-shlwapi_31bf3856ad364e35_6.1.7601.23049_none_586dacf8d4802c33.manifest
File versionNot applicable
File size2,722
Date (UTC)09-May-2015
Time (UTC)06:33
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.23049_none_d511d024762df0a3.manifest
File versionNot applicable
File size958,545
Date (UTC)09-May-2015
Time (UTC)05:59
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-shlwapi_31bf3856ad364e35_6.1.7601.23049_none_fc4f11751c22bafd.manifest
File versionNot applicable
File size2,718
Date (UTC)09-May-2015
Time (UTC)06:09
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_70752bfe4d32f38163de4cad0e45329a_31bf3856ad364e35_6.1.7601.23049_none_26bfcac6cf7e11be.manifest
File versionNot applicable
File size1,038
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_d0353c6183d8f465e631d837a4f7ca51_31bf3856ad364e35_6.1.7601.23049_none_fb4bffb908d3a364.manifest
File versionNot applicable
File size1,036
Date (UTC)09-May-2015
Time (UTC)12:50
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.23049_none_6ea02e44896dc66e.manifest
File versionNot applicable
File size961,782
Date (UTC)09-May-2015
Time (UTC)05:59
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_microsoft-windows-shlwapi_31bf3856ad364e35_6.1.7601.23049_none_fc50b56b1c20c3f9.manifest
File versionNot applicable
File size2,720
Date (UTC)09-May-2015
Time (UTC)06:00
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.23049_none_d511d024762df0a3.manifest
File versionNot applicable
File size958,545
Date (UTC)09-May-2015
Time (UTC)05:59
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-shlwapi_31bf3856ad364e35_6.1.7601.23049_none_fc4f11751c22bafd.manifest
File versionNot applicable
File size2,718
Date (UTC)09-May-2015
Time (UTC)06:09
SHA-1 hashNot applicable
MD5 hashNot 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

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

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 3009986
Revision : 1
Created on : 1/7/2017
Published on : 6/9/2015
Exists online : False
Views : 157