My OS: Vista Home Basic wSP1.
My setup.log of Avast Free 5.0.594 is about 16MB.
I have administrative privileges. If anyone could answer the following questions, I’d really appreciate, since I searched the forum but didn’t find the answer to them.
Do I need such a big setup.log for something?
Which actions are triggering setup.log to grow?
Is there any way to delete it?
I guess Avast will create it again when it finds there is no setup.log.
TIA.
Disable the avast self-defense module (Settings > Troubleshooting).
Delete the log.
avast will create a new one when it first updates.
Ady4um, you do know that you are using an outdated sevice pack, sp2 has been out for ages.
Thank you both.
About setup.log, does it grow for every virus definitions’ update?
About Vista, I know about SP2, but for the most part, SP2 is just the updates since SP1. There are other advantages, like having the possibility to delete the old SP1 install files after installing SP2. Since I already have every update, and the system is working fine, I think I’m only going to install SP2 if I have OS’s problems, and free time to reinstall from scratch 
One other thing you could do, rather than totally delete setup.log, is to (as I do) periodically edit it down to just the most recent entries (say the last 2 weeks or so). That’ll keep it down to a reasonable size (maybe 2-3 megs), and anything older probably wouldn’t be much help if troubleshooting is ever necessary.
It records information about all update checks, not just the ones that result in a virus definitions’ update.
@ ady4um
Go to PROFILE then Modify Profile then Forum Profile Information then Please select your country: then Signature: and put information about your system just like my signature about your system just like my signature so that the helpers can offer pertinent advice.
Remember Those Who Forget History Are Doomed to Repeat It
In other words those that do not keep their operating system up to date are VERY VULNERABLE TO INFECTIONS!
Witness the infamous Conficker attack a few years ago:
http://www.microsoft.com/security/worms/conficker.aspx