Jump to content

Malwarebytes Anti-Malware 2.0.3 Released


Recommended Posts

  • Staff

Greetings :)

I'm proud to announce the release of our latest version of Malwarebytes Anti-Malware: version 2.0.3 for consumers.

This release is heavily focused on the fixing of bugs, accessibility and squashing new malware. It is now available for download from here.

For the time being, in order to balance server load, we'll be throttling upgrades for existing Malwarebytes Anti-Malware users when they check for updates, but if you'd like to get the new version immediately, go right ahead and download it from the link above and install it over your existing version.

As always, if you encounter any problems, bugs or issues please report them in a new topic here or contact our Support team directly here. Also, feel free to check out our user guides and FAQs located here.

We also plan to make some major changes to our user interface (UI) in our next release, Malwarebytes Anti-Malware 2.1.0 which is due out early next year so keep your eye on our newsletter, social networking pages and of course our forums here for more info as it becomes available. We've got some exciting changes in the works, and we'll definitely want to be showing them off as they get closer to completion :)!

Here's the list of changes for this release:

New Features:

• Scans may now be set to run as lower priority processes to improve multi-tasking under Advanced Settings

• Added support for keyboard navigation of user interface

• Added support for JAWS and Windows Narrator screenreaders

Improvements:

• Malwarebytes Chameleon enhanced to be more effective against active malware infections in getting Malwarebytes Anti-Malware running

• Notification for outdated databases now configured to 7 days by default rather than 1 per user feedback

• All scans with Malwarebytes Anti-Malware now create an entry in protection logs

• Failed update checks are now logged in protection logs

• Updating Malwarebytes Anti-Malware should now function even when the Scan tab is awaiting action from the user

• Support for scanning encrypted drives improved when rootkit scanning is enabled

• Upgrading to new versions of Malwarebytes Anti-Malware should no longer prompt for a system restart

Issues Fixed:

• Google Chrome users should no longer experience Malwarebytes Anti-Malware getting stuck or hanging during heuristics scans with Malwarebytes Anti-Malware

• Scans should no longer hang during filesystem objects scan on some systems

• Several crashes in Malwarebytes Anti-Malware fixed

• Runtime errors during installation or upgrade of Malwarebytes Anti-Malware should no longer occur

• Rootkit scanning should no longer flag sectors on non-system volumes as forged when those volumes are encrypted

• Rootkit scanning should now work properly on Bitlocker encrypted drives

• Scanning TruCrypt encrypted system volumes with rootkit scanning disabled no longer results in the filesystem not being scanned

• Issue with repairing rootkit infected drivers on Windows 8 and Windows 8.1 fixed

• BSOD when using Driver Verifier software on a system running Malwarebytes Anti-Malware fixed

• BSOD when using Boxcryptor software fixed

• BSOD when using Malwarebytes Chameleon or self-protection in Malwarebytes Anti-Malware under certain conditions fixed

• Malwarebytes Anti-Malware should no longer crash when using the "Copy to Clipboard" function under certain circumstances

• Dashboard banner text should now reflect language changes in Malwarebytes Anti-Malware instantly

• Several issues with tray notifications fixed

• Display problems with some languages fixed

• Malware Exclusions and Web Exclusions should no longer display duplicate entries following database updates

• Occasional crash of MBAMService when upgrading from version 1.75 of Malwarebytes Anti-Malware should no longer occur

• Several issues with the right-click "Scan with Malwarebytes Anti-Malware” function fixed

• Several problems with access policies fixed

• Several UI performance issues fixed

• Several UI and user experience enhancements implemented

• More than one Malwarebytes Anti-Malware tray icon should no longer be displayed on system start under some circumstances

• Issue with Malicious Website Protection not enabling after install under some circumstances on Windows Vista fixed

• Minor display issues with tables within the UI fixed

Link to post
  • Replies 123
  • Created
  • Last Reply

Top Posters In This Topic

Version 2.0.3.1025 has a bug that shows the Malicious Website Protection as disabled and it cannot be activated.

 

This is pretty alarming.

 

Also, after running a HyperScan, it fails, and you click the "Show Detailed Log" and it just open a desktop Explorer window.

I am having the same issues. Got a notification an hour ago saying Malicious Website Protection is disabled. Whenever I try to enable it, nothing changes. The same also happens when trying to run a HyperScan. 

 

It's currently running a scheduled scan, but I'll see if it even manages to complete it or if another error will occur.

Link to post

Version 2.0.3.1025 has a bug that shows the Malicious Website Protection as disabled and it cannot be activated.

 

This is pretty alarming.

 

 

Agreed... I am having the same problem after updating to 2.0.3.1025

Dashboard shows that Malicious Website Protection is disabled. "Fix Now" button does nothing.

 

TLHTbnM.png

 

Under Stettings -> Detection and Protection and Protection, Malcious Website Protection is enabled:

fsJijhb.png

 

And on the Taskbar pop-up Malicious Website Protection is showing as enabled.

 

jR04bWP.png

 

I currently also run Avast! Internet Security and have had no problems running it cincurrently with MWB Premium.

Link to post
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.