Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: spg SCOTT on May 14, 2011, 06:54:51 PM
-
So in the process of checking a site, I scanned a script (in a text file) with the context menu scan, and it reported clean.
If I do a manual scan from the GUI or scan it in the chest, it is detected.
Same behavior with EICAR...
I think that I have seen another thread that mentioned this, but I can't remember seem to find it...
What is the problem?
Looking at the stats, avast isn't even scanning the files ???
Win 7 64 Home Premium
avast Free 6.0.1125
Winpatrol
-
Same behavior with EICAR...
Just tested, works here...
-
The context menu would detect it if it scanned it...For me, even right clicking eicar and selecting scan, produces the results shown above. Nothing scanned, and subsequently nothing detected.
I think that I have seen another thread that mentioned this, but I can't remember seem to find it...
To add, the thread talked about a file that a user downloaded, scanned it via context menu and it showed clean. Once it was added to the chest, it was detected.
-
The context menu would detect it if it scanned it...For me, even right clicking eicar and selecting scan, produces the results shown above. Nothing scanned, and subsequently nothing detected.
As said, it works here.
See screenshot.
-
Wish it would for me...
The thing that worries me though is, that there was another person with a similar issue so it may not just be me...
I know what to look for, so not *such* a big deal, but for those that don't know...
-
I know what to look for, so not *such* a big deal, but for those that don't know...
I know what you mean...
-
Scott, did you maybe exclude the folder..??
(infections etc)
-
I made it so that I could do the "select folders to scan" scan to show that a manual scan catches it. Plus there are no exclusions set for the context menu scan
-
The context menu scan, being an on-demand scan will also use any avastUI, Settings, Exclusions entries.
-
Empty...but then the other scans wouldn't pick it up either if there was an exclusion...
-
Empty...but then the other scans wouldn't pick it up either if there was an exclusion...
We're just guessing... ;)
-
It's not apparently related to the setup in your sig
Win 7 64 Home Premium
avast Free 6.0.1125
Winpatrol
I have all of those, and right click scan detects eicar fine here.
-
I bet it's related to the fact that the file/folder is on desktop... but apart from that, no idea about the true reason.
-
I bet it's related to the fact that the file/folder is on desktop... but apart from that, no idea about the true reason.
Unfortunately, I am not even sure about that...
-
Hmm... OK, what if you enable creation of the report file (for the "Scan from Windows Explorer" scan) and let all item types be included there. What does the report file show after performing the same scan again?
-
A clue maybe, nothing is reported as being scanned. I enabled everything to be reported and get this:
A few scans, of the files that should be detected and one of them (last) was a random image on the desktop.
From what I can tell, it is not scanning any files.
*
* avast! Scan Report
* This file is generated automatically
*
* Scan name: Scan from Windows Explorer
* Started on: Sunday, May 15, 2011 11:27:03 AM
* VPS: 110515-0, 15/05/2011
*
Infected files: 0
Total files: 0
Total folders: 1
Total size: 0.0 B
*
* Scan stopped: Sunday, May 15, 2011 11:27:03 AM
* Run-time was 0 second(s)
*
*
* avast! Scan Report
* This file is generated automatically
*
* Scan name: Scan from Windows Explorer
* Started on: Sunday, May 15, 2011 11:28:10 AM
* VPS: 110515-0, 15/05/2011
*
Infected files: 0
Total files: 0
Total folders: 1
Total size: 0.0 B
*
* Scan stopped: Sunday, May 15, 2011 11:28:10 AM
* Run-time was 0 second(s)
*
*
* avast! Scan Report
* This file is generated automatically
*
* Scan name: Scan from Windows Explorer
* Started on: Sunday, May 15, 2011 11:28:48 AM
* VPS: 110515-0, 15/05/2011
*
Infected files: 0
Total files: 0
Total folders: 2
Total size: 0.0 B
*
* Scan stopped: Sunday, May 15, 2011 11:28:48 AM
* Run-time was 0 second(s)
*
*
* avast! Scan Report
* This file is generated automatically
*
* Scan name: Scan from Windows Explorer
* Started on: Sunday, May 15, 2011 11:29:09 AM
* VPS: 110515-0, 15/05/2011
*
Infected files: 0
Total files: 0
Total folders: 0
Total size: 0.0 B
*
* Scan stopped: Sunday, May 15, 2011 11:29:09 AM
* Run-time was 0 second(s)
*
-
From what I can tell, it is not scanning any files.
Strange...???
-
This is really messing with the way I check sites...checking what script is causing a detection, I have to open avast, choose what folder to scan, run the scan, and then answer no to the boot scan question...
Wish I could right click... ::)
-
Doesn't make much sense to me, I must say...
The context menu scan is, from the engine's point of view, a scan like any other...
Can you send me your avast5.ini?
-
Wish I could right click... ::)
Still no idea, why you can't...???
-
Should be attached
-
Something about the "extension scanning mode" (which you managed to have enabled somehow) is wrong... I'd say we'd better remove this option altogether, as it's not very useful and might confuse some users.
Please do the following: open the properties of the "Scan from Windows Explorer" scan, uncheck "Scan all files", switch the radio button to "content", close the window with OK, open the properties again, check "Scan all files" again, click OK.
-
Brilliant :)
It was on name extension, which was an empty list, so nothing scanned.
Changed it content and I get a detection. (An odd moment, happy to see a detection ;D)
I noticed that the "scan mode" changed from normal to thorough as a result of the change...
(which you managed to have enabled somehow)
Do you mean that it shouldn't be possible, or that it is odd that it was set. I don't remember messing with it...
-
The problem seems to occur only if that radio button is set to "extension", but the "All files" checkbox is also checked (which should disable the extension-mode anyway, but internally, it doesn't).
Without "all files", there's a default list of extension that will be scanned (though it hardly contains TXT which I saw in a number of your scans) - so having the extension list empty is not the problem.
-
Ok, Thanks for the explaination, and fix :)