This is posted
STRICTLY for informational purposes.
MalwareBytes Anti-Ransomware is currently undergoing
BETA-testing. It is
NOT a final release, rather it is meant to find and fix bugs (first betas are guaranteed to have bugs). Anyone who downloads and tests it should (1) know what they are doing and (2) consider themselves a "guinea pig".
QuoteAs this is the very first beta we do encourage beta users to install the product in non-production environments for testing purposes.
https://blog.malwarebytes.org/news/2016/01/introducing-the-malwarebytes-anti-ransomware-beta/
https://forums.malwarebytes.org/index.php?/topic/177751-introducing-malwarebytes-anti-ransomware/
I don't know. I personally feel ransomware is just another form of malware. Therefore I don't understand why the code to stop it isn't included in the anti-malware programs - except to scare/intimidate users and bring in more revenue for the makers. :(
I don't want to get back to the times with XP when we had to have separate anti-spyware, anti-virus, anti-Trojan, anti-this and anti-that installed on our systems, hogging all our system resources and bogging down performance.
Based on the number of f/p's that have been reported, it might be a good idea to wait a bit before trying the beta. If anyone does decide to give it a try, most definitely create a system restore point before installing.
via ky331: https://forums.malwarebytes.org/index.php?/forum/172-malwarebytes-anti-ransomware-beta/. Just scroll down the page and see the names of some of the programs being blocked.
Yeah, that is not just a lot of FPs, but major name programs being blocked too. Chrome, FF, ESET, CCleaner, McAfee, .Net Framework and more. It seems like there should be some more in house beta, if not alpha testing first.
From the discussion topic at BC (http://www.bleepingcomputer.com/forums/t/603378/malwarebytes-anti-ransomware-beta-feedback-and-discussion/), posted by the developer, Nathan/DecrypterFixer, beta 2 has been released with improved rules to prevent false positives on legitimate software. I also noted the following statement by Nathan in that thread:
QuoteThis will eventually be incorporated into mbam as a update. The last beta will likely become the stand alone.
Beta 2 is still producing numerous FP's
QuoteThis will eventually be incorporated into mbam as a update.
Great news! That made me so happy, I was forced to add my 2¢ worth. Thanks, Corrine!
For those interested, Beta 3 has been released: Beta3 released (https://forums.malwarebytes.org/index.php?/topic/178274-beta3-released/). If testing, remember, the program is still beta so please remember to create a fresh System Restore point before installing.
beta5 (build 0.9.14.361) change-log
Known Issue:
• If installing the upgrade on Windows 8.1 x64 over a previous Beta, the service may not start automatically. In this case, simply click Start Protection on the Malwarebytes Anti-Ransomware dashboard or run the Beta installer a second time.
Improvements:
• Improved internal log format to better distinguish between the various Anti-Ransomware beta versions
• Adjusted embedded license so that earlier beta versions could be expired and users would be encouraged to move off older versions and onto the latest available beta
Issues Fixed:
• Fixed issue that caused high-CPU and memory usage and resulted in a process crash in certain cases
• Fixed issue where the current state of the protection status was not remembered correctly after a reboot
beta6 - build 0.9.15.416
Malwarebytes Anti-Ransomware (BETA) 0.9.15
Known Issue:
• If installing the upgrade on Windows 8.1 x64 over a previous Beta, the service may not start automatically. In this case, simply click Start Protection on the Malwarebytes Anti-Ransomware dashboard or run the Beta installer a second time.
Improvements:
• Further refinements to internal rules to reduce potential for false positives
• Refactored processing to reduce memory consumption and prevent system hangs
• Added ability to update internal rules dynamically without requiring a full program update so new detections and fixes for false positives can be deployed much more rapidly
• Changed log collection to happen asynchronously
Issues Fixed:
• Notification that a new version is available no longer auto-dismisses
• Fixed issue where an Exclusion may not have been honored properly in some cases
• Fixed issue where the protection status was not remembered correctly after a program update