Malwarebytes 3.0 Released

[Puffnstuff]

I am currently using 3.0.5.1299

1269 was the only version it would allow me to have even after repeated searches for updates (both manual and automatic) not to mention scouring their forums for newer builds to address the issues I and many others faced with it. This is Malwarebytes official response to it.

 

[Micrornd]

1269 was the only version it would allow me to have even after repeated searches for updates (both manual and automatic) not to mention scouring their forums for newer builds to address the issues I and many others faced with it. This is Malwarebytes official response to it.

All I can say is that I never encountered that problem, I clicked the "turn on" button after I installed, it never returned in any of the versions.
I do always check for program updates at the Malwarebytes site, as they have always been slow to roll them out and I am impatient.

 

[Puffnstuff]

I can't even launch IE with it enabled as it will crash upon attempted launch. Now it won't let me enter information in fields even with anti-exploit disabled. This software is pure alpha and should've never been released like this. I took this snip so everyone can clearly see the version .1299. I'm about to roll back to 2.21 at least until I can locate a suitable replacement and their pay for software will never grace my pc's again.

 

[Puffnstuff]

The issue is that 3 is triggering Microsoft's enhanced mitigation software, EMET, causing the crashes. I just removed EMET and IE will launch fine. This is yet another thing that Malwarebytes needs to address. I've filed the problem with their support so we'll see how long it takes for them to address it.

 

[Chiefcrowe]

Also use EMET and when I opened it to update the program it crashed firefox. I probably won't be using it until they fix all of these problems! Thanks for reporting it Puffnstuff!

 

[Micrornd]

Puffnstuff and Chiefcrowe - I'm curious, what version of Windows 10 and what version of EMET are you using?

 

[Puffnstuff]

Puffnstuff and Chiefcrowe - I'm curious, what version of Windows 10 and what version of EMET are you using?

I run 1607 build 14393.576 and was using EMET 5.5 but now I see that MS has updated it to 5.51 which WU didn't offer so I just installed it to see what happens and I will report back on my findings.

Edit: I closed IE and tried to reopen it and was greeted by the same problem where EMET will hang the application so I uninstalled it again.

 

[Chiefcrowe]

Actually on the pc that I was trying malwarebytes 3 on is a Win 8.1 machine (with EMET 5.5)

 

[Micrornd]

Thanks for the replies.

I was asking because EMET 5.52 was released in November, and MS announced that they will not support the use of EMET on any version of Windows 10 beyond 1607 (it's also noted in the EMET 5.52 user's guide), and at the same time they also pushed back the cutoff date for support to July 2018 for EMET for Windows 10 1607 and earlier, as well as all earlier Windows, back to Vista SP2.

I don't know if you've seen this - https://blogs.technet.microsoft.com/srd/2016/11/03/beyond-emet/
When it came out there was one dissenting opinion from a normally reliable source - https://insights.sei.cmu.edu/cert/2...tect-insecure-applications-like-emet-can.html, and then the herd of parrots jumped on the bandwagon repeating what he said without anything new added. (well it did generate a lot of hits for their sites)
MS hasn't responded so it's hard to judge who is right.

But apparently something changes after version 1607 since MS will only support the use of EMET up to 1607, but obviously that's not a factor for either of you.
I don't have EMET installed here because EMET's not supported in Server 2016 either, so apparently something is different in it (even though it was released before Win 10 1607), as MS did/does support EMET in prior versions of Server.
Maybe an interaction with defender or other built-in safeguards in the OS that are triggered by Malwarebytes' AE running?

As I said, absolutely no problems in Server 2016, so the difference in the OS's must be where the "rub"
lies.
Hopefully Malwarebytes can sort it out.

Does your Event Viewer offer any clues?

 

[Puffnstuff]

I only have Malwarebytes 3 premium on my desktop and the free version of 2.21 on my other two pc's. I run EMET on both of them for real time scanning so no conflicts there. I'm going to try 5.52 and see what happens because I'm a glutton for punishment. I'll report back on what happens as I expect more of the same behavior from it but it might surprise me.

 

[Chiefcrowe]

Thanks for the update, i'll install 5.52.

 

[Puffnstuff]

5.52 crashes IE upon launch just like 5.51 did with Malwarebytes 3 anti-exploit enabled so I removed it from my desktop so I can run Malwarebytes without issue.

 

[Puffnstuff]

I finally received a response from Malwarebytes and here's what they said to me.

Thank you for letting us know and I will pass this information on to the developers.

Malwarebytes 3.0.5 has the anti-Exploit and the Anti-Ransomware built into it
.

Regards,

William Rowland – “Gringo_pr”
Customer Success Specialist & Malware Removal Specialist

 

[Bubbaleone]

I finally received a response from Malwarebytes and here's what they said to me.

Thank you for letting us know and I will pass this information on to the developers.

Malwarebytes 3.0.5 has the anti-Exploit and the Anti-Ransomware built into it
.

Regards,

William Rowland – “Gringo_pr”
Customer Success Specialist & Malware Removal Specialist

