Yes. You can block it in a firewall, so it does not call home even after install. It is too complicated to maintain. I prefer to download the installer and hold enter and I am done within seconds no need to extract anything, etc.
I dont use firewalls other than Windows. I guess the task can be deleted, just have to remember to do it every time I update. I might try the portable version some time. I used the portable versions of Foxit and Libre office for years, and feel comfortable using them. No difference using portable or the regular versions. Bo
Exactly: https://www.wilderssecurity.com/threads/ccleaner-v5.370654/page-28#post-2714760 I generally try to use portable versions of software. Less gumpf in the system / registry, doubt if there are any downsides. (That said, my main Firefox is an installed version).
Too bad that updater is installed and task added even if you disable option for update check during installation.
Didn't work that way for me. The update program was installed, but no task scheduled. So, unless the core program is directly invoking it, the updater is just a few useless bytes. I've never configured for auto-update, so maybe that's the difference.
I did the same but updater is installed and task added. https://www.wilderssecurity.com/attachments/autoruns-ccupdate-jpg.258884/ You better check your system not via Task Scheduler but via "Autoruns for Windows" with administrator rights.
Yes I also never configured auto update (always disabled it during install). Well this time updater was dropped and task scheduled even if I disabled auto update during install. It doesn't mater to me. I will block internet connections for that binary and also block it's execution in SRP (or using ACL).
Not really. Just have a definitions file. It's what the .ini files are for. No need to keep changing the executable.
Just a word of caution though, especially if you are using Firefox. There have been recent 'under the hood' changes which have necessitated changes to the executable. Using an outdated executable could cause problems. Previously, updates (initially overlooked) have also had to be made for Internet History for FF also resulted in favicons for bookmarks being removed on some computers. Default cleanining rules for Explorer have also changed.
Is the favicon issue fixed 100% with this version? Have you upgraded, and tested? https://forum.piriform.com/index.php?showtopic=48688&p=285717 https://forum.piriform.com/index.php?showtopic=48754 https://forum.piriform.com/index.php?showtopic=49042&page=1&#entry287669 As up to 5.35, it was not fixed. Bo
No, hopefully in the next release though no guarantee. refer https://forum.piriform.com/index.ph...c856b2cb55&showtopic=48688&page=2#entry287868
Thanks here too. I have upgraded, but I have favicons.sqlite* files excluded, so was not aware it wasn't fixed yet.
I didn't check with admin rights, so you're right: it did install. I'll have to remember to disable it after updates, but I think I'm going to ditch the Piriform utilities, anyway. I use AIDA64 and SIW rather than Speccy. Defraggler is the slowest defragger known to man. It's only CCleaner that I actually use on a frequent basis. I'm leaning toward switching to Wise Disk Cleaner, instead.
I have thought about it, but it is irreplaceable, it cleans browser's stuff, that other cleaners do not. I particularly use it to clean cookies. Extensions (Cookie AutoDelete) do not work.
The cookie whitelist in Wise Disk Cleaner appears to be equivalent to CCleaner's, though I haven't yet tested it carefully.
Reverted to 5.62 and all versions is always asking for Outbound connection, which i block. No reason except to spy. Check for updates unchecked. Going to throw ccleaner away.
CCleaner version 5.37 now out. https://www.piriform.com/ccleaner/builds MD5 and SHA-256 file hashes https://forum.piriform.com/topic/49170-ccleaner-v537/?do=findComment&comment=288548 (wrong build number showing but hashes are correct) EDIT... build number has been corrected for the hashes now.
After update scheduled task for auto update was re-enabled. I guess I will have to check this after each update.