MalwareBytes or SUPERAntiSpyware?

chrisaroz

Member
Reaction score
3
Curious what everyone's preference is. I'm a fan of both, though MalwareBytes has a better GUI IMO. Is anyone selling either of these? Why did you choose to go with one over the other?
 
super is more thorough which is why it takes longer. Malwarebytes has habit of fubarring systems. Lately I've just been selling avg since it has both spyware protection and virus protection.
 
Blue screens of death on startup usually or can't start because blah blah registry error etc. The usual. System would boot fine before running it then afterwards it's bricked.

How does it FUBAR systems? Never had it do that to me? :confused:
 
I must say, I have never had MBAM mess up a system in any way after a cleanup and I can't count how many times I have used it.
 
I'm with MrUnknown, used MBAM countless times and it's NEVER messed a system up that I've used it on.
 
I am yet to see issues after using MBAM.

I have not endorsed one over the other but have found myself using MBAM much more often than SAS.

Found this article...if someone wants to read it.
http://www.besttechie.net/2009/05/27/malwarebytes-vs-superantispyware/

Seems like a fairly decent review, though I have to admit I'm never a fan of articles like that on sites that seem to have a notable bias. Checked out the malware report, and pretty much every single threat I looked at had the solution. Download and run malwarebytes. Even beginner users shouldn't need to look up the ones that the scanners can kill out of the box.
 
My personal thought is that, for a machine with more than a simple MyWebsearch type "infection", you need BOTH Mbam and Sas.

On infected machines, I always run Mbam first because it will usually install when viruses are blocking Sas from installing. After Mbam installs and reboots, I run Sas and it finds tons of bad stuff Mbam didn't. Reboot, back to Mbam...you get the idea. Oh and obviously, I check for updates every time I reboot.

I've run Mbam (or Sas) two times in a row with 0 infections found, then run the other program and find several more infections that were undetected by the other. Pretty amazing, but I like them both.
 
I agree with Appleby, you do need them both as they find things the other doesn't.

I just wanted to state that I have never had MBAM mess up a system. It only removes things that are known to be bad, so I can't really see how it could cause a bluescreen. It is possible it may have removed something that a rootkit wanted and on reboot, the rootkit couldn't find it and it caused a bluescreen, not sure, but that wouldn't really be MBAM's fault.

I haven't had SAS mess up a system either.
 
+1 Appleby.

What a silly question, MBAM v SAS.

That review site is suspect too.

Quote about scan time didn't mention if either or both were in quick or deep scan mode.
And the statement that they are the only apps that do the business is probably actionable.

Pretty shallow review.

They are complementary and happily co-exist. Together they make a great team.
 
Last edited:
Also, as for Mbam messing up a system....knock on wood...never had it happen yet. However, I have ran Mbam on some severely infected hard drives that I slaved to my laptop and on 3 occasions, after removing the infections Mbam found, Windows would not boot properly to the desktop. Two of the times they user account logon files were damaged and I can't remember exactly what happened on the 3rd time. On the first two I had to do an XP repair install which fixed the problem but it was very time consuming.

But again, these were slaved drives and I don't know how much can be blamed on Mbam or on the infections, however both were (barely) bootable to the desktop before.
 
.

From my experience, Internet Security 2010 was on a PC, I used MBAM and it cleaned the system but as I noticed that it cleaned winlogon32.exe which replaced the userinit.exe Key in the registry. If someone doesn't know to go back and change that key from winlogon32.exe to userinit.exe then the system wouldn't boot, and therefore the "End User or Tech" could Blame for deleting a file that the registry is looking for for bootup.
 
Excellent post Techno. I have had that happen a couple times doing some manual removal and it took some googling for me to figure out the fix. Great info sir.
 
Thanks Appleby.

I hope this info helps others down the road. I currently have a client, who has the ndis.sys rootkit, but the client is remote, and I tried alot of tricks to try to fix it remotely, but the customer will have to bring it to me.
 
my "1 2 punch" is MBAM and then ComboFix - between the two of them my clients have clean computers

(usually!lol)
 
Back
Top