I downloaded the Pre-Release 64-bit version of superantispyware from their site (www.superantispyware.com) and everything went well. I just now decided to do a memory / startup scan and it’s flagging SAS’s processes. I realize it may be a conflict with the two programs, but I find it strange that real-time prot on SAS is disabled.
See this thread:
http://forum.avast.com/index.php?topic=55820.0
I think the same thing that DavidR mentioned is a factor here.
-Scott-
@ DarkLegend
When posting images, please crop them to show only what is required and use the .gif image file format, this keeps the file size to a minimum, for the poor saps stuck on dial-up, like me ;D
See the difference in the two images, yours and mine, over 100KB less yet the quality and information are all there.
Yes it is similar to the topic Scott gave the link to, since this doesn’t happen to me and I’m using SAS Pro (32bit) and I don’t get this (image2) I believe you my have been tweaking your scan settings to Ignore Virus Targeting ?
SAS has an on-demand function where it allows for a right click scan of a file, for that to happen there would need to be SAS an process running. So I don’t know if this is the case here or if there is an essential difference as I’m using the resident protection and this isn’t happening.
Hmm… Thanks for all the help, I will definitely take a look into the scan settings. One question though, Even having those advanced settings enabled, Should avast be detecting known “Legit” applications like this? And if so, Why? I thought there was some kind of whitelisting process that takes place.
Known legit applications ans clean legit applications aren’t one and the same, avast is scanning for virus signatures and as far as it is concerned it has found some.
If you whitelist something it has to have something more behind that measure than it simply matches a file name, not to mention avast isn’t alerting on superantispyware.exe, but the unencrypted virus signatures it has loaded into memory.