• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Malwarebytes 3.0 Released

That stupid program caused all of my browsers to be blocked. Their website says they've got an update but it only allows you to download 1.09.1.1269 which is the problem child. Build 1.09.1.1280 supposedly has a fix to allow you to use your browsers again but there is no support link on their download page or in their support forums for you to get the update at. I had to uninstall it and go back to 2.21.
 
Well that sucks! If you can please let us know when the new build is available and I'll wait to upgrade until then.
 
Haven't tried it on my systems but I could test it on a VM and just do a snapshot to roll back any changes. Saw a few people saying Edge doesn't work but there may be more to those reports.

Here's a list of known issues posted less than an hour ago:

If you are running an earlier Alpha or Beta, and your upgrade to Malwarebytes 3.0 fails for any reason, simply uninstall the earlier version and then reinstall new version.
Occasionally, after installing, the user will see a “protection layer is off” warning while the protection is being or has already been automatically turned on.
Occasionally, after installing, the user could see a “failure to connect to service” error, usually a reboot or rerunning the installer will correct the failure.
Microsoft Security Essentials running alongside Malwarebytes 3.0 might cause system lockdowns under Windows 7 due to a buggy Microsoft update.
Some translated strings may still appear in English.
Clicking some of the help “?”s throughout Malwarebytes currently does not do anything.
Some Windows Insider Preview builds blue-screen at Malwarebytes 3.0's Web Protection.
Custom Scan options are not persisted for subsequent scans.
If Malwarebytes 3.0 is closed, a context menu scan does not open up to scan page.
New scans don't reset "Threats Quarantined" counter on Scan Summary page.
The correct date and time format is not enforced when adding or editing a scheduled scan.
Web protection can take a long time to start in Windows XP after upgrade from 2.x.
Custom anti-exploit shields are not enabled by default.
Website block notification appears multiple times on Windows XP.
Windows Vista: Post Expiration Notification for manual renewal appears after each reboot.
On Windows XP selecting a folder in Exclusions does not actually allow selecting a folder.
Currently allowed to add a Domain Exclusion on Windows XP but since this is not supported it will be ignored.
There may be some quirky behavior when resizing the user interface.
Some dialogs are improperly formatted with high DPI settings.
Any User Access Policy created in MBAM 2.x is not migrated when upgrading from MBAM 2.x to Malwarebytes 3.0; a new policy will have to be created.
Malwarebytes 3.0 Installation can fail if installed from an imdisk virtual disk.
 
The majority of the problems I see concerning this new version revolve around windows 10 and Kaspersky and I run zone alarm which is based upon their architecture. Each windows 10 pc I tried using it on did the very same thing and the mbam blocked internet access using IE but one pc did retain the ability to use FF. I'm sticking to 2.21 until they release an update that I can actually access and the forums quiet down over there. Once the guinea pigs report success with it I will upgrade but until then I need unfettered access using IE.
 
I made 3 work on my pc by turning off the exploit protection.
make3work.JPG
 
I'm running Windows 7 x86 on an old GX620 Optiplex that's been happily running mbam premium v2.2.1.1043 since it's release. This morning I decided to "update" to the new v3.0.4.1269 with unpleasant results. The update install appeared to go without a hitch but, after restarting, I saw that mbam's systray icon had a big red exclamation mark over it, and the message that real-time protection was disabled. However all my settings were still exactly as I'd had them set before the update, and the console showed me as fully protected but no matter what I tried, that red exclamation with it's protection disabled notification would not go away. Worse, I immediately uninstalled 3.0, rebooted, re-installed 2.2, and was greeted with a big red exclamation mark.

To make a long story short; Malwarebytes is very much aware that 3.0 is buggy and one of their forum admins was advising users to hold off upgrading until they get it sorted. If you've already installed 3.0 and need to go back, run the Malwarebytes "cleanup-tool" to uninstall 3.0 (don't use Programs and Features) if you expect 2.2 to re-install properly. Be sure to reboot after uninstalling and, as soon as 2.2 is finished reinstalling, reboot again.

https://www.bleepingcomputer.com/download/malwarebytes-anti-malware-cleanup-tool/

.
 
Last edited:
When I rolled back to 2.21 the first time all I had to do was just uninstall it and reinstall 2.21 without using any unnecessary third party software. I'm running 3 with the exploit protection turned off which is why I posted that screen shot so you could see that you can run it but that particular tab must be turned off. Plus each time you boot you will be greeted by a popup notice that protection layers are turned off which you must ignore and close or you will re-enable the problem all over again which is remedied by just going back into settings and turning it off again. The forums at Malwarebytes state that there's an update .1280 that is supposed to correct for this issue but I only see .1269 when I download from them plus the internal updater says that its current so IDK what is up with that.
 
