Some of the lines in the above test set triggered the "Automatically select the best possible solution" and "Select the solution manually" options.
(Posted as a place holder. Will restore the entire test set to identify those lines, and then determine what they did ... It's not easy because the custom fix window cannot be resized ... :) ) As it turned out, it wasn't easy for other reasons ... see below ...
The following behavior occurred:
Restored prior backups -- ran RC -- list showed 4 Obsolete Add/Remove menu entry (OA/Rme), 33 path\filename does not exist (dne), and 2 Useless File Extension (UFE) -- 39 total items.
Did Custom Fix for the 4 OA/Rme, no other lines were selected:
3 clicks on OK with "Delete the item" selected -- then 1 OA/Rme line dropped from the top of the list
1 more click on OK with "Delete the item" selected -- 1 more OA/Rme line dropped from the top of the list
12 more clicks on OK with "Delete the item" selected -- nothing appeared to happen -- 2 OA/Rme lines still showed at the top of the list and were still in the registry per regedit
3 more clicks on OK with "Delete the item" selected -- another line dropped from the list -- Whoa! it is removing lines that are not selected!
***
Continued clicking until all lines were off the list except 1 OA/Rme (it was the first on the list at the outset; custom fix would not remove it).
Reran RC -- that line was the only one on the list -- removed it with the Fix button -- regedit confirmed it was gone. The 35 unchecked lines were no longer in the registry (per RC list).
Checking backups:
The second backup was OK -- the 1 checked line removed (with Fix since Remove is not working) was backed up.
The first backup was not OK -- 2 of the three checked lines removed were backed up -- 1 was not. The 35 unchecked lines removed were not backed up.
Restored the backups in reverse chronological sequence (LOFI -- last out, first in) -- RC list only showed 11 lines.
Restored in actual chronological sequence (FOFI -- first out, first in) -- RC showed 34 lines -- 3 OA/Rme (1 was gone), 29 dne (4 were gone), 2 UFE.
Restored in arbitrary sequence -- RC showed 5 lines -- 3 OA/Rme, 2 dne -- other 29 were gone.
Restored again in FOFI sequence -- RC showed only 3 lines, the OA/Rme ones; closed PT, restarted it, ran RC, showed the same 3 lines.
Restored one backup -- ran RC -- it showed the 3 OA/Rme and 6 dne (3 HKCU and 3 HKUS "synonyms"). The single backup contained 21 items and no synonyms, so only 3 items were actually restored (based on what RC reported).
Created some more errors by renaming all the files (4) in wordpad's recent file list -- list confirmed with regedit -- ran RC -- it picked up 1 of these -- opened two files in wordpad's list -- wordpad said it couldn't find them and removed them from the list -- removal confirmed with regedit -- Ran RC again -- it picked up 1 of the two remaining dne in wordpad's list -- enough of this ...
Ran 2005 PT RC with all key options checked, Open With entry scan checked, MRU scan checked, rest unchecked -- it found the entries missed by the RC1 Registry Cleaner (didn't check it line by line but the entry names made it obvious).
Conclusion: many RC bugs revealed during this dialog, primarily in custom fix and backup creation (and of course error detection) ... think I'll wait for RC2 before digging further into RC ... please forgive that LOFI FOFI thing ...
Attention (added note): Somewhere in the above testing, Registry Cleaner, unsolicited, put 36 items in SuperRegIgnoreList.dat. Perhaps, at the point marked ***, it put items in this "super ignore list" instead of backing them up. Consequently, some (not all) of the observed unpredictable behavior can be discounted. Most importantly, backup and restore are working (for the most part)! After editing SuperRegIgnoreList.dat, Registry Cleaner error counts are back to an expected range.