Has anyone noticed a conflict with NBAM and Avast since the new database was released? It’s taking over one hour to do quick MBAM scan when it should only take five minutes or less.
Have you tried stopping Avast’s On-Access Protection first? Otherwise Avast is checking what MBAM is doing.
Hi scott27052,
This must be something else just performed the MBAM quick scan with version 1852 and it took the normal amount of several minutes. It alerted me to two registry issues, but I choose these myself.
There must be something else slowing down your comp. Download HJT from here:
http://www.filehippo.com/download_hijackthis/download/58170ee6e58bba306c943f5b6d745c99/
and then add a hjt logfile txt to your next posting for analysis,
polonus
I haven’t noticed anything and I last updated MBAM and ran a scan Yesterday. I will update and run a scan again.
OK, just downloaded the latest signatures and ran a Quick scan, whilst still on-line and browsing, so obviously avast was still running running.
The scan too 1minute 19seconds, which is about par for an MBAM scan on my system, 64,176 objects scanned. There was a little blip at first as a new tool I’m trying MJ Registry Watcher alerted twice to the MBAM low level access to the registry, so the scan would have been a few seconds quicker…
I generally pause the Standard Shield when scanning with anything else. Done that way, a quick scan with MBAM on my system is typically a little less than 4 minutes.
Normal time scanning from my side :
avast working in background as usual…
Same here with a scan with MBAM yesterday.
Just updated the JM Registry Watcher software as it now has a means of excluding certain registry changes (MBAM creates a registry sub-key at the start of the scan and deletes it on exit), previously it paused the scan whilst I selected OK.
So I have just ran a Quick scan again (whilst on-line), 64,282 objects scanned in 32 seconds, wow that is quick.
Hi
Just thought you should know…
In the last week … MBAM seems to have had a few problems with it’s definition updates 
Producing a couple of - False Positives 
MBAM have been quick to act on these problems.
Sending new updates to put things right 8)
But for people doing scans just at that wrong moment … :o
See…
http://forums.computeractive.co.uk/thread.jspa?threadID=152529&tstart=0
And…
http://forums.computeractive.co.uk/thread.jspa?threadID=152274&tstart=15
Yes, we saw them and they were reported here and were reported quickly on the MBAM forum and corrected quickly too.
If nothing else it shows that whatever else you do treat ‘all’ detections with due caution, never delete quarantine/chest, etc. and ‘always check’