Symptoms

Assume that you have a Web Services on Devices (WSD) server that is running Windows 7 Service Pack 1 (SP1) or Windows 8. In this situation, the transfer fails and the data is corrupted.

Cause

This issue occurs because two additional bytes are added to a file that ends with byte 0x0D when data is sent from the WSD server to a WSD client. The additional bytes are added because the CWSDInboundMIMEHandler::LockAndRead function cannot recognize the carriage-return line-feed (CRLF) that comes before a boundary in the following situations:

  • Data that ends with CR.

  • Data ends with a single hyphen (-).

Therefore, the CRLF before the boundary is added and the transfer fails.

Resolution

Update information for Windows 8

To resolve this issue in Windows 8, install update rollup 2883201. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2883201 Windows RT, Windows 8, and Windows Server 2012 update rollup: October 2013

Hotfix information for Windows 8 and Windows 7 SP1

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 7 SP1 or Windows 8.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

The global version of this update 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 file information notes

  • 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

    Service branch

    6.1.760 1.18xxx

    GDR

    6.1.760 1.22xxx

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical 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 SP1" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. 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 SP1

File name

File version

File size

Date

Time

Platform

Wsdapi.dll

6.1.7601.18205

458,752

09-Jul-2013

04:52

x86

Wsdapi.mof

Not applicable

2,348

10-Jun-2009

21:48

Not applicable

Wsdapi.dll

6.1.7601.22380

458,752

09-Jul-2013

14:02

x86

Wsdapi.mof

Not applicable

2,348

10-Jun-2009

21:48

Not applicable

For all supported x64-based versions of Windows 7 SP1

File name

File version

File size

Date

Time

Platform

Wsdapi.dll

6.1.7601.18205

577,536

09-Jul-2013

05:53

x64

Wsdapi.mof

Not applicable

2,348

10-Jun-2009

21:10

Not applicable

Wsdapi.dll

6.1.7601.22380

577,536

09-Jul-2013

14:52

x64

Wsdapi.mof

Not applicable

2,348

10-Jun-2009

21:10

Not applicable

Wsdapi.dll

6.1.7601.18205

458,752

09-Jul-2013

04:52

x86

Wsdapi.mof

Not applicable

2,348

10-Jun-2009

21:48

Not applicable

Wsdapi.dll

6.1.7601.22380

458,752

09-Jul-2013

14:02

x86

Wsdapi.mof

Not applicable

2,348

10-Jun-2009

21:48

Not applicable

Windows 8 file information notes

  • 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

    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" 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 Windows RT

File name

File version

File size

Date

Time

Platform

Wsdapi.dll

6.2.9200.16664

422,912

12-Jul-2013

02:34

Not applicable

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable

For all supported x86-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Wsdapi.dll

6.2.9200.16664

485,376

12-Jul-2013

01:30

x86

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable

Wsdapi.dll

6.2.9200.20773

485,376

12-Jul-2013

06:35

x86

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable

For all supported x64-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Wsdapi.dll

6.2.9200.16664

599,040

12-Jul-2013

01:38

x64

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable

Wsdapi.dll

6.2.9200.20773

599,040

12-Jul-2013

09:42

x64

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable

Wsdapi.dll

6.2.9200.16664

485,376

12-Jul-2013

01:30

x86

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable

Wsdapi.dll

6.2.9200.20773

485,376

12-Jul-2013

06:35

x86

Wsdapi.mof

Not applicable

2,348

02-Jun-2012

15:00

Not applicable



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

Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×