Malwarebytes Anti-Malware 2 released

Maybe they could make it skin able after they solve the big issues of course.

 

MBAM is working without issue on my 64 bit desktop and I have the pro version running with real time protection enabled and I also have Avira Antivirus suite installed.

 

It may seem like it is, but it isn't under the hood. It's easy to prove it is causing restraint issues on a system, even quad, and six core machines it's causing incessant restraint issues. The boot slowdowns are confirmed. Now we have evidence it's poisoning the DNS Client on Windows. So in general, there are a 'number' if issues still. I'm giving it another 8-10 months before checking it out again. 1.75 is fine, but the DHC dropouts aren't acceptable in that - those are fixed in 2x, but 2x brings it's own problems to the table.

Eset will do for now.

 

I don't doubt what you're observing, but seeing something on a very small number of computers and then coming to conclusions without thoroughly investigating causes doesn't constitute "evidence" in the broader sense, as in "true for everyone". There is currently a thread at Bitsum.com where the matter of Process Lasso restraints on mbam.exe are being looked into. Hopefully we will have something from the developer about it soon.

 

Interesting thing. Should MBAMService be showing up under processes, or MBAM.EXE? I noticed at times it appears MBAMService is stuck on, and being 'restrained', but other times I only see MBAM.EXE running with no MBAMService running. Yet other times it shows, and is restrained.

Why would this be happening?

I allowed one of my machines without MBAM to run monitored for 24 hours, and NO restraints on anything during that period. I let another one run with MBAM 2x installed, and there were close to 40 restraints on MBAM during that period. I really do not have the time to monitor, debug, and report my findings on this product. I'm in fire-forget mode on applications due to some projects I am involved in from now until the end of summer.

 

If they're a member here tell them to feel free to send me a PM.

No, it was a scheduled Threat scan but in any case, if you need to select the option to Scan for rootkits in the Advanced settings, then isn't the Scan for rootkits option under Detection and Protection redundant?

For what it's worth, another scheduled scan has just ran and I DID have the option to Scan for rootkits enabled under Detection and Protection AND in the Advanced settings and the log shows that Scan for rootkits was STILL DISABLED.

Me thinks the developers at MBAM have some work to do.

 

I agree that it's confusing and I hope they simplify it. I haven't fully tested yet, but what it looks like is scheduled scans are fully customizable and don't pull settings from the "Custom Scan" section - you have to set all of the options when you create one. If go into the Automated Scheduling section and click the "add" button you get an "Add Schedule" page and in the bottom left is an "Advanced" button. When you open the advanced options you can check "scan for rootkits" there. Hope that helps.

 

MBAM 2.0.2 keeps starting up at random times and when I try to exit the program by right-clicking the tray icon, it freezes. Uninstalled. Done with it for a while.

 

@RubbeR DuckY

There seems to be a subtle form of censorship being played out at Malwarebytes. A whole lot of posts that have been made in the Malwarebytes forum recently, have suddenly disappeared. Seems to be the result, that when there is whole slew of problems being reported about v2.0, just apply spin.

 

Hi all, I've been following the thread and see various people with issues. People usually only post if they have a problem, so I am wondering if as a whole, the latest v2.02 is OK to install yet.

 

I've used every build since v2 was released and I haven't had any problems. That's not to say there aren't issues - there are and they been acknowledged by the developer who has promised to fix them - but for me it's stable and runs quietly in the background. Why not try it and if you have some issue then uninstall and wait for the next update?

 

I have build 2.0.2.1012 running on 4 machines with Win7 and win 8.1 without issues.

 

I'm done with it, and will begin selling off my 7 lifetime licenses on Ebay shortly. Problem solved.

 

Make sure to keep a couple of licenses for yourself, I'm sure they'll fix these issues.

 

v2.0 proves that newer isn't better, and should serve as a lesson to all software developers to think twice, and check 3 times before releasing an "upgrade". MBAM's name was bullet proof prior to 2.0, and is far from that now.

 

A forum helper has replied to you over there. FYI No spin, housekeeping 101

 

Same here on several different systems

 

OK I'll give it a shot.

 

Let us know how you make out. I'm still treading water with 1.75 myself here.

 

Installation was flawless. Made my settings, and did a Threat scan. No problems. While doing Settings I couldn't find an explanation of what "Self Protection Module" is in the MBAM Guide. Can some one give me an explanation so I know whether to check it or not? Thanks in advance.

 

If you navigate to the Malwarebytes forum you'll find the answer https://forums.malwarebytes.org/index.php?showtopic=149334&hl=+self +protection#entry834242

 

These last reports have been encouraging. For the longest time, all I'd heard about 2.0 and above was negative.
I've stuck with 1.75, bound and determined not to migrate to a flawed version.
Whoever said MBAM used to be bullet-proof but is far from that now, has hit the nail on the head. But champions of all walks of life are the ones who manage to get back up and continue on.
I'm getting the sense that that is the course MBAM is starting to follow. I think I'll be upgrading before long!
But I'll create a couple of full system images prior to upgrading, so I can restore both machines if things aren't ideal.

 

Thanks for the heads up.

 

I created a AX64 image to restore to before doing the V2 upgrade, in case as you say, things aren't ideal, and give me a way back to V1.75 in about 15 minutes. Version 2 looks good so far.

 

Still on 2.0.1.1004 here.