Malwarebytes 2 - Yes, No or Maybe ???

[REDACTED]

I'm sticking with MBAM v1.75 at the moment. I've tried every new version since 1.75 and none of them haave worked smoothly on my machine. The problem always seems to be that the MBAM driver causes a BSOD during scans. Rather than try to fix the problem I started looking at other similar products and have been impressed with Emsisoft Emergency Kit:

https://www.emsisoft.com/en/software/eek/

I'd suggest trying it as it's free.

Scans are configurable and can be set to exclude files, folders or drives. Can also scan for PUP's.

The only downside is that the update process isn't quite as fast as MBAM's.

Update: I've just installed the latest stable release of MBAM and it works correctly with no BSOD's. They must have fixed the driver issue!

[schmidthouse]

My feeling being a user is Mbam Version 2 has taken some getting used too, as it seems (in some respects) fundamentally heavier/awkward compared to v.1.75

[DavidR]

My feeling being a user is Mbam Version 2 has taken some getting used too, as it seems (in some respects) fundamentally heavier/awkward compared to v.1.75

It took some time to be able to change the scan settings in my win7 netbook as the scan settings window was larger than my screen size (until a hack to increase screen res above the native res), so I couldn't uncheck the scan archive option in the Hyper scan.

Once that was removed/unchecked the scan was more like the Quick scan of old.

[bob3160]

The pro version of Malwarebytes 2.1.4.1018 using too much resources.

I complained about it quite some time ago.
Is it ever going to change
Folks complain about Avast, maybe they need to look deeper.

[DavidR]

The pro version of Malwarebytes 2.1.4.1018 using too much resources.
<snip image>
I complained about it quite some time ago.
Is it ever going to change
Folks complain about Avast, maybe they need to look deeper.

From the first version of 2.0 MBAM Pro became a resource hog, so much so I had to disable the resident function on my win7 netbook. Kind of defeats the point of buying the MBAM Pro version.

I don't know which services it uses in win8.1 or win10 - but in this XP system it uses 3 services, so you might find it uses even more.

EDIT: Currently I haven't updated to the latest version 2.1.4.1018 still using 2.0.4.1028 and that has been a resource hog.

[REDACTED]

I only use the free version and it seems fine except that I wish it still had the old quick scan that went twice as fast as the new Threat scan. I also unchecked the box for scanning within archives. It does scan somewhat faster if you temporarily disable your resident AV. If you scan with the AV active, you can see the scan happening in both products. That's not necessarily a bad thing . It just slows things down a little.

[schmidthouse]

Frankly, I don't think we can correctly compare MBam v.1.75 to the newer versions (v.2.1.4.1018) Premium due to different/improved technology/Engine etc  which to achieve better security, takes more resources
** Just as I don't believe we can correctly compare Older versions of Avast (say version Seven or Eight) to version 10 (2015) for the same reasons; different/improved technology/NG etc which to achieve better security "also" takes more resources.

I have used the Paid versions of both MBam and Avast for years and they have changed. As they have developed, it can be stated They 'both' have gotten better at providing more security and on my OS's they both consume more resources and seem heavier then earlier versions I've mentioned.

[bob3160]

In this comparison, Malwarebytes is still the largest system hog.
I agree that for better protection, more resources need to be used but there also needs to be a trade off at some point.
I don't want to go back to the old days when the protection used so much of the system resources that it was impossible
to enjoy your computer.

[CraigB]

The new version of Malwarebytes runs very smooth here on 8.1 64x, I don't notice any lagging or anything else.

[polonus]

I am testing it and no weighing too heavy on the old Vista cycles for me.
Stumbled upon it for I could not update SAS free this week,
the protection on demand I normally have installed.

polonus