Running 4.8.1216 but happens on the current release too. Vista x86 with SP1.
Example:
When I click on my Start Menu then click on All Programs then just open up an entry and just point to an executable it is scanned by the Standard Resident Shield.
All I have checked off for this shield is to scan executed programs, nothing else. Obviously just placing my cursor over the entry does not execute it IMO.
My understanding of SF is that the loading takes place when Vista is booted up. Could be all the Start Menu programs are preloaded and avast! interprets things incorrectly, ie the program is being executed when pointing the mouse over one of these programs. Just grasping at straws here.
If you place the pointer over an executable in Explorer no scan is done as far as I’ve seen.
What you don’t mention is what sensitivity setting you have the Standard Shield on (Normal is the default) ?
I don’t see any such activity when having a rummage through the All Programs, though a) I’m not using |Vista and b) the standard shield is on Normal sensitivity.
Actually all I need to do is open the folder in the All Programs list and avast! will scan all the executables. I don’t need to point to anything in the folder.
I also see this with ObjectDock where I have a folder that contains shortcuts to my different programs. It is a drop down menu and it opens slowly the first time I click on it. Avast! is scanning for executables. However it doesn’t always do the scan after the first time.
Some time ago I’m sure there was something like this where when you opened folders, exe files were opened so the icon could be extracted and displayed in windows explorer, I don’t know if this could be a possible if it is checking/opening the target.
I checked and it doesn’t work like that for me (no scanning you describe occurs).
So, what exactly are your Standard Shield settings? Scan files on open - disabled, Scan created/modified - disabled?
Do you have any application installed that might “touch” the files you open from the menu (don’t know, some special skinning, themes stuff… or maybe some other resident security application that might trigger the access)?
Standard Shield has everything disabled except for the scan of executed programs and the 3 items under it. I also have the option enabled to show details on performed actions.
I just installed the demo version of 4.8 pro on a vanilla Vista SP1 system I run under VirtualPC. It behaved just like my ‘real’ machine. The target program in folders with shortcuts are being scanned when the folder is opened.
It seems that once a folder is opened and scanned I can open the same folder without it being scanned for a time. Eventually it gets scanned again.
Keep in mind I am running Vista Ultimate x86 with SP1.
It’s a Vista phenomenon.
Following Streetwolf’s initial post I checked the Standard Shield box “Show detailed info on performed action” on a Vista Home Basic SP1 machine to see what happens. As I clicked on each “folder” in the Start Menu, the full path of each of the shortcuts was listed in the pop-up as having been scanned by Standard Shield. XP does not behave this way even if I set the Standard Shield to scan “All Files”.
Just click on one of the folders in your Start Menu under All Programs. Just about all of them have shortcuts. Also make sure you set the option in the Standard Shield to ‘show detail on performed action’ so you will see the popup
I’ve debugged some Vista system libraries and found out, when shortcut files are read, their EXE files are opened with the same method which is used for execution. In general, it’s not even so easy to identify when a process is going to be launch. Standard Shield doesn’t know it; it only assumes the opened file may be used for execution. Unfortunately, Vista opens those .lnk files (and .exe files) with the same flags which are used for execution. Anyway, these EXE files are scanned just once - rescan will only happen if they are changed.
PK
Does this mean that the performance impact of any AV’s on-access scan engine will be amplified in propertion to the scanner’s inefficiency by Vista’s inherent “Linkscanner”-like behaviour?