Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by sbwhiteman

  1. Just did, and no more FP. Thanks.
  2. MBAM has just identified SMARTv2.exe as a Trojan.MSIL.SD. I believe this is a false positive. This is a services tweaker published by The Windows Club. A fresh VirusTotal scan is 0/40: http://www.virustotal.com/file-scan/report.html?id=69edaa650fd6d03fbe0e826a2f76a5a1ec1d7e1d680eadeffbbf89162fe5cb34-1303213220 Here's the log: Malwarebytes' Anti-Malware www.malwarebytes.org Database version: 6395 Windows 6.1.7601 Service Pack 1 Internet Explorer 9.0.8112.16421 4/19/2011 7:57:55 AM mbam-log-2011-04-19 (07-57-44).txt Scan type: Quick scan Objects scanned: 178438 Time elapsed: 2 minute(s), 38 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\Steve\Desktop\SMARTv2.exe (Trojan.MSIL.SD) -> No action taken. [0fec8692c33dfb052c3b008fbf410000] Regards. SMARTv2.zip
  3. Thanks, Exile. Looking forward to log files again! Regards.
  4. Hi noknojon, This is an issue with commandline scanning using the free version. So we're not talking about manual scanning and there is no Scan Schedule. On the Settings\General Settings tab, "Automatically save log file after scan completes" is checked. Nevertheless, no log is created after a commandline scan is run with the -quick and -terminate parameters set. Nothing shows up under the Logs tab, and there is no log in the folders you reference. (I've tried this on both a Windows 7 64-bit machine and a Windows XP 32-bit machine.) And adding the -log parameter does not help. By the way, this worked fine in versions through 1.44. The problem began in 1.45 and has been acknowledged above, "to be fixed in 1.46." Unfortunately it remains. Can we get confirmation from the developers that it is being worked on? Thanks.
  5. I'm interested in this log issue as well. As far as I can tell, version 1.46 does not correct it. Running a commandline scan (mbam.exe /scan -quick -terminate) does not produce a log file, whether the -log parameter is set or not. (I have "Automatically save log file after scan completes" checked in the GUI settings.) Is this being worked on?
  6. Thanks RD for the quick reply. Just so I'm clear, using the commandline free version (and the Windows Task Scheduler) one used to be able to automatically update and have the program terminate (mbam /runupdate) and then run a quick scan (mbam /quickscanterminate), all without user intervention. Now, after mbam /update, the user must intervene to either close the program or run the scan. If after updating, a scan is run by the Task Scheduler, you receive the error message that "Malwarebytes is already running." So is there now no way to automatically update then run a quick scan, without user intervention, in the free version? Thanks.
  7. Using the free commandline version, before version 1.45 it was possible to run an update and have it terminate without user intervention after the update (mbam /runupdate). Is it no longer possible to do this? Thank you.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.