Last night I did my first scan with Avast 5.0 and it came up with something I am not sure how to fix or really what to make of it.
http://img138.imageshack.us/img138/2586/hmmwf.png
Any suggestions would be much appreciated.
Last night I did my first scan with Avast 5.0 and it came up with something I am not sure how to fix or really what to make of it.
http://img138.imageshack.us/img138/2586/hmmwf.png
Any suggestions would be much appreciated.
Are you running AdAware…??
asyn
There is nothing to fix, these are unencrypted signatures loaded into memory by aawservice.exe (bad form as they can be detected by the resident AV), which belongs to AdAware.
Is your AdAware the Pro/paid option that runs resident or had you just done a scan with it (hence the signatures in memory) ?
Personally I wouldn’t give AdAware hard disk space as it really hasn’t kept pace with anti-spyware/malware (MBAM or SAS I would say are the two leaders right now).
What scan were you doing, I suspect custom scan with Memory included in the scan ?
I am running adaware with the resident protection, and a couple days ago I had done a scan. I use both adaware and malwarebytes. Although now I will probably drop adaware.
I had done a custom scan that did include the memory.
So really this is just a false positive and I have nothing really to worry about?
No it isn’t a false positive, when you send a signature based of hunting for virus signatures you can’t really call it a false positive when it alerts on those that it has found. But you have nothing to worry about or fix as I mentioned in my first reply, other than as you mention your dropping adaware ;D
To my way of thinking virus signatures in security software should be encrypted to prevent the resident AV from inadvertently detecting them.
thanks a lot i appreciate it.
No problem, glad I could help.
Welcome to the forums.
+1
asyn
MBAM is very good.