2 ms·

Registry has some serious practical problems. How do I easily list, or copy to another machine, the settings for application X? For technical users these are th

Registry has some serious practical problems. How do I easily list, or copy to another machine, the settings for application X? For technical users these are the most important operations. I know how to view or copy a text file... An associated problem is that the registry accretes trash that is never weeded out (and it's hard to weed it out). Also at least in former times it was slow (partly because of the trash thing, probably partly because of the implementation, partly because of the centralised design).

ComodoHacker 10y ago
>How do I easily list, or copy to another machine, the settings for application X? with reg query, reg export and reg import commands, respectively. Or with a few clicks in the GUI, if you prefer.
Godel_unicode 10y ago
Right-click that program's config hive, export. Move file to new system, merge. I did this very frequently before PowerShell got amazing support for the registry (seriously, it's the best. Tab completion of registry values in get-childitem if you supply a registry path). > ...accretes trash If your app doesn't remove it's old settings when uninstalled how is that a problem for the registry to solve? It happens with /etc also. > hard to weed it out Search for the hives if you don't know where they are. Right-click the hives in question, delete. Registry usability got leaps and bounds better in Windows 7, and again in Windows 10. Most registry problems you hear about are holdovers from the bad old days (XP and older).