>Or you can use much better Registrar Registry Manager Lite

I think they wrote an extensive shell around the API. The thing missing here (as noted by the originator of this thread and obviously not advertised by Resplendence) is the ability to read stranded registry files from previous installations of Windowses, or their own backups. The API reads the registry hive currently in use. Available tools (I already bought some - just like in DOS days, Microsoft spawns an aftermarket for tools fixing their, ahem, design) can only backup the full registry an restore everything; which means that they can't extract settings related to one app, from the current or backed up registry. It's the whole file that would become current, or nothing.

I'm looking for such a tool for 15 years now, and I'm not holding my hopes high.

>>Only if your paths are exactly the same... you can open the current registry in regedit, navigate (manually) to the given key (no you can't paste a location anywhere, no such GUI there), then export the key or branch into a .reg file. Then take the .reg file to the other machine and import in regedit.
>>
>>If your paths differ anywhere, you can open the .reg file in any text editor (I guess it may need to be unicode capable, not sure) and edit it. Note that any backslash needs to be duplicated.
>>
>>You may also, as a precaution, export the same area from the target machine, so if it gets hosed, you have a backup.