Latest Version of Malwarebytes

I just ran a scan of a few files from the context menu. In v1.75, they would take a few seconds to scan. In v2, they took over a minute, then the program temporarily froze when I tried to exit after the scan had ended. I refrained from instantly going back to v1.75 because I thought I just needed time to settle in with v2, but this has been a very disappointing experience, so I may remove this version soon.

andrew129260 said:

Sorry, my post was not talking about the bsod. I was talking about the multiple other bugs. I understand the testing phase/process quite a bit, and I believe that any decent company should have had this tested better then what was presented here.

I also am seeing bug reports on multiple things on malwarebytes forums that I have been able to reproduce, and have sent in bug reports via email. I get that there are thousands of possible ways for a system to be configured, but some of this stuff was clearly not tested at all. A majority of these bugs is not even caused by third party programs being the reason. Which is another point that eradicates the whole excuse that they didn't have enough users to test.

Scanning is the the whole point of this software, if it cannot even do that well, what is the point?

Also, its pretty bad that in a VM and clean install of windows and just their product, I find TEN bugs in their software by using it for 5 minutes. 10!

I just don't get it. What was malwarebytes thinking here?

UsernameIssues said:

ThrashZone said:

I have to agree with Andrew,
This is pretty basic stuff,
Upgrading = failure in allot the licenses being acknowledged protection mode disabled,
Custom scans including rootkit = did no one ever use this

The only solution offered so far as I've seen is use mabm clean ?

I've only been reading this thread - not the threads on the mbam forums - so maybe I missed what you meant by "Custom scans including rootkit = did no one ever use this". Can you please elaborate?

I believe they were referring to the multiple freezing and some files being accidentally skipped when supposedly scanning when this feature is enabled.

I was not aware of your findings. Then yes, they should find any flaw that shows in a clean VM.

Where has it been shown that mbam skipped files that were supposed to be scanned? Hopefully that idea did not come from my posts. I did mention that the GUI skips some files, but the scans seem to have been made per Process Monitor.

Yes, the freezing should have been fixed before releasing v2, but I've yet to see it totally halt. I wonder if they knew about that and opted to release it anyway. Do you know if that issue has been mentioned in their forums?

Someone reported on the MBAM forum they found their scan freeze is caused by moving the USER folder.
Read more at MBAM2 freezes when performing a Threat Scan

A Guy said:

If it freezes and slows down our PCs, which are generally higher performance, I wonder what the "average" PC is like. I really won't bad mouth MBAM. I have uses it, 1st free, then paid since it 1st appeared. It has been an extraordinary program all that time. If indeed others are experiencing these issues, then I trust they will fix it. My particular BSOD on rootkit scan could be limited to my own machine. I never had any issue with the older version, so that is my expectation for this new one is all. A Guy

My test box has an Old AMD dual core 5600+.
V1 Quick scans were about 2 minutes faster than V2 Threat scans (with Rootkit enabled).
PC is still usable during the scan and no freezes.
I've been using MBAM 2 since pre-Beta on a Win 7 x86 OS ...

For me, V2 is better.
For people I support, I suggest they wait before updating to V2 as there are many issues reported ...