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.

Insufficient MBCS file name support on the FTP client in Windows


View products that this article applies to.

Symptoms

When you try to use the FTP client in Windows Server 2012 R2, Windows 8.1, Windows Server 2012, or Windows 8, you may encounter the following symptoms.

Symptom 1

The FTP client cannot handle a command text file when it's saved as ANSI text. Additionally, when the command text file is read by using the –s option, you receive the following error message:

451 No mapping for the Unicode character exists in the target multi-byte code page.

Symptom 2

When you try to read the MBCS file names on the FTP server by using the FTP mget command, you receive the following error message:

550 The system cannot find the file specified.

Symptom 3

When you use the FTP mput command to upload files to the FTP server that have MBCS file names, the uploaded files have corrupted file names.

Symptom 4

When you use the FTP lcd command on a local folder that has an MBCS file name, the command fails.

↑ 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 April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


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.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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, 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.17xxxWindows 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, 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 x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Ftp.exe6.3.9600.1767948,64010-Feb-201523:17x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Ftp.exe6.3.9600.1767954,78410-Feb-201523:16x64
Ftp.exe6.3.9600.1767948,64010-Feb-201523:17x86

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.17 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
Ftp.exe6.2.9200.1728647,61625-Feb-201504:57x86
Ftp.exe6.2.9200.2140247,61625-Feb-201504:19x86
For all supported x64-based versions of Windows 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Ftp.exe6.2.9200.1728654,27225-Feb-201506:43x64
Ftp.exe6.2.9200.2140254,27225-Feb-201505:23x64
Ftp.exe6.2.9200.1728647,61625-Feb-201504:57x86
Ftp.exe6.2.9200.2140247,61625-Feb-201504:19x86

Additional file information

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_a8435930502a8c6cd4a55e50c71dcd7b_31bf3856ad364e35_6.3.9600.17679_none_243ebb8277c7172e.manifest
File versionNot applicable
File size691
Date (UTC)11-Feb-2015
Time (UTC)20:09
PlatformNot applicable
File nameX86_microsoft-windows-ftp_31bf3856ad364e35_6.3.9600.17679_none_419ae2bf741706cc.manifest
File versionNot applicable
File size2,576
Date (UTC)11-Feb-2015
Time (UTC)00:04
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_1a3d5eabb7c2aa734df07bc3dd7defa5_31bf3856ad364e35_6.3.9600.17679_none_b82a085be8f8f1a8.manifest
File versionNot applicable
File size695
Date (UTC)11-Feb-2015
Time (UTC)20:09
PlatformNot applicable
File nameAmd64_a8435930502a8c6cd4a55e50c71dcd7b_31bf3856ad364e35_6.3.9600.17679_none_805d570630248864.manifest
File versionNot applicable
File size693
Date (UTC)11-Feb-2015
Time (UTC)20:09
PlatformNot applicable
File nameAmd64_microsoft-windows-ftp_31bf3856ad364e35_6.3.9600.17679_none_9db97e432c747802.manifest
File versionNot applicable
File size2,580
Date (UTC)11-Feb-2015
Time (UTC)00:12
PlatformNot applicable
File nameX86_microsoft-windows-ftp_31bf3856ad364e35_6.3.9600.17679_none_419ae2bf741706cc.manifest
File versionNot applicable
File size2,576
Date (UTC)11-Feb-2015
Time (UTC)00:04
PlatformNot applicable
Additional file information for Windows 8 and for Windows Server 2012
Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameX86_1e32379c5a4b80699053fbc235749752_31bf3856ad364e35_6.2.9200.17286_none_6fcb36f5731599c2.manifest
File versionNot applicable
File size691
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameX86_e6fb49d66d8f3aacefee0ebb4219d1cf_31bf3856ad364e35_6.2.9200.21402_none_5ec7f15378bd7255.manifest
File versionNot applicable
File size691
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameX86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.17286_none_a99851b729ef119f.manifest
File versionNot applicable
File size2,576
Date (UTC)25-Feb-2015
Time (UTC)05:49
PlatformNot applicable
File nameX86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.21402_none_aa746ea042cf69ac.manifest
File versionNot applicable
File size2,576
Date (UTC)25-Feb-2015
Time (UTC)04:58
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012
File propertyValue
File nameAmd64_0419111eb2af4a58a54f131c7007d152_31bf3856ad364e35_6.2.9200.17286_none_422eb3562ea336b5.manifest
File versionNot applicable
File size1,030
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameAmd64_1e32379c5a4b80699053fbc235749752_31bf3856ad364e35_6.2.9200.17286_none_cbe9d2792b730af8.manifest
File versionNot applicable
File size693
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameAmd64_39ec9973327f41f8033b62bd1ccd13a0_31bf3856ad364e35_6.2.9200.21402_none_df17ccadf3f5f502.manifest
File versionNot applicable
File size695
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameAmd64_6c8a25fd01e084f7b50d6e0bb8d0d68d_31bf3856ad364e35_6.2.9200.17286_none_759fc521ee9d1724.manifest
File versionNot applicable
File size695
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameAmd64_9e3196678fd1fbdc23491380a06c5d7b_31bf3856ad364e35_6.2.9200.21402_none_8450f0c37247e545.manifest
File versionNot applicable
File size1,030
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameAmd64_e6fb49d66d8f3aacefee0ebb4219d1cf_31bf3856ad364e35_6.2.9200.21402_none_bae68cd7311ae38b.manifest
File versionNot applicable
File size693
Date (UTC)25-Feb-2015
Time (UTC)13:32
PlatformNot applicable
File nameAmd64_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.17286_none_05b6ed3ae24c82d5.manifest
File versionNot applicable
File size2,580
Date (UTC)25-Feb-2015
Time (UTC)07:36
PlatformNot applicable
File nameAmd64_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.21402_none_06930a23fb2cdae2.manifest
File versionNot applicable
File size2,580
Date (UTC)25-Feb-2015
Time (UTC)06:55
PlatformNot applicable
File nameX86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.17286_none_a99851b729ef119f.manifest
File versionNot applicable
File size2,576
Date (UTC)25-Feb-2015
Time (UTC)05:49
PlatformNot applicable
File nameX86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.21402_none_aa746ea042cf69ac.manifest
File versionNot applicable
File size2,576
Date (UTC)25-Feb-2015
Time (UTC)04:58
PlatformNot 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 : 3027174
Revision : 1
Created on : 1/7/2017
Published on : 4/14/2015
Exists online : False
Views : 187