Consider the following scenario:
- You run an application on a Windows CE 5.0-based device that has an inserted storage device. The application opens a file handle on a mounted volume that corresponds to the storage device.
- You remove the storage device.
- Then, you try to suspend the Windows CE 5.0-based device.
In this scenario, the system becomes unresponsive.
This problem occurs because the File System Disk Manager (FSDMGR) enters into an infinite loop. When a file handle is opened on a mounted volume, and then the volume is dismounted, the file handle is reset by a deallocation process. However, a file system change notification is sent to the file handle when a suspend operation is called at the same time. Then, the system becomes unresponsive.
Software update information
A supported software update is now available from Microsoft as Windows CE 5.0 Platform Builder Monthly Update (December 2006). You can confirm this by scrolling to the "File information" section of this article. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is:
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 obtaining Windows CE Platform Builder and core operating system software updates:
837392Â
(http://kbalertz.com/Feedback.aspx?kbNumber=837392/
)
How to locate core operating system fixes for Microsoft Windows CE Platform Builder products
Restart requirement
After you apply 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 OS menu, make sure that the following options are selected, and then click Sysgen:
- Clean Before Building
- Copy Files to Release Directory After Build
- Make Run-Time Image After Build
- On the Build OS menu, click Open Release Directory. At the command prompt, type the following command, and then press ENTER:
blddemo clean -q
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other 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
Collapse this tableExpand this table
| File name | File size | Date | Time |
|---|
| Wincepb50-061206-kb929174-mipsii_fp.msi | 646,144 | 06-Dec-2006 | 22:40 |
| Wincepb50-061206-kb929174-mipsii.msi | 645,632 | 06-Dec-2006 | 22:40 |
| Wincepb50-061206-kb929174-armv4i.msi | 628,224 | 06-Dec-2006 | 22:40 |
| Wincepb50-061206-kb929174-mipsiv_fp.msi | 650,240 | 06-Dec-2006 | 22:40 |
| Wincepb50-061206-kb929174-sh4.msi | 619,520 | 06-Dec-2006 | 22:40 |
| Wincepb50-061206-kb929174-mipsiv.msi | 649,728 | 06-Dec-2006 | 22:40 |
| Wincepb50-061206-kb929174-x86.msi | 585,728 | 06-Dec-2006 | 22:40 |
Files that are included in this hotfix
package
Collapse this tableExpand this table
| File name | File size | Date | Time | Path |
|---|
| Windows ce 5.0_update_kb929174.htm | 7,260 | 06-Dec-2006 | 22:34 | 061206_kb929174 |
| Fsmain.lib | 369,482 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Armv4i\Debug |
| Fsmain.lib | 330,222 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Armv4i\Retail |
| Fsmain.lib | 403,140 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Mipsii\Debug |
| Fsmain.lib | 338,718 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Mipsii\Retail |
| Fsmain.lib | 403,180 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Mipsii_fp\Debug |
| Fsmain.lib | 338,756 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Mipsii_fp\Retail |
| Fsmain.lib | 411,028 | 05-Dec-2006 | 23:51 | Public\Common\Oak\Lib\Mipsiv\Debug |
| Fsmain.lib | 339,296 | 05-Dec-2006 | 23:51 | Public\Common\Oak\Lib\Mipsiv\Retail |
| Fsmain.lib | 411,068 | 05-Dec-2006 | 23:51 | Public\Common\Oak\Lib\Mipsiv_fp\Debug |
| Fsmain.lib | 339,336 | 05-Dec-2006 | 23:51 | Public\Common\Oak\Lib\Mipsiv_fp\Retail |
| Fsmain.lib | 328,862 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Sh4\Debug |
| Fsmain.lib | 289,454 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\Sh4\Retail |
| Fsmain.lib | 311,310 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\X86\Debug |
| Fsmain.lib | 259,642 | 05-Dec-2006 | 23:50 | Public\Common\Oak\Lib\X86\Retail |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates