Malwarebytes' Anti-Malware 1.41

[DKT27]

It's posted here by mara-

[jalaffa]

Excellent DKT27 - you make me proud :)

[harpua]

Oh yeah, it was Mara. I edited my post above to reflect that and give credit where credit is properly due.

Here's the actual instructions he gave:

Registry Switches for Controlling IP-Blocking in MBAM 1.41

Create the indicated registry value (labeled as key | value) with the indicated data and reboot to enforce the policies below. All of the values are of type DWORD. In order to create a registry value, open the Registry Editor (Start -> Run -> regedit), navigate to the key listed, and then right-click in the right-hand panel and choose New -> DWORD.

1) HKEY_LOCAL_MACHINE\Software\Malwarebytes' Anti-Malware | silentipmode

Description: With a DWORD value of 1, the protection module will block and log IPs silently.

2) HKEY_LOCAL_MACHINE\Software\Malwarebytes' Anti-Malware | startipdisabled

Description: With a DWORD value of 1, IP blocking will start disabled on reboot, although it can be enabled subsequently.

3) HKEY_LOCAL_MACHINE\Software\Malwarebytes' Anti-Malware | disableipblocking

Description: With a DWORD value of 1, IP blocking will be permanently disabled (cannot be toggled).

Note that, on 64-bit editions of Windows, the registry values that AdvancedSetup mentioned are located in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Malwarebytes' Anti-Malware <br style=""> <br style="">

[DKT27]

Thanx. :)

I know it because it's not the first time I've searched for it. I've given that link to many people who needed it. :)

[harpua]

So could someone advise whether it has really been fixed in 1.42 or is it still advisable to keep IP protection disabled in the registry?

[DKT27]

I think that it has a new feature that you wont need to disable it even from registry (manually). See the changelog. Well I would have given the answer but I don't wish to restart my PC now.

[harpua]

Being able to ignore individual IP's is not sufficient for me. Overall, I think the IP protection is a pretty useless and worse, annoying feature. Unless it can be permanently switched off from within the program, I'm not re-enabling it from within my registry.

[LeetPirate]

Being able to ignore individual IP's is not sufficient for me. Overall, I think the IP protection is a pretty useless and worse, annoying feature. Unless it can be permanently switched off from within the program, I'm not re-enabling it from within my registry.

Last time I used this it kept restarting the IP protection at each boot, I also believe it to be useless and annoying so I got rid of MBAM.

[harpua]

As I said, if you disable it in the REGISTRY, it is gone for good. It isn't even in the MBAM menu as an option after the registry mod.

[LeetPirate]

As I said, if you disable it in the REGISTRY, it is gone for good. It isn't even in the MBAM menu as an option after the registry mod.

I see. If only I had known this long before, it's too late now for me and MBAM, we're divorced, I prefer Microsoft Security Essentials now. :rolleyes:

[harpua]

Up to you. Only takes a minute to install and a couple of minutes to do the registry mod. There is no better app to find and automatically remove malware that has gotten into your system, imo. MSE does not have enough configuration options to suit my tastes. I prefer ESET AV to that. But MBAM is in another class of antimalware apps, imo, and is more of a remover than a preventer. MSE and ESET AV are more geared to preventing infection in the first place. Both types are useful and have their place, imo.

[LeetPirate]

Up to you. Only takes a minute to install and a couple of minutes to do the registry mod. There is no better app to find and automatically remove malware that has gotten into your system, imo. MSE does not have enough configuration options to suit my tastes. I prefer ESET AV to that. But MBAM is in another class of antimalware apps, imo, and is more of a remover than a preventer. MSE and ESET AV are more geared to preventing infection in the first place. Both types are useful and have their place, imo.

I had too many false positives with MBAM, it always tried to kill keygens and password crackers. The one time there was an actual virus guess what happen? MBAM failed to even detect it but MSE caught it. NOD32 detected it but failed to remove it.

[harpua]

It's worked great for many infections I've removed from others machines I've been called upon to fix. I agree it FPs keygens and cracks a lot, but so do many other malware apps. I can usually tell which are FP's and which are the something to worry about. If in doubt, there's always virus total. There's always going to be that one piece of malware that this app or that app fails to detect. Next time MSE might fail to detect something that the other apps catch. Same can be said for every AV app out there. But everyone should use whatever they are most comfortable with. MSE doesn't do it for me, just as MBAM doesn't do it for you. But as I said, MBAM is not designed to be the only AV software one should have on a system. I view it as an adjunct to a main AV app like ESET or MSE or Avast etc.

But all I'm saying is that, for those who haven't entirely "divorced" themselves from MBAM yet, the faulty IP Protection module is no reason to avoid the application or disable the real time protection because, fortunately, IP Protection can be completely disabled so that it doesn't even load as part of the app.

[DKT27]

MBAM is more better than any AM program ever. I haven't kept it's live protection ON but it's scannin cannot be compared to any other.

[Sl@pSh0ck™]

I agree that MBAM is one of the most effective antimalware there is, but it is quite a resource hog compared to other antimalware, I have opted to keep it as an on demand AM and settled for threatfire as my back up real time scanner for norton AV.