Malwarebytes false postive - avast won't start.

Has anyone experienced the same problem? see attached log.

try a quick scan with mbam and post back here.

I have reported in mbam forum

regards
nmb

edit : and also found that if I remove those infections, avast won’t start(two people have mentioned in the mbam forum).

Yes, actskin4.ocx belongs to avast…

ylap do you use mbam?.. can you do a scan and post back here?.

Looks like a False Positive as it detects 19 items that I took no action on on both XP Pro and Windows 7.

Results are the same. MB’s false positive.

Thanks for the confirmation guys. hope mbam guys will come up with a solution. until then we can’t advice mbam to someone who needs a virus infection check up using the same.

I have the same, 18 registry infections and 1 file (actskin4.ocx) infected. I’m sure these are false positives as this isn’t the first time mamba has made these errors.

Dear Forum,

I have the same results with MBAM. No action has been taken and I will wait for MBAM to respond.

There have not been many false positives with MBAM. This appears to be one of the few exceptions.

Last year I used A-squared and that seemed to return a lot more false positives.

Best regards,

Avastfan1

update : It is not yet fixed (after update 2882.)

update : It is not yet fixed (after update 2883).

Well me I don’t have MBAM set on auto update, being a dial-up user and normally only update it once a week before I do an on-demand scan, which was last Friday. Having done a scan no detections, but my database version is 2860.

So to me there seems a distinct advantage in only updating before an on-demand scan and hopefully give time for any such corrections to be made.

I use mbam on demand. I scan once every three days. I just update before scan as you do. My luck that today I found those fp’s. :frowning:

The strange thing is that first MBAM suggested it was fixed in 2882 and then 2883, yet it still isn’t. MABM have in the past been very quick to correct any FP, this one seems more complex as it isn’t just a file but the associated registry entries being classed as Trojan.agent.

So hopefully it won’t be long.

Hope so.

searching for a solution ?

If anyone is has experienced the same thing and you removed the false positive infections, you can do this:

go to mbam quarantine and restore the files detected. careful, don’t delete the previously detected malwares.

Try updating MBAM as the latest database 2886 corrects the FPs

Its fixed in Database version: 2887 for me.

Available in database 2890-got it today. everything is fixed.

Great :slight_smile:

HI :slight_smile:

I did scan yesterday and everything was fine.

Have a nice day. :slight_smile: