this is one of the most serious software intrusions I have ever seen. So guess Piriform/Avast are now on final notice from this end of the planet - seriously raise your game or be happy with losing credibility and customers. Pretty sure I opted out of any background reporting as well. Then there's this little gem of information on how CCleaner appears to have another unsavory issue relating to this Monitoring debacle: I'm not sure which of those is actually worse. Honestly, such a problem simply demonstrates a chronically critical (and blatantly obvious!) error that Piriform have either deliberately added in, or have chronically demonstrated that their Software QA/Testing Team need a good solid kick between the uprights. I actually came in here to add to the increasing list of concerned/annoyed users reporting this recent issue of Monitoring in 64-bit Windows refusing to stay disabled in the past couple of releases. And after demonstrating how that package refused to play in a fair and open manner to a significant percentage of my paying client base (both private and corporate/business users) Avast will be losing customers down this end of the planet for that product.

Off topic, but with the way Avast Antiviral insidiously operated in the background over the past few versions (as well as magically misreported non-existent issues requiring 'Upgrade To The Paid Version To Solve These' - ?), I've recently ditched that software package in all of my own systems. Ooooooh, I'd forgotten Avast had their fingers on the keyboards with Piriform. The 32bit version doesn't appear to display the same issue. If the OS is 64bit, then yes it does - so just rename the CCleaner64.exe program to something else and then as the program cannot be found it cannot be run. My comment above 'Curiously the CCleaner.exe version appears also to run the 64bit version' It's very disappointing and I trust this error is not a sign of things to come! These are just workarounds - AVAST should fix this problem. (Note: Also with Windows 10 - 1803 on a 32bit PAD)īut initially the CCleaner.exe program does load the CCleaner monitor and this needs to be deleted from the Registry else it will initialise at start up - though you can stop it running at the UAC prompt. With Windows 10 - 1803 the same functionality occurs as with Windows 7 above.

The version is still V545.6611 and both are in the CCleaner program folder.Ĭuriously the CCleaner.exe version appears also to run the 64bit version - at least that's what it says - if you believe anything anymore.

With Windows 7 what I have discovered is that if you run CCleaner.exe (13364kb) rather than CCleaner64.exe (18100kb) the program seems to deactivate the monitoring as requested and keeps it deactivated. I posted this a few hours ago on topic #52341 - it's relevant to this topic too - I hope it helps.

Do i need ccleaner monitoring