MBAM 1.60 released.

DOWNLOAD FREE: http://www.malwarebytes.org/products/malwarebytes_free

DOWNLOAD PRO: http://www.malwareby...alwarebytes_pro

Malwarebytes Chameleon technology:
Gets Malwarebytes Anti-Malware running even when blocked by infection.

Incremental updates (paid version only):
Smaller updates let you stay up-to-date faster! We've also improved the reliability and performance of the overall update process for all users.

Ability to password protect key program settings (paid version only):
Let only those you trust change settings

All trials have been reset:
We want everyone to have a chance to experience the full functionality of this release for 14 days. This will occur within one day of the release.

The database has been optimized:
It is now smaller and more efficient. There are fewer fingerprints, but that's because we consolidated many fingerprints into one. This will also occur within one day of the release.

Release Notes:

http://forums.malwarebytes.org/index.php?showtopic=3283&st=0&gopid=509999

Enjoy it.

Thanks Hernan!

Just to note that current MBAM users can upgrade internally to 1.6.
Users of the free version will have to do this manually, via the "Update" tab.

For users of the paid version, 1.6 will download automically, but a re-start will be required to complete the install (at least on Win 7 64 bit systems).

Malwarebytes Chameleon

Malwarebytes Chameleon is a set of new technologies developed by us to help get Malwarebytes Anti-Malware up and running on a system when it is prevented from doing so by specific malware infections.

To access Chameleon, open your START menu and click on All Programs > Malwarebytes Anti-Malware > Tools and click on Malwarebytes Anti-Malware Chameleon.

If your START menu is empty or inaccessible due to the infection, then you may alternatively open it through the Windows Task Manager. To do so, press Ctrl+Shift+Esc on your keyboard. Once the Task Manager opens, click on File at the top and choose New Task (Run). In the "Create New Task" box, click on the Browse button. In the window that opens, navigate to C:\Documents and Settings\All Users\Start Menu\Programs\Malwarebytes' Anti-Malware\Tools for Windows XP or C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Malwarebytes' Anti-Malware\Tools for Windows Vista and Windows 7, then click on the drop-down menu that says Programs and choose All files. Double-click on Malwarebytes Anti-Malware Chameleon.lnk (it will appear as a help file).

You may also open Chameleon directly from your internet browser by pressing Alt on your keyboard and using the File > Open or Open File menu and navigating to C:\Documents and Settings\All Users\Start Menu\Programs\Malwarebytes' Anti-Malware\Tools for Windows XP or C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Malwarebytes' Anti-Malware\Tools for Windows Vista and Windows 7, then double-clicking on Malwarebytes Anti-Malware Chameleon.lnk (it will look like a help file).

I let the MBAM internally update to the new version and then restarted. I then did a scan which came up empty. I got an alert from Outpost about some MBAM fie which I OK'ed. Then Avast 6 alerted to something that it referred to as a rootkit. This file is abbreviated in spots but it this is what I was able to see:

SVC:MBAMSwissArmy>C:\...\mbamswiss.. which was all that was visible. I am suspecting that this is just part of the new MBAM version. For now I had Avast ignore it but will be running several scans as a cross check. Did anyone else have this or something similar happen?

Dale.

Both Forum, Avast and MBAM, are advicing to add each other to thier respective ignore lists. Avast! to its File system shield, Web shield, and Behavior Shield, and MBAM every folder or file you can find of Avast!.

I also added Comodo, SAS, WinPatrol, SpywareBlaster, and CCleaner to each other for good measure.

Regards. 

this is what I was able to see: SVC:MBAMSwissArmy>C:\...\mbamswiss.. which was all that was visible. I am suspecting that this is just part of the new MBAM version.

Yes, Dale, that's MBAM's file.

Dale:

a little more info:

In your OutPost FW, click on Settings>General (upper left hand corner).
In the right pane, under Self-protection, click on the [Exclusions] button, to list applications that are allowed access to the FW components.
In the window that appears, click the [Add] button, and browse to the location of MBAM - usually:
C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
Click on mbam.exe, then on [open], and it should appear in your exclusion list.
[OK] out.
Repeat for mbamgui and mbamservice files in the same folder.

As for avast, you need to add the same MBAM files to its exclusions, and avast to Mbam's exclusions.
Instructions to do this are here:
http://forums.malwarebytes.org/index.php?act=findpost&pid=417798

Finally, if you use Windows Defender, you should add to its exclusion list (Tools>Options, under Advanced options, click on the [Add] button, browse to the following files) and add them to the window in much the same way:
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\mbamswissarmy.sys

I updated MBAM on Windows 7 SP1 and on two XP SP3 systems (one is a Dell laptop 9 years old). There were no problems and so far all is running smoothly. Apparently, some folks had update issues: See: http://www.wilderssecurity.com/showthread.php?t=315062

Eventhough there is nothing about a problem between Avast and MBAM in Avast! Forum, Advancesetup ( Ron Lewis ), MBAM administrator, reported a problem today.

 http://forums.malwarebytes.org/index.php?showtopic=103131&view=findpost&p=510602

He did not said what was wrong, but he stated that the problem was fixed with the lattest Avast definition update. However, I did not find a fixed data update in today Avast defininitions:

http://www.avast.com/en-us/virus-update-history

I can not tell if it is ralated to Dale's reporting that Avast detected mbamswiss as a rootkit. Mbamswiss is definitely a MBAM file as Bugbatter said, but not only for this new 1.60 MBAM but also for the the past 1.51 MBAM.

Regards.

Just reporting that I did not encounter any problems/conflicts with the new MBAM , along with Avast!6.   FWIW, I have NOT implemented any of the Avast/MBAM "exclusions" listed in "Section K" (in case this links elsewhere)  http://forums.malwarebytes.org/index.php?act=findpost&pid=417798

No problem installing on my backup computer with XP, except for Outpost asking for an OK, not a peep from Avast. On the computer with Vista, the problems I mentioned above cleared up by themselves with me not making any adjustments or exclusions. :emotion-1: