FIX: Registry keys that are created by using the REG_OPTION_VOLATILE flag may appear as duplicate registry keys after a system reset in Windows CE 5.0 (912155)



The information in this article applies to:

  • Microsoft Windows CE 5.0

SYMPTOMS

In Microsoft Windows CE 5.0, registry keys that are created by using the REG_OPTION_VOLATILE flag may appear as duplicate registry keys after a system reset. This problem only occurs when you use the RAM-based registry. This problem does not occur when you use the hive-based registry.

RESOLUTION

Software update information

A supported software update is now available from Microsoft as Windows CE 5.0 Core OS QFE 912155. 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 How to locate core operating system fixes for Microsoft Windows CE Platform Builder products

Prerequisites

This update is supported only if all previous updates for this product are also installed.

Restart requirement

After you install this update, you must perform a clean build of the whole platform. To clean the platform, click Clean on the Build menu. To build the platform, click Build Platform on the Build menu. You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this package has the file attributes (or later file attributes) that are listed in the following table.
File nameFile sizeDateTime
Wincepb50-051231-kb912155-armv4i.msi842,75206-Jan-200601:08
Wincepb50-051231-kb912155-mipsii.msi878,59206-Jan-200601:08
Wincepb50-051231-kb912155-mipsii_fp.msi878,59206-Jan-200601:08
Wincepb50-051231-kb912155-mipsiv.msi891,39206-Jan-200601:08
Wincepb50-051231-kb912155-mipsiv_fp.msi891,39206-Jan-200601:09
Wincepb50-051231-kb912155-sh4.msi831,48806-Jan-200601:08
Wincepb50-051231-kb912155-x86.msi775,16806-Jan-200601:08
The English version of this update 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 tool in Control Panel.
File nameFile sizeDateTimePath
Fsreg.lib368,23619-Dec-200518:57public\common\oak\lib\armv4i\debug
Fsreghive.lib440,99619-Dec-200518:56public\common\oak\lib\armv4i\debug
Fsreg.lib237,72219-Dec-200518:56public\common\oak\lib\armv4i\retail
Fsreghive.lib280,56019-Dec-200518:56public\common\oak\lib\armv4i\retail
Fsreg.lib384,94619-Dec-200518:57public\common\oak\lib\mipsii\debug
Fsreghive.lib459,18419-Dec-200518:57public\common\oak\lib\mipsii\debug
Fsreg.lib242,83219-Dec-200518:57public\common\oak\lib\mipsii\retail
Fsreghive.lib289,87819-Dec-200518:57public\common\oak\lib\mipsii\retail
Fsreg.lib384,98419-Dec-200518:57public\common\oak\lib\mipsii_fp\debug
Fsreghive.lib459,22619-Dec-200518:57public\common\oak\lib\mipsii_fp\debug
Fsreg.lib242,89019-Dec-200518:57public\common\oak\lib\mipsii_fp\retail
Fsreghive.lib289,94819-Dec-200518:57public\common\oak\lib\mipsii_fp\retail
Fsreg.lib393,77619-Dec-200518:58public\common\oak\lib\mipsiv\debug
Fsreghive.lib468,35419-Dec-200518:57public\common\oak\lib\mipsiv\debug
Fsreg.lib244,62019-Dec-200518:57public\common\oak\lib\mipsiv\retail
Fsreghive.lib291,55019-Dec-200518:57public\common\oak\lib\mipsiv\retail
Fsreg.lib393,81419-Dec-200518:58public\common\oak\lib\mipsiv_fp\debug
Fsreghive.lib468,39619-Dec-200518:58public\common\oak\lib\mipsiv_fp\debug
Fsreg.lib244,68219-Dec-200518:58public\common\oak\lib\mipsiv_fp\retail
Fsreghive.lib291,62619-Dec-200518:58public\common\oak\lib\mipsiv_fp\retail
Fsreg.lib315,63219-Dec-200518:56public\common\oak\lib\sh4\debug
Fsreghive.lib381,05819-Dec-200518:56public\common\oak\lib\sh4\debug
Fsreg.lib215,35819-Dec-200518:56public\common\oak\lib\sh4\retail
Fsreghive.lib258,69619-Dec-200518:56public\common\oak\lib\sh4\retail
Fsreg.lib306,02419-Dec-200518:56public\common\oak\lib\x86\debug
Fsreghive.lib370,27019-Dec-200518:56public\common\oak\lib\x86\debug
Fsreg.lib201,26219-Dec-200518:56public\common\oak\lib\x86\retail
Fsreghive.lib237,36419-Dec-200518:56public\common\oak\lib\x86\retail

WORKAROUND

To work around this problem, you can switch to the hive-based registry. To maintain the same set of system requirements as the RAM-based registry, you can store the hive-based registry files in the RAM file system.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Starting in Windows CE 5.0, the dwOptions parameter of the RegCreateKeyEx function can be set to the REG_OPTION_VOLATILE flag to specify that a registry key is volatile. Volatile registry keys should be removed automatically before the system restarts.

For more information, 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


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbBug kbfix kbQFE kbpubtypekc KB912155 kbAudOEM