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.
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.
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.