Buggy MBAM 3.0

[Fred]

Not really pleased with the new MBAM 3.0.

Leaves the Chameleon driver behind after uninstall, which slows the system alot.
After maximizing and restoring the main GUI, it's minimum width becomes the desktop width?
If you close the application from the tray icon and then uninstall with the /silent switch, the uninstaller hungs forever.

Hope they fix this soon. For now, we'll have to force the removal of the Chameleon driver manually from UVK's Service manager.

[Charger440]

From what I have seen of the new MBAM. they may be losing a customer if they don't fix that crap. Their focus seems to be on selling the premium version so much that they annoy you with the installer too.

[Fred]

I'm sure they'll fix it soon, Jim.

However, according to their EULA, we, techs should not be using it, anyway. I recently read a TN topic where a guy from the MBAM team explicitly said they didn't want their software to be used by techs.

https://www.technibble.com/be-a-profess ... ment-74433

The only reason I didn't remove it yet is that I'm guessing everyone would shout at me to put it back imediatley afterwards.

[wmmiller]

The Premium version is still 2.2.1. 1043 on my machine. They must not have pushed it out to premium user yet. Unless they doing a controlled roll out.

[Charger440]

I think TN is the one that banned me for giving an honest review of d*. That told me they were not interested in sharing good information but protecting the feelings of their friends.

As for the post about MBAM, when I install it on a customers computer, I do use it to clean their computer but I also leave it on the for the customer to use on their own. Everytime I use it and leave it, that is a sales opportunity for them. So when you cut to the chase on it, I'm doing exactly what they want as a tech and if they had installed it prior, I'm not going to skip it just because I'm a tech.

[wmmiller]

Same here and good point Jim. I install it and leave it on almost every computer I deal with. I wouldn’t be surprised if computer techs are the reason most people end up with it installed. It’s not normally installed on people’s computers I see unless I installed it. It may be short sighted to want to ban a tech from installing it and leaving it behind in the end. It was said they don’t like it, they didn’t say they would hunt us down. Not that I care. See signature.

[Muhammad Tasneem]

Is it possible to add different MBAM verson like

Version 1:
Malwarebytes Anti-Malware (Free/Premium) 1.75
http://filehippo.com/download_malwareby ... are/14815/

Malwarebytes Anti-Malware (Corporate) 1.80.2.1012
http://data-cdn.mbamupdates.com/v0/clie ... 2.1012.exe
http://data-cdn.mbamupdates.com/v0/clie ... 2.1012.msi

Version 2:
Malwarebytes Anti-Malware 2.2.1
http://filehippo.com/download_malwareby ... i_malware/

Version 3:
Malwarebytes 3.0.4.1269
http://filehippo.com/download_malwarebytes_3/

[Fred]

Jim, Bill, couldn't agree more with you guys except now I won't leave it installed if the chameleon driver keeps slowing down the machine. My dev laptop has a SSD drive, works super fast and boots in less than 10 secs, until I install MBAM, and it becomes almost as slow as when it had a HDD.

[steve2189]

I'm sure they'll fix it soon, Jim.

However, according to their EULA, we, techs should not be using it, anyway. I recently read a TN topic where a guy from the MBAM team explicitly said they didn't want their software to be used by techs.

https://www.technibble.com/be-a-profess ... ment-74433

The only reason I didn't remove it yet is that I'm guessing everyone would shout at me to put it back imediatley afterwards.

It's not that Malwarebytes don't want their software used by techs.
They don't want their software used for commercial purposes without being paid for a licence.
So if you use MBAM to clean a customer's machine, and sell the customer a MBAM license (by becoming a Malwarebytes partner), then they are fine with that.

[wmmiller]

We get it Steve.

[Chester170]

It does make my Pc much slower than before. Too bad cause I really liked MBAM before this update.