Interesting to note that MBAM Premium users are not yet being offered this so called upgrade.
 
Puffnstuff said:
When I rolled back to 2.21 the first time all I had to do was just uninstall it and reinstall 2.21 without using any unnecessary third party software.....
Click to expand...

To clarify; 'mbam-clean.exe' is written by the Malwarebytes company. It completely removes all traces of their products from the file system and registry and was written specifically to address the type of install/uninstall errors such as I experienced. I'd first used Windows installer to uninstall 3.0 followed by two attempts at reinstalling 2.2 but, the systray icon error persisted. As soon as I'd run mbam-clean and rebooted, mbam premium 2.2 installed normally and functioned perfectly.

@corkyg; you're absolutely correct because I'm also a premium account and it wasn't offered to me either. Nope...I inflicted this upon myself.

.
 
Last edited:
Bubbaleone said:
@corkyg; you're absolutely correct because I'm also a premium account and it wasn't offered to me either. Nope...I inflicted this upon myself.
Click to expand...

I noted this at the last upgrade. It does seem that they use the free version as a sort of beta debug edition, and when the dust is all settled, they will auto update premium users. I took note of your fix for possible future use. Thanks for that.
 
Elixer said:
You would think such issues would have been sorted out before the launch of 3.0.
Click to expand...
I absolutely agree with you. Paying customers shouldn't be treated as beta testers and this issue mirrors a hypothetical scenario I had to deal with in a business class not so long ago. There are some overly ambitious people at that company that failed their fiduciaries to the customers by releasing this not ready for prime time software in the name of profits. When I read their forum postings I saw that they'd released a version that supposedly addressed these issues but I cannot find a link to it anywhere on their website. The version on my pc is still the same as the download and no updates since that time have occurred to the software itself just the signatures. I don't like having to run with the anti-exploit disabled but if I don't none of my web browsers will work and I'm still having periodic issues with them as now I can't print coupons.
 
Here's the link to the .1280 build that addresses the anti-exploit issue while running Kaspersky based AV.

Edit: I just tried it and IE still doesn't work with AE enabled. I'm about to roll back to 2.21 and call it a day.
 
Last edited:
Removed that standalone AE installer and Malwarebytes 3 then reinstalled 2.21 and it works again. Do not install 3 unless you are a glutton for punishment. I'll be looking for a replacement to it in the near future. Malwarebytes continues to blame Kaspersky anti-virus for the issue but I'm having my doubts about this.

If it were solely Kaspersky's fault then 2.21 wouldn't work right either. The issue is with their anti-exploit software which I'm not happy about. That stand alone installer wouldn't even allow IE to launch before it turned an error. They've really screwed the pooch on this release.
 
Last edited:
The other issue I was having with 3 was that tabs would randomly crash on me no matter what browser I was using. Since moving back to 2.21 I've not had a single tab crash further establishing in my mind that 3 is still a beta that should've never been released to the public as a reliable product..
 
They must have changed it, I have MBAM premium on one PC, and 2 free versions on 2 PC's... and v3 hasn't been included on any updates. Maybe they figured it out using the general user public wasn't good beta testing policy.
 
Charlie98 said:
They must have changed it, I have MBAM premium on one PC, and 2 free versions on 2 PC's... and v3 hasn't been included on any updates. Maybe they figured it out using the general user public wasn't good beta testing policy.
Click to expand...

That's a bummer because v2 is really great. MSE/Defender + MBAM v2 + Chrome is a pretty nice combo for most people.
 
I think that I'm gong to switch to Bitdefender total security 2017 and completely remove the 3rd party software from my pc's.
 
PliotronX said:
They're just taking a cue from Microsoft 😛
Click to expand...
The fact that they can't be bothered to create a fix for this issue speaks volumes to me. Then the supposed fix they released in stand alone form does the very same thing shutting off internet access to browsers.
 
I had that problem when I updated to Spybot V2... it was so bad I rolled it back to V1. I recently gave it another spin and it seems to have been ironed out.

I like MBAM, I'll just keep rolling with V2 for a bit...
 
I've been using it since it became available on Server 2016 and Win8.1 without problems, both use IE.
I am currently using 3.0.5.1299
Everything is turned on in "Protection", the only thing that may be different is that "Potential Threat Protection" is set to "Warn User" (I always check for false positives).
It is set to update ever hour.
It's doing everything it is supposed to without any problems for me, just as 2.0 did.
So if you have questions or want to compare settings .....

Additionally it honored my lifetime licenses, just as 2.0 did.
 
You must log in or register to reply here.
Back
Top