What's puzzling to me is the statement by "Gringo_pr'" which makes it sound like their developers didn't previously know about these bugs. Which obviously isn't the case given that the following quote from the Malwarebytes for Home Support forum is dated Monday the 19th. Btw, the third item listed, “Real-Time Protection disabled”, is the exact error I reported on in my first reply to this thread Monday two weeks ago, #8.

bdubrow/Staff/Topic Starter
Posted Monday 12/19/2016 at 09:56 PM

Hello!

We’ve just released a new v. 3.0.5 upgrade patch for Malwarebytes v. 3.0.

If you’re running any earlier 3.0 version you will be prompted to upgrade at some point over the next week or so. But if you’d like to install the latest version immediately, you can download and install v. 3.0.5.1299 from this link.

This release resolves a number of items that have been reported since the initial launch of Malwarebytes 3.0:

Fixed installer error that displayed 'External exception E06D7363'
Fixed issue where updates would get stuck in 'Checking' state
Fixed issue where “Real-Time Protection disabled” notifications would display throughout the day (NOTE: this notification may still be seen on reboot on some systems, but we’re working on another longer-term fix to address that separately)
Fixed slow shutdown issue that could occur in Windows 7 with real-time Malware Protection enabled (NOTE: a corresponding fix for Ransomware Protection is still pending)
Fixed conflict with Kaspersky that would not allow browsers to open properly
Improved upgrade experience when installing over a previous version of the Malwarebytes anti-exploit technology

I know there are a number of other items still pending, but the team is actively working on getting those addressed as soon as possible, too!

https://forums.malwarebytes.com/topic/192529-malwarebytes-305-patch-release-now-available/

So what's the actual date of this reply you received from MBAM? If it's dated later than the 19th I'd suspect Mr. Rowland is pretty much clueless, given that the developers have been working on this for at least a week now.

.

 

[Puffnstuff]

So what's the actual date of this reply you received from MBAM? If

DEC 24, 2016 | 07:02AM PST is the date time stamp on the email.

 

[Puffnstuff]

Anther email to malwarebytes and the complete removal of the 3 ensues.

I just discovered another issue with anti-exploit. I'm using office 2016 pro plus and PERRLA APA software. With anti-Exploit enabled it will crash word every time I try to edit my APA database using PERRLA. When I disable AE the PERLLA software will update its database without issue. I tried specifying the M3 to exclude PERLLA and all office folders but the problem persisted until I disabled AE. I'm about to uninstall M3 from my system to prevent any further issues. Last semester I was using 2.21 and suddenly my APA citations started becoming corrupted but I could never pinpoint the source of the issue and now I'm leaning towards your software as the culprit. This is completely unacceptable behavior from a premium software.

 

[Puffnstuff]

Apparently Malwarebytes wrecked my IE fonts as well rendering viewing fonts in web pages using IE on this pc neutered. Thanks a bunch Malwarebytes, a product that will never again be installed on my pc's.

 

[pcslookout]

I switched to Emsisoft Anti-Malware for now.

 

[Micrornd]

Version 3.0.6 is now available

 

[JimKiler]

I have had v3 on my pc for 2-3 weeks now and no issue. Although it wanted to scan my PC every day for some reason.

 

[Mike64]

Version 3.0.6 is now available

I seem to have spoken to soon. V3 didn't "interfere" with anything, but also seems not have been doing much. I checked it this morning and it hadn't updated or run a scheduled scan since I installed it, and website protection wouldn't turn on at all. (And for that matter, I have no idea if it was really doing anything at all except sitting there.) All of which appear to be known issues that MB is "busily working on" according to their reps on their forum. As many users they said, MB clearly should not have deemed this (seemingly, for no good reason) to be "no longer in beta"… I went back to v2, which fortunately I had copy of since as far as I could see, prior versions aren't available on their website.

What with all the drama it seemed to be causing, I figured I'd wait until my installed v2 actually "notified" me of v3, which only happened today. I haven't done anything but use Firefox and Word 2007 so far, but it installed just fine and hasn't caused any trouble. And fortunately I'd remembered to save my license key/ID (also that original lifetime one) in a reasonably accessible place after the v2 upgrade sent me digging for the original packaging into the miscellaneous boxes of old discs and whatnot in the closet since MWB apparently can't be bothered to pull it from the old version before installing the new one (or is merely hoping that some statistically significant number of users have lost it and will be willing to buy the newer annual ones to replace it…)

 

[Puffnstuff]

I tried the latest version of Malwarebytes 3 the other day on my clean install and it did the very same thing as before interfering with PERRLA syncing. I removed it again and the issue stopped. It won't even follow its own exclusion rules with PERRLA and my APA software is more important than it is so away it went for the last time.

 

[Mike64]

I tried the latest version of Malwarebytes 3 the other day on my clean install and it did the very same thing as before interfering with PERRLA syncing. I removed it again and the issue stopped. It won't even follow its own exclusion rules with PERRLA and my APA software is more important than it is so away it went for the last time.

The nag pop-ups have fortunately slowed to a dull roar, so I've been only half paying attention, figuring I'd eventually get around to checking the web for updates on its status. I must say I'd have thought they'd have gotten their act together by now, but I guess not...