Jump to content
CCleaner Community Forums

Avast!


CeeCee

Recommended Posts

How many of you know, that Avast! will run Anti-rootkit scan on Windows startup by default? LOG file is placed in C:\Program Files\Alwil Software\Avast4\DATA\log. If you want, here's the way to disable rootkit scan on Windows startup: http://support.avast.com/index.php?_m=know...ratingconfirm=1

 

Another thing you might not know, is that some Avast! LOG files are locked and can't be deleted (not even by using Unlocker program). This is because of the self-defence mode. You have to temporarely disable it to delete LOG files. You can disable it by going avast! Program settings -> Troubleshooting.

 

Of course, some of you already know these things, but some might not.

Link to post
Share on other sites
How many of you know, that Avast! will run Anti-rootkit scan on Windows startup by default? LOG file is placed in C:\Program Files\Alwil Software\Avast4\DATA\log. If you want, here's the way to disable rootkit scan on Windows startup: http://support.avast.com/index.php?_m=know...ratingconfirm=1

 

Another thing you might not know, is that some Avast! LOG files are locked and can't be deleted (not even by using Unlocker program). This is because of the self-defence mode. You have to temporarely disable it to delete LOG files. You can disable it by going avast! Program settings -> Troubleshooting.

 

Of course, some of you already know these things, but some might not.

I noticed that option about the RootKit scan in Troubleshooting. If it is doing the scan in the Free version then the scan is very quick as my start-up times have not increased that I am aware of.

Yes, it is comforting to see those files even after a CCleaning.

Thanks for the information. It is comforting to know that even Unlocker can't touch those files.

:) davey

Link to post
Share on other sites
If it is doing the scan in the Free version then the scan is very quick as my start-up times have not increased that I am aware of.

I didn't notice any difference. I just noticed this thing from the log file. I have disabled this startup scan for now. Might enable it again later though.

Link to post
Share on other sites
  • Moderators
Another thing you might not know, is that some Avast! LOG files are locked and can't be deleted (not even by using Unlocker program). This is because of the self-defence mode. You have to temporarely disable it to delete LOG files. You can disable it by going avast! Program settings -> Troubleshooting.

I didn't know about the rootkit scanning on startup, which I think is a very good ideal.

 

I did however know about the self protection it has as no cleaning tool can touch it. When I last used Avast and was going to update the CCleaner winapp2.ini cleaning routine for it then just left well enough alone because I didn't think it would be a very good ideal to recommend people disabling the protection just to clean a few measly logs that aren't hurting anything.

Link to post
Share on other sites

Um this is what a help file is for. The root kit scan on start up is clearly pointed out in the help file. I knew about it 1 hour after I installed Avast. Never stops amazing me the people that will use a program for years and not know many of it's functions because they didn't bother to read a help file. Since Avast has such a disgusting GUI you really need to read the help file to learn all the features. It's definitely not an intuitive GUI like Avira AntiVir is.

Link to post
Share on other sites
because they didn't bother to read a help file.

My "bad habit" is that i rarely read help files. But i usually go through the program settings and learn that way.

Link to post
Share on other sites
No offense but you obviously didn't learn in this case. It's clearly pointed out to.

 

c54c4c868387.jpg

True. Strangely i somehow missed it. Btw, i can't see the picture, but i think what you mean.

 

Edit: i had to enable referrer to see it.

Link to post
Share on other sites

New info about this rootkit boot scan. This is a response to me on Avast! forum:

 

It isn't run at boot, but 8 minutes after boot to enable any boot activity to complete, allowing a comparison to be made against what is actually running and what is reported as running.

 

If you found the C:\Program Files\Alwil Software\Avast4\DATA\log\aswAr.log you will also have found that the scan takes seconds, my last one took 3 seconds (start time at top and finished time at the bottom of the report).

 

Well, i think i enable it after all...

Link to post
Share on other sites
Of course, some of you already know these things, but some might not.

CeeCee, I am glad that you started this topic.

(removed by davey).

:) davey

 

P.S. Oops!!! Sorry Hazel,topic related but wrong forum.

Link to post
Share on other sites
  • Moderators
New info about this rootkit boot scan. This is a response to me on Avast! forum:

 

It isn't run at boot, but 8 minutes after boot to enable any boot activity to complete, allowing a comparison to be made against what is actually running and what is reported as running.

 

If you found the C:\Program Files\Alwil Software\Avast4\DATA\log\aswAr.log you will also have found that the scan takes seconds, my last one took 3 seconds (start time at top and finished time at the bottom of the report).

 

Well, i think i enable it after all...

 

This is the best bit of info in this already pretty good thread. Nice one CeeCee.

Link to post
Share on other sites
This is the best bit of info in this already pretty good thread. Nice one CeeCee.

Thanks. Just checked from the log and my last scan took 7 seconds. So it's basicly nothing. Better keep it enabled.

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...