Author Topic: Malwarebytes - Avast PREVENTS infected scanned objects?  (Read 1854 times)

0 Members and 1 Guest are viewing this topic.

Aphex23

  • Guest
Malwarebytes - Avast PREVENTS infected scanned objects?
« on: December 24, 2011, 02:28:34 AM »
The title probably doesn't make much sense, but I didn't know how to get the idea across.  What is happening is, as always I have Avast running.  I had run a full scan on Avast a few days ago, it found 2 malware viruses and removed them.  Today I decided to run Malwarebytes to see if it noticed anything that Avast did not.  Well, -as- Malwarebytes is running, it seems like everyime Malwarebytes finds a supposedly infected file, Avast grabs it first and pops up a message saying something like "(x) was stopped before being opened... etc." Malwarebytes does not show an infected file found (I assume because Avast literally grabbed it first as soon as Malwarebytes found it).  Does this sound possible?  Has it happened to anyone else? Should I turn off my real time shield when running other virus programs like Malwarebytes to prevent this from happening, or will Avast take care of them properly even though it was another program that found it?

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37601
  • Not a avast user