Discussion in 'other anti-malware software' started by puff-m-d, Nov 14, 2016.
Still using 100% CPU during scans!
It was the self-protection module
I updated to the latest Windows Insider build a few days ago. Since then I have been running 3.0 with anti-ransomware mode enabled and am not seeing those files in my SVI folder anymore. anybody else noticed this with newest insider build?
We are still working through all the issues being reported. Even though the various 3.x versions have gone through extensive QA, private beta and public beta processes, these issues did not show up until after release of each new version.
I understand all of your frustration and apologize while the teams work these bugs out. If you are unhappy with Malwarebytes I do want to stress that we have a no-questions-asked refund policy. It doesn't matter if you bought yesterday or 5 years ago. If you want a refund, contact me and I'll make sure it gets processed.
I do not, or ever did, wanted a refund. I've been more than satisfied with MB v1 and v2. Version 3 however, has some issues.
Thanks for keeping us informed of what MB in doing. Hope to see v3.1 soon that will address these problems.
Same here. Even if I did remove V3 completely for the time being, I am looking forward for a new version which I am confident the problems will be solved.
Agree with Robereyewhy and Antarctica - I have used MBAM for years and appreciated and depended on it - that's whey I have licenses for 3 home pc's. Your (MBAM) statement on here helps considerably in quieting THIS restless user. Thanks.
They are back
Thanks for the update; looking forward to the next release
On Win Insider Preview version, Defender is being turned off as MBAM is registering itself as an AV in the Action center.
This can happen if for whatever reason Defender is reporting in WAC as outdated. This condition can be the result of pending Windows Updates for example.
there is rumor about killing some WISE software detected as PUP/PUM. any news for it?
adwcleaner is now detecting too.
In my case the software isn't affected, however, the MBAM scan points out that it is a PUP and the "ignore always" button won't cause the scan to ignore always, so the warning reappears with each scan. I had this issue w/Auslogics defrag as well.
Try adding them to the exclusions list.
Thanks, but with all the other v3 problems, I'm waiting for a fix to the scan results' "ignore always" exclusion. My short term solution is run MBAM only on demand.
I went back to V2 long ago and will wait for V3 to get better.
The Malwarebytes 3 releases to date have so far been disappointing, I guess this is not a total surprise, essentially it is a combination of efforts from three different program teams.
Unfortunately the suspicion is that at this moment in time, it appears no one person at Malwarebytes understands how to resolve its internal failings.
Just in case anyone running HMP.A has missed it:
Does anyone know if we can edit and or remove programs added to Exploit Protection now with 3.0.6? I know it wasn't possible with an earlier build.
3.0.6 does allow editing/removal to programs added to Exploit Protection. -Jack
Thank you, SAJack.
I have to say that I am having a MUCH better experience with MB 3.0.6 this time around. I haven't had any issues at all using Windows Defender + VoodooShield and the latest HitmanPro.Alert RC build 582. This machine isn't experiencing the slow down it had previously either.
My advice though is to completely remove MBAM 2 using mbam-clean.exe, restart BEFORE installing MB 3. Have your key handy.
As always, your mileage may differ.
@anon Thanks, I hadn't seen that. Installed w/o PUPs. Recently switched to portable version.
MBAM 3 continues to make me insecure about website protection - it shows web protection on but clicking on test sites indicate different things - not consistent. I am uninstalling MBAM and restructuring my pc programs until I hear everything has been fixed in MBAM. I really hate to do this as I've had MBAM for years, and have lifetime licenses, but it's not worth the frustration and uncertainty.