Avast! has been a pleasure to use for the brief time I have used it.
I had previously used ESET Security Suite (ESS) and ESET NOD32 for years. However, an innocuous third party software installation completely fubar’d ESS. I was unable to reinstall ESS and left with a dilemma of either repopulating my hard drive from scratch or trying an alternative.
Avast! installed easily and has performed flawlessly. Honestly I expected nothing less, based on reviews and evaluations of Avast!
Apparently, at least part of the problem I had with the ESS installation was because the 3rd party software changed the “Environment Variables\Path” entry, found in the System Properties under the advanced tab.
That issue has been corrected. However, in light of the fact that I am extremely satisfied with Avast! at this point, I feel no other changes are necessary and will Carpe Diem and jog on. LOL
Which brings me to my question … Are there any files such as log files or installation files that can be deleted or could be periodically cleaned up as part of good house keeping, so as not to grow so large over time?
I have used the Avast! “Log Viewer” feature to delete contents of certain log files, but wondered if there were other files that needed manual attention. Thanks !!!
Can’t think of any, apart from periodically checking and cleaning the “infected” section of the chest, which I have hardly ever bothered to do, as it never contains much.
But, reason I’m posting is that you may find it worthwhile to run the Eset uninstall tool, info and download here (with credit to fredvries.)
Thanks for the links Tarq57 !!!
There were some legacy registry entries that I had previously been unable to manually uninstall or was unaware of actually … the uninstaller took care of that
At one time I used to periodically trim setup.log (there’s two copies, in separate avast sub-folders) down to the last couple of weeks, since otherwise it could grow to quite a few megs. And it apparently wasn’t affected by the log-size settings in program options.
But sometime relatively recently, say within the last year or so, Alwil must have changed how that log works, since its size now seems to be holding fairly steady at a little over 100K.
It is that file that caused me to start this thread in the first place. I figured since that file was not controlled by program options or available user interface, there may be others.
Nice to know that trimming that file will not, or should not affect performance.
Currently the setup log file on my machine is only 171KB. I have been keeping an eye on it. I’m interested to see how large it will get.
You’re quite welcome. Note that you’ll have to temporarily disable avast’s self-protection feature (program settings/troubleshooting, at or near the bottom) in order to save the amended log file, just don’t forget to re-enable it afterwards.
As I’d noted in my first reply, there should no longer be a need to trim this file, but it might behave differently on others’ systems.
