Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Solomon on May 13, 2007, 10:48:26 AM

Title: Blocker function. What other file types can I add besides default set?
Post by: Solomon on May 13, 2007, 10:48:26 AM
Was wondering besides the normal file types that are blocked using the standard default set, what other file type extensions can I add to the blocker function?  Is there a limit?
Title: Re: Blocker function. What other file types can I add besides default set?
Post by: DavidR on May 13, 2007, 02:40:45 PM
Personally I would leave this alone as it doesn't really have any effect unless you also tick the operations that should be blocked for those files.

By default the Blocked Operations: are unchecked so none are blocked, you would be surprised how much this could get in the way of your normal use of your system.

Basically the only files that are in the default set are executable ones, that feasibly be able to carry out one or more of the blocked operations. So there would be little point adding non-executable files to the list.

Title: Re: Blocker function. What other file types can I add besides default set?
Post by: Lisandro on May 14, 2007, 07:49:00 PM
Appart from the fact that the Behavior Blocker is an old feature and it's usefullness is very limited in today's Windows environment. It is a blocker of suspicious behavior (thus preventing an unknown virus to spread).

Almost all the actions on your computer are performed by .exe files. If you prevent .exe files from executing their actions (such as opening a file for writing), you block almost everything - Word won't be able to write the .doc file, e-mail client won't be able to save the downloaded e-mail, programs won't be able to store their settings. The operation "opening a file for writing, performed by an .exe file" is very common and there's nothing suspicious about it. On the other hand, the operation "opening an .exe file for writing" is much less common and more suspicious (actually, I think it's even more suspicious when it's performed by a file with .xyz extension - that cannot even be started in an ordinary way - than by an .exe file). It will prevent files (like BAT,VBS,WSH,SCR,EXE...) to execute their actions.