Yes, it could be a glitch, but I don't know until I see that log.
No worries, just post the log whenever you can
Yeah, the new version did not detect the Rogue.Fake.MSE. The Don't.Steal.Our.Software entry did come up, but as I understand it, that's something MBAM did to establish the fact that their database was being stolen. Isn't that correct? Here's the log. Looks clean except for the Don't Steal thing. Thanks so much!
Malwarebytes' Anti-Malware 1.46
www.malwarebytes.org
Database version: 4180
Windows 6.0.6002 Service Pack 2
Internet Explorer 7.0.6002.18005
6/8/2010 2:51:51 PM
mbam-log-2010-06-08 (14-51-51).txt
Scan type: Full scan (C:\|)
Objects scanned: 280043
Time elapsed: 45 minute(s), 46 second(s)
Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 1
Memory Processes Infected:
(No malicious items detected)
Memory Modules Infected:
(No malicious items detected)
Registry Keys Infected:
(No malicious items detected)
Registry Values Infected:
(No malicious items detected)
Registry Data Items Infected:
(No malicious items detected)
Folders Infected:
(No malicious items detected)
Files Infected:
C:\Users\Fred\Documents\Fred's Files\Programs_Patches_Setup\mbam-setup-1.46.exe (Dont.Steal.Our.Software) -> Quarantined and deleted successfully.
