jhvance

Will incorporating those registry entries eliminate as well the recurring nag window to purchase Software Updater for a $10 discount? Edit: It seems so, as there have been no further popups of that nag window since I made the registry changes on either of my Win10H machines!

There was an instance of the updated version's installer which remained in Task Manager despite the toggle of that "Abort" switch (thanks for that -- the developers might want to correct the oversight), so I terminated it and tried the installer again -- no joy, as the same behavior repeated. So, I again terminated the process tree in Task Manager, then rebooted and tried it again -- no joy, again. So, a complete uninstall was in order. That older machine still has a registered version of Revo Uninstaller on it, so I launched it with subsequent instruction to root out the CCleaner installation completely under an "agressive" profile; once that ran through the Piriform uninstaller and found remaining dregs, I deleted all of those (one of which was the offending file, ccleaner64.exe -- that sucker was a lot more resistant to removal than I would ever have thought normal for non-malware) and again rebooted. No sign of CCleaner, so I could try a completely fresh install, which seems to have worked so the issue-du-jour can be marked as "resolved". Does make me wonder about the recent trajectory toward more user-unfriendly behavior on the part of this long-utilized app with the transition to Avast's umbrella, though...

I've just downloaded and installed the latest version (v5.54.7088) on three computers, with no problems on one Win10H laptop but issues on another Win10H laptop and a Win7Ult desktop -- on the latter two, the installation process stopped when the executable ccleaner64.exe was attempting to overwrite the existing file. In all cases, I had begun by simply launching the installation executable (stored on an external thumb drive) using the Start|Run option. The error message box which pops up gives an option to abort, retry or ignore -- retrying generates the same error, ignoring leaves to previous cclearner64.exe file in place so the installation isn't fully updated. I've been able to correct the issue in the Win10H machine by aborting, then rebooting and using Windows Explorer to drill down to the installation executable, then right-clicking to "run as administrator" -- this seemed to resolve whatever permissions issue was present in the original attempt on that machine, but it didn't work on the Win7Ult desktop. There wasn't an issue on the other Win10H laptop, so now I'm left with a problem on the older OS. Any thoughts?

I've been a CCleaner user for much of the past decade, and have always considered it reliable so routinely have upgraded when new versions are posted to FileHippo and the morning bootup reveals the one installed on my different computers needs replacing. I followed that protocol again with the 5.45 release, but rather quickly discovered that it was crashing on both Win10 and Win7 machines -- figured it was just a foible of something in the release that hadn't been fully beta-tested and so proceeded to uninstall that new release and re-install the functionality of v5.44 until there was a subsequent update notice. Just discovered this bit of news about Piriform becoming part of Avast and the intrinsic problems with the active monitoring setup -- not at all sure that I'll make the effort to upgrade when there's a new release, but will certainly wait a few days and read through the forum posts to make a final decision. Sad...really sad. The demanding thirst for monetization through analytics has imposed such near-requisites for covert exfiltration of user information to satisfy the bottom line from what had been reputable and trustworthy firms, but that list is rapidly shrinking to a vanishing point.