We are a small software company that creates custom DLL’s for a number of companies. In the course of testing, we occasionally have to register a set of DLLS without unregistering the previous set of DLL’s, creating orphan registry entries. Up until this point, we’ve advocated using a registry clean tool, but last week someone using Registry Mechanic lost their ability to maintain Symantec applications (and we rely on quite a few of these for VPN) due to something done by the registy cleaner. Apparently, MS and Symantec recommend categorically against registry cleaners, because of the potential of service release creating registry entries not properly anticipated by the “cleaner” getting “cleaned” and then causing the system to fail. I looked carefully at Registry Mechanic, and the tool had some bugs even saving the customization settings I tried to configure. I do not think it is trusworthty, desite it’s position in the market. Can anyone recommend a way for us to get rid of our orphan registry entries with a minimum amount of intervention to the rest of the registry? What would be ideal is something where we could circulate a settings file that would cause the tool to focus on the one thing we need it for– orphan entries — without corrupting anything else.