Insufficient MBCS file name support on the FTP client in Windows

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.

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

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

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

Artikel-id: 3027174 – senaste granskning 14 apr. 2015 – revision: 1

Feedback