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:
SYMPTOMSIn 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.RESOLUTIONSoftware update informationA 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 PrerequisitesThis update is supported only if all previous updates for this product are also installed. Restart requirementAfter 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 informationThis 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. |
Wincepb50-051231-kb912155-armv4i.msi | 842,752 | 06-Jan-2006 | 01:08 | Wincepb50-051231-kb912155-mipsii.msi | 878,592 | 06-Jan-2006 | 01:08 | Wincepb50-051231-kb912155-mipsii_fp.msi | 878,592 | 06-Jan-2006 | 01:08 | Wincepb50-051231-kb912155-mipsiv.msi | 891,392 | 06-Jan-2006 | 01:08 | Wincepb50-051231-kb912155-mipsiv_fp.msi | 891,392 | 06-Jan-2006 | 01:09 | Wincepb50-051231-kb912155-sh4.msi | 831,488 | 06-Jan-2006 | 01:08 | Wincepb50-051231-kb912155-x86.msi | 775,168 | 06-Jan-2006 | 01: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. |
Fsreg.lib | 368,236 | 19-Dec-2005 | 18:57 | public\common\oak\lib\armv4i\debug | Fsreghive.lib | 440,996 | 19-Dec-2005 | 18:56 | public\common\oak\lib\armv4i\debug | Fsreg.lib | 237,722 | 19-Dec-2005 | 18:56 | public\common\oak\lib\armv4i\retail | Fsreghive.lib | 280,560 | 19-Dec-2005 | 18:56 | public\common\oak\lib\armv4i\retail | Fsreg.lib | 384,946 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii\debug | Fsreghive.lib | 459,184 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii\debug | Fsreg.lib | 242,832 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii\retail | Fsreghive.lib | 289,878 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii\retail | Fsreg.lib | 384,984 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii_fp\debug | Fsreghive.lib | 459,226 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii_fp\debug | Fsreg.lib | 242,890 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii_fp\retail | Fsreghive.lib | 289,948 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsii_fp\retail | Fsreg.lib | 393,776 | 19-Dec-2005 | 18:58 | public\common\oak\lib\mipsiv\debug | Fsreghive.lib | 468,354 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsiv\debug | Fsreg.lib | 244,620 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsiv\retail | Fsreghive.lib | 291,550 | 19-Dec-2005 | 18:57 | public\common\oak\lib\mipsiv\retail | Fsreg.lib | 393,814 | 19-Dec-2005 | 18:58 | public\common\oak\lib\mipsiv_fp\debug | Fsreghive.lib | 468,396 | 19-Dec-2005 | 18:58 | public\common\oak\lib\mipsiv_fp\debug | Fsreg.lib | 244,682 | 19-Dec-2005 | 18:58 | public\common\oak\lib\mipsiv_fp\retail | Fsreghive.lib | 291,626 | 19-Dec-2005 | 18:58 | public\common\oak\lib\mipsiv_fp\retail | Fsreg.lib | 315,632 | 19-Dec-2005 | 18:56 | public\common\oak\lib\sh4\debug | Fsreghive.lib | 381,058 | 19-Dec-2005 | 18:56 | public\common\oak\lib\sh4\debug | Fsreg.lib | 215,358 | 19-Dec-2005 | 18:56 | public\common\oak\lib\sh4\retail | Fsreghive.lib | 258,696 | 19-Dec-2005 | 18:56 | public\common\oak\lib\sh4\retail | Fsreg.lib | 306,024 | 19-Dec-2005 | 18:56 | public\common\oak\lib\x86\debug | Fsreghive.lib | 370,270 | 19-Dec-2005 | 18:56 | public\common\oak\lib\x86\debug | Fsreg.lib | 201,262 | 19-Dec-2005 | 18:56 | public\common\oak\lib\x86\retail | Fsreghive.lib | 237,364 | 19-Dec-2005 | 18:56 | public\common\oak\lib\x86\retail |
WORKAROUNDTo 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.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbBug kbfix kbQFE kbpubtypekc KB912155 kbAudOEM |
---|
|