mbamnet.dll & mbamcore - Trojan horse BackDoor.Generic13.YXM ?

[AdvancedSetup]

AVG should have this fixed in the next couple of hours from now. Please check for AVG updates in a couple hours and that should hopefully then correct this issue.

[Mainard]

Hello all!

In case you do not have this already set for exclusions:

To exclude using AVG 2011:

Step 1: Run AVG

Step 2: Click Tools->Advanced Settings

Step 3: Click on the side-bar Resident Shield-> Excluded Items

Step 4.1: Add Path: C:\Program Files\Malwarebytes' Anti-Malware\

Step 4.2: Add File: C:\WINDOWS\system32\mbam.sys

Step 4.3: Add File: C:\WINDOWS\system32\mbamswissarmy.sys

Step 5: Click Apply and OK.

[breakingwave]

I tried all the suggestions in this thread without success. I finally rolled back to version 1.46 and had success. This does not make me comfortable with installing upcoming new releases as an early adopter. I am disappointed in Malwarebytes. We own two licenses here at home, but I am not sure I would pay for it again.

[Wide_Glide]

This was not caused by Malwarebytes' but by AVG and their updates, so why talk bad towards Malwarebytes'??????

I also have 2 Pro Versions of Mbam and a Free version installed on a Test PC and have never had any issues with none of them.

Now, I do not use AVG either, you can see that from my signature below. All exclusions were added and well no probs whatsoever!

Thank You,

[cains]

I tried the fix from the second post in the thread and got Malwarebytes running again. I updated and scanned and Malwarebytes found nothing. But, when I scanned with AVG again, it pulled the same files out of Malwarebytes. I restored the files again from the virus vault. I'm leaving AVG running but not scanning with it for a few days so maybe the AVG folks will get this fixed.

Yea robin thats the same thing for me My malwarebytes runs fine its just the avg scan when i run it, it finds the malwarebytes false alert. i am also leaving my avg running and not disableing it, it only shows the detection when ever i run a scan from avg. So hopefully avg will have the problem fixed soon as seeing it is a problem on there end with todays update.

[Justice11407]

If this has not been posted the below directions supplied by the Malwarebytes consumer support team will work just fine until AVG resolve`s the False positives with an update:

Edited December 25, 2010 by AdvancedSetup
content removed

[cains]

I just got done running a another avg scan just now and did a full scan and nothing poped up this time so avg must have fixedd the problem.

[AdvancedSetup]

@Justice11407

Thank you for your concern and desire to assist others however please do not post email contents on public forums.

The issue is that AVG had a false positive that was removing our files as posted in many posts here on the board now. AVG should have it either fixed now or very soon so please check for AVG updates which should then stop detecting our files.

Thank you again.

[gregftlaud]

As of last nite 12/24 at 10pm the issue was resolved by AVG. I did a manual update of AVG around that time.......removed malwarebytes from my exceptions list.........malwarebytes ran fine. Did a scan on AVG and none of malwarebytes files came up as a trojan.

Greg

[shadowwar]

Greg,

Those execeptions are a good idea to leave anyways. It prevents conflicts and system slow downs between AVG and Mbam.

[gregftlaud]

Well, if it happens again I'll add back the exception. I'm gonna give AVG the benefit of the doubt though here b/c i've been running malwarebytes and avg together for years now and never had this problem. I'd rather not allow an exception to any of my folders on my computer b/c u never know when an actual virus might try to attack that particular folder and take advantage of the exception u made or just attack that folder at random then u are really screwed!