Updates 10/13/14 - MBAM

While I still haven't downloaded/tested the new version, I'd like to call attention to a change in behavior, which I believe is detrimental:

Under Settings/ Advanced Settings, there is an option:

Automatically quarantine detected items: When unchecked, any threats detected will not be quarantined immediately. A notification will instead be presented, and you must choose how to respond. If you do not respond within forty (40) seconds, the threat will be quarantined automatically.

In other words, the choice now is really between INSTANTANEOUS quarantining vs. DELAYED quarantining (unless user intervenes promptly) [rather than between "automatic" quarantining vs. MANUAL quarantining, as it had been].

The issue is being discussed/debated here:  https://forums.malwarebytes.org/index.php?/topic/158478-auto-quarantine/

Malicious Website Protection is not enabled, and cannot be enabled:
https://forums.malwarebytes.org/index.php?/topic/158692-malicious-website-protection-disabled/

Also I cannot run any Scans. I think this latest update is broke.

This has been an issue, as reported in http://www.wilderssecurity.com/threads/malwarebytes-anti-malware-2-0-3-1025-released-today-october-13-2014.369193/

Quoting two key posts there:

From Marcin:  "Hi guys, we're having issues with one of our CDN providers and the syncing with our origin servers. It's causing sync issues on the client as well. We're working as quickly as we can on this!"

From AdvancedSetup:  "If you are receiving a message inside the MBAM program that Malicious Website Protection is disabled please do the following to correct the issue.

•On the Dashboard click "Update now" to get the latest database version
•Right click the Malwarebytes tray icon and click "Exit"
•Restart the Malwarebytes application from the programs menu or desktop shortcut.
•In most cases this resolves the issue, however if the issue still persists, reboot the computer and the issue should be resolved.
•If the above procedures still do not correct the issue for you then please download the MBAM installer  http://www.malwarebytes.org/mwb-download/ and reinstall the program which will fix the issue for you."

I don't believe this is an issue related to the new program version 2.0.3.1025... because I still have 2.0.2.1012, and am experiencing the same problem (Website protection disabled).   I can click on the button to enable it on the Settings / Detection and Protection tab; and also, separately, by RIGHT-clicking on the MBAM icon in my system tray; and even doing both, the dashboard is still not acknowledging this.

So I would tend to hope it's a server/definitions issue, as had been asserted above.   I have no plans to "mess-around" with what may turn out to be needless reinstallations.

By the way, having accessed the test website for protection, I can confirm the Malicious Website protection is indeed OFF, despite my having clicked both option locations to enable it.

Marcin (or someone else from MBAM) offered a fix:

Delete (or just rename) the file C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware\RULES.REF

Exit and restart MBAM.  (I opted for a reboot to do this).

The red warning is initially still there.

Open MBAM, to update its database.

Then enable Malicious Website Protection.    It should "stick" this time.

Hopefully, this is a one-time fix that will survive reboots... time will tell.

These steps worked for me....

•On the Dashboard click "Update now" to get the latest database version
•Right click the Malwarebytes tray icon and click "Exit"
•Restart the Malwarebytes application from the programs menu or desktop shortcut.
•In most cases this resolves the issue, however if the issue still persists, reboot the computer and the issue should be resolved.

Still on version 2.2012

I was finally offered the program update on my win7 system, accepted it (keeping my fingers crossed), and all appears mostly well so far.

The only "issue" is that   Delay Protection at Startup for 15 seconds   [under Settings / Advanced Settings] is checked... and if you uncheck it, it will re-check itself (upon reboot).   Some people are alleging the problem is merely in the GUI (Graphical User Interface), but not in the actual programming/running.   If it is implementing the delay, I can't say I noticed it.

EDIT:   for more information, see https://forums.malwarebytes.org/index.php?/topic/158699-malwarebytes-15-second-delay-on-startup-cannot-be-unchecked/page-2#entry890275

Finally got my download today, didn't notice any problems. I noticed the "scan for rootkits" box is not checked by default. Should I turn it on and run a scan?

"Scan for rootkits utilizes a specific set of rules and tests to determine if a rootkit is present on your computer. For readers who unfamiliar with this term, an explanation may be handy. A rootkit is malicious software that can be placed on a computer which can modify operating system files in a manner that hides its presence. Malware detection methods that rely on hooks to the operating system for detection and analysis would prove ineffective if the hooks had been purposely manipulated by the malware. Our testing method is more intensive and more effective, but including rootkit scans as part of your overall scan strategy increases the time required to perform a scan."

Dale,

I guess it couldn't hurt to run a rootkit scan (once)... but if anything is actually found, you might want to consider inquiring about it (getting help) before removing it.

For what it's worth, I have the rootkit scan box checked.  

I believe you have the paid version of MBAM?   If so, you should have continual (real-time) protection.   On that basis, I would NOT advocate "routine" scanning... rather, I would only scan if something seemed to be wrong on your system.

Bit of a problem here. Yesterday, I think I ran a scan with the rootkit scan enabled. Can't remember for sure, but the system froze and I had to do a manual shutdown. After restart worked fine. However, today, I noticed four items in quarantine...three of that Conduit pest and one of..xxx.Candy..something or other....

I suspect these are the same remnants that show up in Hitman Pro scans, and up till now, on no other scans. I went ahead and deleted them and started an easy scan, and walked away from the computer for a few minutes. When I got back I found a BSOD, but didn't write down the error code. So...hard shutdown and restart. Everything came back normally. I decided to see if the remnants would show up again, so ran one more quick scan.

This went normally except  toward the end of the heuristic scan, when it froze with no BSOD. Tried  the three finger restart  and the screen then went black. One more hard shut down and restart. Everything seems to be working fine, but decided to quit trouble shooting for the night. Don't know if this has anything to do with the new version or not. Those malware remnants seem cause to no problems, so I just ignore them when I run Hitman Pro. AdwCleaner doesn't get rid of them.

Dale,

I just heard from Hernan (Iroc9555), and he's also reported a BSOD with MBAM:

https://forums.malwarebytes.org/index.php?/topic/158863-bsod-and-error-during-heuristic-analysis/ 

So far, I don't seem to be impacted, even running rootkit scans.   (But in the back of my mind, I think it may have happened once, many months ago???  If so, it obviously wasn't with the same/current version.)

If you open MBAM, go to History, then Application Logs, you should see a list of your Scan Logs --- unless they were "lost" during the BSOD... so you can open it/them to see whether or not you had rootkit scanning enabled or disabled (lower left-hand box summarizing scan options).   Hope this helps somewhat.

Well...I did a regular scan without the rootkit option awhile ago. Everything went fine until 13:12 into the scan, then it quit counting. Highest object eached 255300. A bit before this happened my online radio went silent with the count at 254200 objects. I attempted to access its page to reset it but could not. Not sure of the key sequences I was doing, but after trying to go to Task Manager, the radio came back on and the count had reach the 255300. Then it all froze again, with the radio working when I had to do a hard shutdown and restart.

I had it start normally, then in a little bit the system wanted to do a ChkDsk. The results page went by too quickly to read, but it has started OK and is now running so I can type this. I'm gonna go browse the MBAM boards to see how many people beside IROC and me have had this problem. I suspect it is something in the new version, since the previous one worked fine.