Best phone camera 2017
Running XP (SP2) with spyware blaster/avg 8.5.449/malwarebytes/ ad aware. Been running ok for a couple of months & upgrade regularly. Did another upgrade today & it looks like AVG is reporting a trojan in the malwarebytes folder. Tried to run malwarebytes after upgrade and got an error "Run time error'48' - File not found :mbamcore". Anyone else had any trouble?
Thx ashdav, I was confident I had kept upto date, but not the case. It was a conflict with AVG, as I uninstalled it & malwarebytes ran fine. Then installed the new version of AVG and both run fine now.
Maybe this was the problem.
An AVG database update this morning (December 24, 2010) incorrectly detects two DLL files (mbamcore.dll and mbamnet.dll) in Malwarebytes' Anti-Malware 1.50.1 as trojans. This is a false positive. AVG has acknowledged this false positive, and has promised us that it will be corrected within an hour.
We are sorry for our users who are affected by this. It has happened before in the past, and AVG had assured us it would not happen again.
We are also aware that this incident has negatively affected our rating on CNET Download.com and other portals. We would appreciate if a few of our users would set the record straight.
If you use AVG antivirus and get these detections, ignore them. Update your AVG definitions; hopefully it will be fixed soon.
If you have already quarantined the Malwarebytes' Anti-Malware files using AVG (sent them to the Virus Vault), you can fix this as follows:
1. Set Exclusions within AVG
Exclude the Malwarebytes' Anti-Malware program files directory (usually C:\Program Files\Malwarebytes' Anti-Malware, or C:\Program Files (x86)\Malwarebytes' Anti-Malware on x64 operating systems) from AVG.
Precise instructions for how to do this for several versions of AVG may be found here.
2. Restore the Malwarebytes DLLs from the AVG Virus Vault
Step 1: Start AVG
Step 2: Click History -> Virus Vault
Step 3: Select mbamnet.dll and click Restore. Then do the same for mbamcore.dll.
Malwarebytes' Anti-Malware should now function as normal.
This thread is now locked and can not be replied to.