Downloaded file is truncated on a Windows Embedded CE 6.0 R3-based device


Symptoms


Consider the following scenario:
  • You have a Windows Embedded CE 6.0 R3-based image on a target device. This image contains the Windows Embedded CE 6.0 monthly update for December 2009.
  • You try to download a file to an external storage device of the target device by using Windows Internet Explorer. The external storage device has enough available capacity for the file. The size of the file is larger than the available capacity of the built-in storage of the device.
In this scenario, the downloaded file is truncated without any notification.

Cause


This issue occurs because the size of the cache folder on the device is not checked when the file is downloaded. Therefore, the file is truncated to the size of the cache folder.

Note Before the Windows Embedded CE 6.0 monthly update for December 2009 is installed, files are downloaded to the cache folder first, and then the files are copied to the destination folder. 

Resolution


After you install the following update, the download process checks the size of the cache folder. If the size of the cache folder is not at least 100 kilobytes larger than the size of the file, the file is downloaded to the destination folder directly.

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (November 2010). You can confirm this by scrolling to the "File information" section. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is as follows:
Product version-yymmdd-kbnnnnnn-processor type
For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about how to obtain Windows CE Platform Builder and core operating system software updates:
837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder products

Prerequisites

This software update is supported only if all previously issued software updates for this product have also been applied.

Restart requirement

After you install this software update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
  • On the Build menu, click Clean Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any updates. 

File information

The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Installer files
File nameFile sizeDateTime
Wincepb60-101130-kb2429701-armv4i.msi2,009,60030-Nov-201022:51
Wincepb60-101130-kb2429701-mipsii.msi1,969,15230-Nov-201022:51
Wincepb60-101130-kb2429701-mipsii_fp.msi1,969,66430-Nov-201022:51
Wincepb60-101130-kb2429701-mipsiv.msi1,974,78430-Nov-201022:51
Wincepb60-101130-kb2429701-mipsiv_fp.msi1,975,29630-Nov-201022:51
Wincepb60-101130-kb2429701-sh4.msi1,956,35230-Nov-201022:51
Wincepb60-101130-kb2429701-x86.msi1,911,29630-Nov-201022:51
Files that are included in this hotfix package
File nameFile sizeDateTimePath
Windows embedded ce 6.0_update_kb2429701.htm7,64630-Nov-201022:24101130_kb2429701
Dochost.lib1,674,47017-Nov-201015:54Public\Ie\Oak\Lib\Armv4i\Debug
Dochost.lib1,108,66817-Nov-201015:54Public\Ie\Oak\Lib\Armv4i\Retail
Dochost.lib1,579,02017-Nov-201015:54Public\Ie\Oak\Lib\Mipsii\Debug
Dochost.lib1,070,34017-Nov-201015:54Public\Ie\Oak\Lib\Mipsii\Retail
Dochost.lib1,579,14217-Nov-201015:54Public\Ie\Oak\Lib\Mipsii_fp\Debug
Dochost.lib1,070,46017-Nov-201015:54Public\Ie\Oak\Lib\Mipsii_fp\Retail
Dochost.lib1,600,17817-Nov-201015:55Public\Ie\Oak\Lib\Mipsiv\Debug
Dochost.lib1,075,89017-Nov-201015:55Public\Ie\Oak\Lib\Mipsiv\Retail
Dochost.lib1,600,29017-Nov-201015:55Public\Ie\Oak\Lib\Mipsiv_fp\Debug
Dochost.lib1,076,00617-Nov-201015:55Public\Ie\Oak\Lib\Mipsiv_fp\Retail
Dochost.lib1,461,94217-Nov-201015:55Public\Ie\Oak\Lib\Sh4\Debug
Dochost.lib991,61417-Nov-201015:55Public\Ie\Oak\Lib\Sh4\Retail
Dochost.lib1,429,68017-Nov-201015:54Public\Ie\Oak\Lib\X86\Debug
Dochost.lib991,94817-Nov-201015:53Public\Ie\Oak\Lib\X86\Retail

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