I ran a scan of an old drive that had mal-ware on it with Avast! and it quarantined a few items and created it’s final report. Then I followed with a scan by Malwarebytes Antimalware and as it hit the next few infected files Avast! popped up a message of dangerous file detected and asked to quarantine.
Since Avast! is capable of detecting those files why would it not do so on it’s pass instead of waiting for MBAM to hit the files later?
This information doesn’t help as there is no details of what was found on either scan (especially the mbam scan) to make any determination.
You can post the scan log information for both avast and mbam scans.
Yeah, sure. Give me a few.
Probably compressed files that MBAM uncompressed and where then intercepted by avast.Nope....malwarebytes does not scan compressed archives
Not sure what you mean here, your the one seeking information/help.
I mean, give me a few minutes.
Well, the logs are scrambled and can’t be read from a different operating system. The quarantine index looks like this:
“-0000002A1054632436mscache_cookie_windows_cleaner7.exeH:Win32:WrongInf-D [Susp]Viryes13609248296241476-0000002B986434200”
I’ll have to mirror that OS back to the internal drive and boot from it to start that copy of Avast! in order to read the logs. I’m in the middle of building up a Windows 8 partition so I’ll reply to this post sometime later, maybe Sunday or Monday.
It was an old drive with a friends backed up 20 GB partition on it so it was more about curiosity. They were actual viruses and not just adware infections. I knew they were there and was surprised Avast! didn’t catch them until MBAM was scanning.
Unless Avast! has an option to read remote partition logs?