New
#11
Any automated registry cleaner carries with it a some level of risk and (in most cases) no performance gain.
But - cleaning the registry makes some people feel good - so CCleaner includes a very conservative registry cleanup tool.
If you have an application that did a poor job of uninstalling, then there can be junk left behind in the registry. If you let CCleaner clear out what it finds from that bad uninstall, then you manually search the registry for remains of that bad install, you will probably find junk that CCleaner does not clean out. CCleaner is just not that aggressive of a cleaner.
I would like to see someone benchmark the performance and restart times of a computer that has years of use, never had its registry cleaned by a "registry cleaner". Then use a tool like CCleaner to only "clean" the registry. Do not clear temp files or defrag the drive - only benchmark before/after "cleaning" the registry.
That said, there are a few registry entries that can cause start up delays. An automated registry cleaner might find those for you, or might not.
I've used CCleaner's registry "cleaning" tool because I learn from what it shows me and I'll accept the risk of what it could barf. I just don't suggest that others use CCleaner's registry "cleaning" tool.
Even CCleaner's temp file cleanup tool is conservative. There are a few types of temp files that it does not remove by default. (e.g. orphaned MS Office temp files - the ones that begin with ~$) I'm not even sure that CCleaner will get rid of those files ending in CHK. You tell us
As for which functions to safely use - run the cleaner and leave the other parts of the app alone. The other parts are good if you want to work thru some specific errors or problems with the help of those in this forum.