CCleaner 3.12.1572 Now "Cleans" avast! By Default

Does anybody know exactly what CCleaner cleans in avast!? I updated CCleaner today, and it now has avast! as an option, and it’s checked by default. I chose to clean avast! and it removed 18mg’s of something, what, I don’t know… Anybody?

They are only the avast temp log files which are harmless but i still prefer to untick security software app’s in my list just in case.

Old log`s…i am guessing!

Anything Ccleaner cleans should be clearly listed. After clicking the Analyze button, double click on the Avast! entry from among the list of cleanable items. This should bring up the details you want.

As mentioned, its probably temp files, logs, etc.

you got a reply ;D

http://forum.piriform.com/index.php?showtopic=34201&hl=avast&fromsearch=1

If you first just chose “Analyse” and double click avast!6 line you will see all items to be cleaned.
It also works if you double click the line after cleaning but then it is definitely too late to decide!

Hi,

As craigb and Pondus mentioned here, those can be old log files from avast!. But its recommented not to check that option. Those files may be usefull in future.

Have a wonderful day. Good Karma!

Good info everyone, thanks! I did not know that I could double click an entry to see more specific info. I trust CCleaner, but it just seems weird to clean my AV!

I mentioned the following before:

if any Avast user would go to Piriform's forums or contact page and suggest to add Avast 6 (with the current default path), they would probably do it, and there shouldn't be any conflicts.

And then http://forum.piriform.com/index.php?showtopic=34091&view=findpost&p=203350

So after that request they added Avast 6 in CCleaner with no conflicts. :o :slight_smile:

This of course has nothing to do with me. The reason I mention this is because I would have change at least 2 things.

First, I would NOT have added Avast with the “default=true”, but with “default=false”.

Then, as originally requested in that post I linked to, I would also add the “report” folder too, not only the “logs”, and I would extend this addition to older Avast versions in CCleaner’s items. IMHO this second change / request would be valid ONLY if the “default=false”.

I have no idea why they don’t add the reports too, or why they set the default as true for Avast.

avast did not do the job. Housekeeping was necessary and they don’t pay attention to that.
Now, a 3rd party tool is just showing how the housekeeping is necessary.
Pay attention to the numbers!

Well Ideally you want to stop the creation of the unp99999999.mdmp files to avast as I believe these are error conditions (and probably why they remain), which it would be better to fix the problem than the symptom.

I don’t have any of the logging9999999999.log files in my Log sub-folder (image1), so I don’t know if you have something like debug logging enabled, are these files created daily ?

You could also restrict the size of these user log files in the avastUI, Settings, Maintenance section (image2) I have mine set to 32KB and that may account for the multiple Mail9999999.log files.

I don’t have CCleaner clean any avast area.

I just accepted the CCleaner default and let it clean the Avast log files. I haven’t noticed any change in how Avast runs since the files were cleaned.

By the way, Wise Disk Cleaner in their advanced cleaning section identifies these files for cleaning after a scan but when you hit the “Clean” button it doesn’t appear to clean them.

Good for CCleaner :slight_smile:

@Tech and DavidR,

I’m not sure I understood your posts. I mean, I know what those temporal files are, but I don’t understand why you are bringing the issue.

In my case I don’t have leftovers / remnants, and my logs are not near those big numbers of MB. I thought that this topic was about CCleaner’s capability (and what can’t do) in relation to Avast, and less about the “big” MB of cleaning logs. Moreover, I’m not sure CCleaner can clean all those tmp files of Avast by default (and if it can, it is not related to the Avast item itself in CCleaner). But maybe I misunderstood the main issue of this topic.

Generally it is in line of what is or isn’t cleaned by ccleaner, as I said I don’t see anything in ccleaner that is cleaning any avast location by default (but I still have ccleaner 3.11.). I totally disagree with allowing ccleaner clear any avast logs as they are a useful user and debugging tool.

Tech is reporting what isn’t being cleared by avast housekeeping, which he is having ccleaner clean up in the avast locations. My point to him is he could probably limit what is there in the first place to be cleaned by ccleaner.

@DavidR,

Thank you. Now I understand what you meant (and that you were specifically talking to Tech).

I agree with you about not letting CCleaner automatically clean Avast logs (nor reports, if they decide to add those also). That’s why I said that the “default=true” for Avast is a mistake from Piriform IMHO.

Still, I don’t know why they decided to add the logs only, but not the reports.

I think that I can see their logic in not dealing with reports as they probably feel they are generated by the user.

But they certainly shouldn’t add anything to default settings they should have a god understanding of what the logs are used for.

@DavidR,

I understand your point (almost an educated assumption). From the link I posted, they decided to take in the “default=true”, but leave out the “reports” cleaning. I would have done it the other way around: throwing out the “default=true” (setting “default=false”) and including the reports. BTW, I would have done that for all previous Avast’s versions too.

I personally don’t see any difference in the criteria. If Piriform adds the logs, then should also add the reports with the exact same criteria. Again, the “correct” ;D criteria would have been to include both but leave it as “default=false”, so to keep being “conservative” in the criteria, but giving more power to the users.

Ideally. I never get any help on the avast dumps and logs…

I did some testing and CCleaner also removes all stored data from a full scan. The first time I ran CCleaner on avast!, it cleaned 18MG’s of something, and each time after that, it only cleaned a few KB. Today, I used CCleaner to clean everything, including avast!, then I did a manual full scan, and it took 8min longer then normal (29 vs 21). Then after avast! finished I analyzed with CCleaner, and what do you know, there was 18MG’s again waiting to be cleaned…I have unchecked the avast! box, and will not clean it again. It defeats the whole purpose of avast! storing files in the persistent cache.