…just found out, after updating it to version2.36.1233 >>> included on my system are Avast5 and MalwareByte. Haven’t used mbam for a while so there was nothing to delete, but usntr.log (persistence cache log file) was included for Avast. As it’s not protected by the self-defense module, that was easy. This said that’s just a log file, this won’t break your Avast…but it might be needed for troubleshooting purposes…well sometimes, mainly during beta testing phases. They must have considered that the file contained private data…which is probably true but okay, just wanted to mention that and send a little warning
ps: other Avast log files are protected, so they can’t be deleted like that.
I unchecked the Avast5 option in the Applications section right away, whilst it shouldn’t be able to delete protected files, I can’t see it needing to delete any avast files. The deletion of the usrntdat.log (not usntr.log) would be pretty pointless (would slow subsequent scan) and in my system this is 1KB. The nsrnt.dat is 256KB, neither of which I would want ccleaner playing with.
I have MBAM but there is no check against that option, I can’t recall is this option was there before and I unchecked it for the same reasoning, I don’t want ccleaner playing with any security based application.
No malwarebytes wasn’t there before, ccleaner has alway’s cleaned defender well so there just adding some popular av’s and scanner’s now and i find it did well and hasn’t harmed anything, i did an update and tried a reboot and firewall settings have not been touched but it deleted 28meg of un’needed old file’s so im happy. Oh and my full scan just finished at 17mins which is what it is usually.
They are adding them in what they are calling Utilities , which at the very least is a major misclassification and would lull people into thinking there is no downside.
You didn’t say what these files were - I don’t know how you managed to accrue 28MB of old avast files as there is a housekeeping routine to keep the major logs down to a workable size, whist retaining enough information should it be required for debugging, etc.
Can confirm that it did reset my update timing back to 240 min and my virus chest size was reset also so iv turned it off now anyway, no harm done and i like to experiment and now i know what it does.
Posters above refer to CCleaner 2.36 deleting files usrntdat.log and usntr.log.
First of all, I could not find file usrntdat.log in my machine, only usntr.log.
And, second, CCleaner 2.36 did not delete usntr.log, with Avast! Antivirus 5 “utility” checked.
As a side note, I remark that the transient cache is not working correctly here (both caches checked). Files keep being scanned repeatedly, even after two subsequent uses only seconds apart. For large files, this is quite a nuisance! Might the absence of the file usrntdat.log have anything to do with this problem?
No it didn’t delet the log file it just cleaned it, just tried another scan now and it completed in 11 min’s. I only have one option ticked under persistant cache.Transient cache is ticked also.
well as far as I know this is just a log file, meant to refer to to get information, but in no case used by Avast to operate anything. It just contains the persistence cache log, therefor is seen by CCleaner as directly relating the content of your hard disk. Deleting it won’t change the behavior of anything, won’t reset anything…hey, it’s not a setting file (aka *.ini), and again, it’s the only log file that’s not protected by the self defense module explaining how CCleaner can delete it. The persistence cache files themselves won’t be affected obviously. As to the 28 MB size, yes, the longer it’s been used, the bigger it becomes. Same here on my system.
ps: now I’m ready to hear from an Avast dev if this file has any other impact, I can be wrong of course.
edit: hmm David, the usntrdat.log doesn’t exist ;D >>> you might have been thinking about the actual persistence cache dat files. Noone has ever said that those would get deleted …which would indeed be completely stupid.
edit: just seeing now as expected in the selfdef.log file that access was denied to the other log files.
edit: other log files get actually deleted (not all, two are protected), seeing it now. I most likely deleted them in a previous run of CCleaner without looking at the result pane, and as they got re-created, they’re targeted too >>> screen shot.
The largest log it clears is aswAr 1.log which is the one that deleted 28meg off my machine last night, just ran another scan and there is a further 17meg to be cleaned from the same log file but i think i’ll leave it.
The aswAr1.log in my C:\Documents and Settings\All Users\Application Data\Alwil Software\Avast5\log folder is only 1,856KB. So I don’t understand how yours keeps getting so large as it should be overwritten each time the anti-rootkit scan is done. You must have masses of data on your system ?
Only got 366meg in add remove program’s and every thing else is kept on external hard drive, just scanned with ccleaner then and it shows another 17000KB in the aswAR1.log, everything runs good and fast so it must be the normal size for my machine.
Yes as the anti-rootkit does check a lot of files, though it is surprisingly quick at it, mine is normally very quick, 27 seconds for shed load of files scanned.
My on-demand Full System scan only does the Rootkits (quick scan) so I guess if a) your system has more data, b) or you are doing a custom scan where you elect for a Rootkits (full scan). Either of these may mean more data is being scanned.
…which would indeed be completely stupid.