1 hour ago, testingtom said:
<div class="ipsQuote_contents">
<p>
Hurry before the mods snitch!! <span>:)</span>
</p>
</div>
? They're good, sensible people, I expect that parameter to be retired in the future though.
It wasn't used in 6.23 (obviously), but it's interesting that a 6.24 clean install only has 1 "(Cfg)XXXX" entry until it's run (and allowed Internet access, then there are some 40+). If it can't access the network, Registry cleaning is still one of the main menu entries, I thought they had moved it for good to the Tools section in 6.24.
It feels as if they are trying things and see what works for them (that ABTestingNames value implies as much), as if there were no clear course or direction for the program. Do they not have visibility about what's used and what's not? I don't think it takes much to see areas that could be improved ?
Man, I had never used / examined CCleaner as often as I have the past 2 days, and only because when I went to perform a custom cleaning it wouldn't work ?
16 minutes ago, Digital Jedi said:
<div class="ipsQuote_contents">
<p>
I can still choose to keep certain cookies when using Health Check. I mean, it's technically what I was already doing with Custom Clean. It's just a confusing way to put it.
</p>
</div>
"Basic cleaning" isn't defined anywhere that I know of, I wonder what they mean by it, but I don't think the Health Check option serves the same purpose as custom cleaning. I mean, at least in the custom cleaning section one can deselect things that don't want to be deleted or select others that are off by default. I suppose those using 3rd party definitions for what to clean through Winapp2.ini would also need to go to custom for that to work.
However... Smart cleaning (smart = automated if cleaning would net +X GB of free space) seems to use the same rules as "Custom clean", if that still works in the free version (don't know, I don't use it), what was moved to Pro was the ability to manually start the cleaning process? The free version has that enabled by default.