Tuesday, July 24, 2018 -- CCleaner v5.45.6611
We're pleased to announce the latest release of CCleaner for Windows.
In this release, we’ve made stability improvements and added better reporting to allow us to deliver faster bug fixes and software improvements.
v5.45.6611 (24 Jul 2018)
- Removed Windows.old cleaning rule
- Fixed a crash in Disk Analyzer
- Added more detailed reporting for bug fixes and product improvements
Anyone who has updated to Norton v22.15.0.88 and previously created a custom program rule in their Norton Smart Firewall (Settings | Firewall | Program Control) to block CCleaner traffic through the firewall might want to check if access has been set back to Allow.
I received the Norton v22.15.0.88 update today via an Automatic Live Update and every single program rule in my firewall was deleted (i.e., as if I had deliberately reset my firewall). The first time I ran CCleaner today the firewall created a new rule for my 32-bit ccleaner.exe executable and set the access back to the default Allow.
FYI, I've decided to downgrade to CCleaner Portable v5.35 for now (released Sept 2017, after the bundled Floxif malware of v5.33 but prior to the Emergency Updater of v5.36, intrusive pop-up advertisements of v5.44 or the latest Active Monitoring fiasco of v5.45), since my Vista SP2 OS and FF ESR v52.x browser features haven't changed significantly since Sept 2017.
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * NS v22.15.0.88 * CCleaner Portable v5.35.6210
Today we have removed v5.45 and reverted to v5.44 as the main download for CCleaner while we work on a new version with several key improvements. You can grab version 5.44 from one of the links below:
[..]
As stated before, we'll split cleaning alerts (which don't send any data) from UI trend data (which is anonymous and only there to measure the user experience) and provide a separate setting for each in the user preferences. Some of these features run as a separate process from the UI: we'll restore visibility of this in the notifications area, and you'll be able to close it down from that icon menu as before.
We understand the importance of this to you all. This work is our number 1 priority and we are taking the time to get it right in the next release. There are numerous changes required, so that does mean it will take weeks, not days. While we work on this, we have removed version 5.45 and reinstated version 5.44.
Here is more info from betanews.com https://betanews.com/2018/08/01/do-not-install-the-latest-version-of-ccleaner/ Also from Ghacks.net https://www.ghacks.net/2018/08/01/ccleaner-5-45-dont-install/
We will separate out Active Monitoring (junk cleaning alerts and browser cleaning alerts) and heartbeat (anonymous usage analytics) features in the UI and we will give you the ability to control these individually. You will have the options of enabling all, some or none of these functions, and this functionality will be uniquely controlled from the UI.
We will take this opportunity to rename the Advanced Monitoring features in CCleaner to make their functions clearer.
We will deliver these changes to the software in the coming weeks.
I'm still not sure that will entirely address user concerns about scheduled tasks that continue to run in the background after the program is closed and/or minimized to the system tray.
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * NS v22.14.2.13 * CCleaner Portable 5.45.6611
Thanks for your feedback. We value your input and want to acknowledge your concerns around the changes to active monitoring (heartbeat).
The new CCleaner heartbeat reports only non-personal, absolutely non-identifiable usage information for the purpose of improving CCleaner. This could be, the percentage of users who have experienced a crash, or are using scheduled cleaning.
First and foremost, being able to detect usage patterns across our entire user base allows us to act more quickly when things go wrong. Gathering information via this forum, support tickets or social media is helpful but with such a huge quantity of users, is not a small undertaking. The new 'heartbeat' delivers quantifiable, representative data, quickly, so when things go wrong, we can rectify the situation sooner. In the long term, having some insight into how our users use CCleaner allows us to improve it.
The heartbeat has been added to an existing CCleaner process called 'CC Monitor'. That process is controlled via the Enable Active Monitoring checkbox. This option covers both checking for updates and the new heartbeat. It has two other optional features: 'System Monitoring' and 'Browser Monitoring'. System Monitoring triggers an alert when you have a lot of junk to clean. Browser Monitoring is a paid feature that gives you intelligent cleaning options when you close your browsers.
After listening to your concerns, we have reviewed how this feature has been implemented and we agree that there are areas for improvement.
Please bear with us while our product and development teams work on this. We will update you as soon as we can. In the meantime, to disable all monitoring, please close all CCleaner processes via the Task Manager.
Thanks for your patience while we work towards a resolution.
As mentioned above, there are several posts at the CCleaner forum and from what I've read, no posts by any developers / employees, so I'm beginning to think this is by design and not a bug....
The heartbeat has been added to an existing CCleaner process called 'CC Monitor'. That process is controlled via the Enable Active Monitoring checkbox. This option covers both checking for updates and the new heartbeat....
After listening to your concerns, we have reviewed how this feature has been implemented and we agree that there are areas for improvement.
Please bear with us while our product and development teams work on this. We will update you as soon as we can. In the meantime, to disable all monitoring, please close all CCleaner processes via the Task Manager.
Thanks for your patience while we work towards a resolution.
I posted some feedback <here> in that same thread on how my CCleaner Portable v5.45 is behaving, but as far as I can tell my setting at Options | Monitoring | Enabled Active Monitoringremains disabled after CCleaner is closed and I can't see any obvious signs that the 32-bit CCleaner executable (ccleaner.exe) is still loaded in memory after the interface is closed or that any tasks associated with CCleaner were created in my Task Scheduler.
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * NS v22.14.2.13 * CCleaner Portable 5.45.6611
As mentioned above, there are several posts at the CCleaner forum and from what I've read, no posts by any developers / employees, so I'm beginning to think this is by design and not a bug.
Monitoring looks okay, for me.
