Current State of MalwareBytes

[MikeLierman]

I've had this discussion with some on Google Plus, including Lisa from Call That Girl. I'm still not sure on my position, but I'm fairly disappointed with the quality of MalwareBytes version 2. I thought I'd voice my opinion and see if anyone else here has also experienced my frustrations.

• As version 2 started to roll out, I started updating my customers to the new version. This seemed to be a bad idea, a lot of paying customers had numerous problems, including not being able to update. I also very much disliked how it was rolled out. Customers on the 1.75 version would get a prompt to update, which would take them through multiple button click to uninstall old version and install the new version.
  
• Definitions will get stuck and not update. Or.. multiple popup windows in the tray informing the user that MalwareBytes has not been updated, even though it updated several hours earlier.
  
• Extremely long scanning process. A full scan on a typical machine will take 2-4 hours. In version 1.75 the same scan took roughly 45 minutes to an hour. I understand that a few things have been added, including rootkit scans, but doubling up the scan speed doesn't sit well with me.
  
• Issues with scans getting suck in "pre-scan" and not actually scanning.
  
• Random program crashes, and incompatibility across some systems, even with a clean install of MalwareBytes. I've ran across a few systems where it would refuse to open, after digging and doing some research, a couple of MBAM 'engineers' suggested editing a preference file in MBAM.

 

[FoolishTech]

Hey Michael, I'll "byte" ... how about the forced update to v2 when you updated v1.75 defs, or my largest gripe, not supporting command line parameters.

 

[glennd]

or portable

 

[CLC]

Hey Michael, I'll "byte" ... how about the forced update to v2 when you updated v1.75 defs, or my largest gripe, not supporting command line parameters.

They are supposed to be adding switches to version 2.1, that's what I read on their forums anyway.

 

[Go-To Gordon]

Extremely long scanning process.[/B] A full scan on a typical machine will take 2-4 hours. In version 1.75 the same scan took roughly 45 minutes to an hour. I understand that a few things have been added, including rootkit scans, but doubling up the scan speed doesn't sit well with me.

While I have had a couple clients have issues with updates I do not understand people stating longer scan times! Even on bogged down older machines with rootkit checked I'm seeing WAY shorter scan times. In the 5-20 minute range.

 

[nlinecomputers]

While I have had a couple clients have issues with updates I do not understand people stating longer scan times! Even on bogged down older machines with rootkit checked I'm seeing WAY shorter scan times. In the 5-20 minute range.

Same here. It is MUCH faster now.

 

[HFultzjr]

Hey Michael, I'll "byte" ... how about the forced update to v2 when you updated v1.75 defs, or my largest gripe, not supporting command line parameters.

Yeah, I agree about the auto update. If I want version 2, I'll download version 2.

Harold

 

[Xander]

Shorter times seen here, too. As for versioning, they're not under any obligation to support older versions. I'm more bothered when I go to do a MBAM scan with D7II and it starts installing the old 1.75 (and, yes, my local installer is 2.02).

If I want an outdated version, I'll .. no, I won't use an outdated version.

 

[PCX]

Hey Michael, I'll "byte" ... how about the forced update to v2 when you updated v1.75 defs, or my largest gripe, not supporting command line parameters.

Auto update to 2.0 can be avoided by simply click cancel during the definitions update and then just let the rest of the definitions update on the old version, then I think you have to click on cancel again to ensure it does not update to 2.0 after updating the definitions.

 

[cypress]

Scan times are better for me too. Biggest gripe has been the update feature.

 

[Porthos]

Hey Michael, I'll "byte" ... how about the forced update to v2 when you updated v1.75 defs, or my largest gripe, not supporting command line parameters.

That can be turned off in settings uncheck "check for program updates"