Malwarebytes Anti-Malware Updates

Guess it depends on the system. On mine both the service and exe show 0% CPU usage with real time protection enabled.

 

I did initially have trouble uninstalling the first beta. I had to cancel the uninstall, unload the tray icon/real time protection, and kill the service in the task manager. Then the uninstall completed properly and after rebooting the 2nd beta installed without incident

 

My cpu usage also shows 0%, memory is 235mb ( better than previous beta) for the service and 8.7mb for the tray app but I do notice some sluggishness opening programs or browser, one program that makes the sluggishness really evident for me is to run a registry scan with CCleaner, with MBAM 3 active the scan takes 17 seconds to run...without MBAM running the scan completes in 5 seconds.

Win10 x64 with only Defender running with MBAM, i7cpu, 16Gb ram, Samsung 840Pro SSD.

 

Takes to long to boot to windows, missing MBAE notifications.
Win7 64

 

Have you left Exploit Protection enabled and then disabled all of the mitigations or did you just turn off the module? Obviously it's easier to turn off the module, however that causes a persistent "protection disabled" warning in the tray icon and the main UI. One thing I noticed is keeping the module On with the individual mitigations off leaves the mbae DLL injected into processes, where as turning the module off means no DLL injection (would be good if someone could confirm this). There weren't any obvious negative impacts with the DLL injected and the mitigations off alongside HMPA, but this should be confirmed through testing.

 

Installed latest beta, while doing so a box popped up, something about it couldn't access a MBAE driver, clicked " Try Again", the box popped up again, I clicked " Ignore" this time, after that it installed ok. Everything seems to work fine, Threat Scan 389,000 items scanned in 56 seconds. Also, this time I had to enter my license, first beta it did that automatically.

 

"Also, this time I had to enter my license, first beta it did that automatically."

that was my complaint about trying the first beta. it gave me a new key and didn't pick up my old one. maybe because I have paid MBAM life and MBAE yearly installed?

 

Can you disable the Anti-Exploit protection and tell me if the sluggishness opening programs goes away? We think we've found the cause here.

 

This version does not install either on my PC (like the previous 3 Beta):

Code:

Runtime Error (at 14:76): Could not call proc.

 

I just had my first BSOD on my testing machine.

Not thinking, I restored my pre-beta image so I am unable to provide the dmp.

Sorry about that. I'll try the next beta.

It would be great if we could disable the warning about not being protected when disabling exploit protection.

 

I agree...

 

Are you upgrading from a previous beta and/or an older version of Malwarebytes Anti-Malware? Or is this a clean install? Can you give me some specs on the machine (OS, etc)

 

Woah, that's a serious one. Can you PM me any other info you have?

 

Yep, sure. I'm on it.

 

Now that mbam looks like an Internet security suite do you plan to add a firewall?

 

I wouldn't call it a suite, in fact, I hate that word. Our focus is performance, whereas suites tend to be bulky. We've built a single-agent endpoint protection product that can replace antivirus. We do not intend to wrap in features like backup, firewall, etc. into it.

 

The registry keys and related files will likely be detected as part of the linking engine. If you exclude the program directory of the PUP detection that triggered those registry detections, then they should not be detected anymore.

 

Exploit mitigations will always clash. Having said that we'll take a fresh look if we can enable some default exclusions if HMPA is installed and active.

 

Yes, if a third-party AV is detected then MB3 will also register. This will not deactivate the third-party AV or interfere with it in any way. They can both run alongside each other.

 

I will add to this and mention that we have done a lot of testing and improvements so that even though the scan does use CPU, it does not cause impact, slowness or sluggishness in the system, so that users can continue working even if the scan is running.

 

The modern Windows Firewall is actually very good. We do rely on it for our Web Protection module, which works on top of the Windows Firewall (using WFP).

 

Hopefully clean install (I have uninstalled MBAM 2 & 3 before, but the v3 uninstaller stalled, so I removed things manually).

Windows 10 Pro x64 protected by Emsisoft Internet Security & HitmanPro.Alert

I was able to install in Safe Mode, but the App reports as 3.0.0 and offers an update that fails to install again, though this time at 14:64. "Funny" thing: the downloaded installer for that update is 3.0.2.1175...