Symptoms
Assume that you have a Windows Embedded Compact 7-based device that uses persistent storage mounted as root and formatted as TexFAT. When an application calls SetSystemPowerState(_T("coldreboot"), POWER_STATE_RESET, POWER_FORCE), newly added files are missing from the root directory of the persistent store.
Note This issue typically occurs after you apply Windows Embedded Compact 7 Monthly Update (April 2013).
More Information
Software update information
Download information
The Windows Embedded Compact 7 Monthly Update (November 2013) is now available from Microsoft. To download this Windows Embedded Compact 7 Monthly Update, go to the following Microsoft Download Center website:Â
Windows Embedded Compact 7 updates
The kind of processor that each file applies to is visible in the name of each file in the "File information" section.
Prerequisites
This update is supported only if all previously issued updates for this product have also been installed.
Restart requirement
After you apply this 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 other updates.
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.
Files that are included in this hotfix package
|
File name |
File size |
Date |
Time |
Path |
|---|---|---|---|---|
|
Storemain.cpp |
56,384 |
21-Nov-2013 |
00:44 |
Private\Winceos\Coreos\Storage\Fsdmgr |
|
Fsdmgr_lib.lib |
2,972,602 |
21-Nov-2013 |
00:33 |
Public\Common\Oak\Lib\Armv5\Checked |
|
Fsdmgr_lib.lib |
3,196,010 |
21-Nov-2013 |
00:32 |
Public\Common\Oak\Lib\Armv5\Debug |
|
Fsdmgr_lib.lib |
2,788,736 |
21-Nov-2013 |
00:32 |
Public\Common\Oak\Lib\Armv5\Retail |
|
Fsdmgr_lib.lib |
2,972,854 |
21-Nov-2013 |
00:35 |
Public\Common\Oak\Lib\Armv6\Checked |
|
Fsdmgr_lib.lib |
3,196,246 |
21-Nov-2013 |
00:34 |
Public\Common\Oak\Lib\Armv6\Debug |
|
Fsdmgr_lib.lib |
2,788,988 |
21-Nov-2013 |
00:34 |
Public\Common\Oak\Lib\Armv6\Retail |
|
Fsdmgr_lib.lib |
2,969,316 |
21-Nov-2013 |
00:36 |
Public\Common\Oak\Lib\Armv7\Checked |
|
Fsdmgr_lib.lib |
3,193,450 |
21-Nov-2013 |
00:36 |
Public\Common\Oak\Lib\Armv7\Debug |
|
Fsdmgr_lib.lib |
2,786,282 |
21-Nov-2013 |
00:36 |
Public\Common\Oak\Lib\Armv7\Retail |
|
Fsdmgr_lib.lib |
2,889,070 |
21-Nov-2013 |
00:38 |
Public\Common\Oak\Lib\Mipsii\Checked |
|
Fsdmgr_lib.lib |
3,168,278 |
21-Nov-2013 |
00:38 |
Public\Common\Oak\Lib\Mipsii\Debug |
|
Fsdmgr_lib.lib |
2,727,490 |
21-Nov-2013 |
00:38 |
Public\Common\Oak\Lib\Mipsii\Retail |
|
Fsdmgr_lib.lib |
2,890,830 |
21-Nov-2013 |
00:40 |
Public\Common\Oak\Lib\Mipsii_fp\Checked |
|
Fsdmgr_lib.lib |
3,170,038 |
21-Nov-2013 |
00:40 |
Public\Common\Oak\Lib\Mipsii_fp\Debug |
|
Fsdmgr_lib.lib |
2,729,250 |
21-Nov-2013 |
00:40 |
Public\Common\Oak\Lib\Mipsii_fp\Retail |
|
Fsdmgr_lib.lib |
2,704,060 |
21-Nov-2013 |
00:42 |
Public\Common\Oak\Lib\Sh4\Checked |
|
Fsdmgr_lib.lib |
2,962,446 |
21-Nov-2013 |
00:42 |
Public\Common\Oak\Lib\Sh4\Debug |
|
Fsdmgr_lib.lib |
2,575,342 |
21-Nov-2013 |
00:42 |
Public\Common\Oak\Lib\Sh4\Retail |
|
Fsdmgr_lib.lib |
2,601,990 |
21-Nov-2013 |
00:43 |
Public\Common\Oak\Lib\X86\Checked |
|
Fsdmgr_lib.lib |
2,710,952 |
21-Nov-2013 |
00:43 |
Public\Common\Oak\Lib\X86\Debug |
|
Fsdmgr_lib.lib |
2,430,422 |
21-Nov-2013 |
00:43 |
Public\Common\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.
References
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
