noname

When you do reg cleaning, you already run this risk. Very few people who do reg cleaning actually *check* what the tool remove, but they are aware it can go wrong. It can go wrong all the same regardless of the fact you can see a progress bar or not. If reg cleaning goes wrong, it's usually because the tool is too aggressive and picks up essential keys to delete.

And why not? Users should do whatever they like, if they do something wrong it's their problem. If a tool provides them with the means of making a mess, you can't blame the tool, can you? I think anything that can be automated on a computer should - then it's up to you to keep an eye on it or let it run unattended.

Hello, and thanks for your reply! Don't worry about deleting the other post, I rephrased my questions here. I understand the concern you raise, and I know that registry cleaning is something touchy. I thought that maybe it could be useful to advanced users, who are aware of the risk of reg cleaning but who still want to do it in the most non-intrusive manner. I thought about it because through a scripting language (the powerful autohotkey) and various utilities I've been able to completely automate my computer's maintenance, everything I deem useful is scheduled, junk files are deleted automatically, the registry is defragmented etc etc. The last step would be to have reg cleaning run unattended, then all clean-up operations would be performed absolutely automatically. I hope that it can be considered in the future, maybe with some extra warnings and disclaimers in the doc files. Cheers!

Hello, Why isn't it possible to run the registry cleaner unattended through the /auto command line switch? It would be extremely practical and would allow to have computer maintenance which is perfectly free from user input. Thanks a lot!