It probably should have stayed in Beta for a lot longer of a time period. It has proven, both during Beta AND after release (IMHO, should have never been released) to be a very buggy and unreliable solution.

What a thrill it is to find this out!! Thanks again.Ĭraig, pls don't make the mistake that because MBv3 exists, you need to have it. MBAM took $25 Anti-Exploit Prem Renewal from me on Dec 4 (via Cleverbridge) for a product that is then - DELETED - by FREE-to-Me - MBAM 3.0 Prem - RELEASED JUST 4 DAYS LATER. Thank you for educating me that MBAM 3.0 even exists. I haven't yet upgraded to V3 and have no current plans on doing so. Thanks for posting and thank you for the heads up. It is recommended, until the bug is fixed, that you disable the MBAM Anti-Ransomware module, when you run your MR backups, and then re-enable the module once you have exited MR. The integrity of the MR backup is unaffected, but remnants are left in the System Volume Information folder, consuming disk space. The thread over at the Malwarebytes 3.0 Forum can be found here. There is a known bug in all builds of MBAM Version 3, to date, that result in your hard disk space being decreased because MBAM is conflicting with MR, and other services using VSS. Just a note for those of you who are using the new Malwarebytes Premium Version 3 (current iteration 3.0.6.).

Malwarebytes 3.0 premium