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:

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 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.


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:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows 8.1 and Windows Server 2012 R2

    RTM

    GDR

  • 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 name

File version

File size

Date

Time

Platform

Ftp.exe

6.3.9600.17679

48,640

10-Feb-2015

23:17

x86

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Ftp.exe

6.3.9600.17679

54,784

10-Feb-2015

23:16

x64

Ftp.exe

6.3.9600.17679

48,640

10-Feb-2015

23:17

x86

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.

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.17 xxx

    Windows 8 and Windows Server 2012

    RTM

    GDR

    6.2.920 0.21 xxx

    Windows 8 and 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

Ftp.exe

6.2.9200.17286

47,616

25-Feb-2015

04:57

x86

Ftp.exe

6.2.9200.21402

47,616

25-Feb-2015

04:19

x86

For all supported x64-based versions of Windows 8 and Windows Server 2012

File name

File version

File size

Date

Time

Platform

Ftp.exe

6.2.9200.17286

54,272

25-Feb-2015

06:43

x64

Ftp.exe

6.2.9200.21402

54,272

25-Feb-2015

05:23

x64

Ftp.exe

6.2.9200.17286

47,616

25-Feb-2015

04:57

x86

Ftp.exe

6.2.9200.21402

47,616

25-Feb-2015

04:19

x86

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 property

Value

File name

X86_a8435930502a8c6cd4a55e50c71dcd7b_31bf3856ad364e35_6.3.9600.17679_none_243ebb8277c7172e.manifest

File version

Not applicable

File size

691

Date (UTC)

11-Feb-2015

Time (UTC)

20:09

Platform

Not applicable

File name

X86_microsoft-windows-ftp_31bf3856ad364e35_6.3.9600.17679_none_419ae2bf741706cc.manifest

File version

Not applicable

File size

2,576

Date (UTC)

11-Feb-2015

Time (UTC)

00:04

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File property

Value

File name

Amd64_1a3d5eabb7c2aa734df07bc3dd7defa5_31bf3856ad364e35_6.3.9600.17679_none_b82a085be8f8f1a8.manifest

File version

Not applicable

File size

695

Date (UTC)

11-Feb-2015

Time (UTC)

20:09

Platform

Not applicable

File name

Amd64_a8435930502a8c6cd4a55e50c71dcd7b_31bf3856ad364e35_6.3.9600.17679_none_805d570630248864.manifest

File version

Not applicable

File size

693

Date (UTC)

11-Feb-2015

Time (UTC)

20:09

Platform

Not applicable

File name

Amd64_microsoft-windows-ftp_31bf3856ad364e35_6.3.9600.17679_none_9db97e432c747802.manifest

File version

Not applicable

File size

2,580

Date (UTC)

11-Feb-2015

Time (UTC)

00:12

Platform

Not applicable

File name

X86_microsoft-windows-ftp_31bf3856ad364e35_6.3.9600.17679_none_419ae2bf741706cc.manifest

File version

Not applicable

File size

2,576

Date (UTC)

11-Feb-2015

Time (UTC)

00:04

Platform

Not applicable

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8

File property

Value

File name

X86_1e32379c5a4b80699053fbc235749752_31bf3856ad364e35_6.2.9200.17286_none_6fcb36f5731599c2.manifest

File version

Not applicable

File size

691

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

X86_e6fb49d66d8f3aacefee0ebb4219d1cf_31bf3856ad364e35_6.2.9200.21402_none_5ec7f15378bd7255.manifest

File version

Not applicable

File size

691

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

X86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.17286_none_a99851b729ef119f.manifest

File version

Not applicable

File size

2,576

Date (UTC)

25-Feb-2015

Time (UTC)

05:49

Platform

Not applicable

File name

X86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.21402_none_aa746ea042cf69ac.manifest

File version

Not applicable

File size

2,576

Date (UTC)

25-Feb-2015

Time (UTC)

04:58

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012

File property

Value

File name

Amd64_0419111eb2af4a58a54f131c7007d152_31bf3856ad364e35_6.2.9200.17286_none_422eb3562ea336b5.manifest

File version

Not applicable

File size

1,030

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

Amd64_1e32379c5a4b80699053fbc235749752_31bf3856ad364e35_6.2.9200.17286_none_cbe9d2792b730af8.manifest

File version

Not applicable

File size

693

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

Amd64_39ec9973327f41f8033b62bd1ccd13a0_31bf3856ad364e35_6.2.9200.21402_none_df17ccadf3f5f502.manifest

File version

Not applicable

File size

695

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

Amd64_6c8a25fd01e084f7b50d6e0bb8d0d68d_31bf3856ad364e35_6.2.9200.17286_none_759fc521ee9d1724.manifest

File version

Not applicable

File size

695

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

Amd64_9e3196678fd1fbdc23491380a06c5d7b_31bf3856ad364e35_6.2.9200.21402_none_8450f0c37247e545.manifest

File version

Not applicable

File size

1,030

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

Amd64_e6fb49d66d8f3aacefee0ebb4219d1cf_31bf3856ad364e35_6.2.9200.21402_none_bae68cd7311ae38b.manifest

File version

Not applicable

File size

693

Date (UTC)

25-Feb-2015

Time (UTC)

13:32

Platform

Not applicable

File name

Amd64_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.17286_none_05b6ed3ae24c82d5.manifest

File version

Not applicable

File size

2,580

Date (UTC)

25-Feb-2015

Time (UTC)

07:36

Platform

Not applicable

File name

Amd64_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.21402_none_06930a23fb2cdae2.manifest

File version

Not applicable

File size

2,580

Date (UTC)

25-Feb-2015

Time (UTC)

06:55

Platform

Not applicable

File name

X86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.17286_none_a99851b729ef119f.manifest

File version

Not applicable

File size

2,576

Date (UTC)

25-Feb-2015

Time (UTC)

05:49

Platform

Not applicable

File name

X86_microsoft-windows-ftp_31bf3856ad364e35_6.2.9200.21402_none_aa746ea042cf69ac.manifest

File version

Not applicable

File size

2,576

Date (UTC)

25-Feb-2015

Time (UTC)

04:58

Platform

Not applicable

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×