Jump to content

Funk

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Funk

  1. MBAMService.exe still popping up regularly on ProcMon. AFAICS, surely excluding drives x/y/z from all detections should mean that MWB should simply treat them as if they don't exist; if it's not been asked to monitor them, surely it doesn't need to query/address the sleeping disk(s) every few hours...
  2. Configured per your post; will see what it does overnight...
  3. Hi AdvancedSetup, Update: I think we can rule out scheduled scan being the issue - it's not due to run until 2am, however MBAMService.exe has just woken all the sleeping drives again exactly 2 hours since the last time (to the minute!). I'll run the support tools tomorrow if I have time but tbh I suspect this is just MWB 'doing its thing' and regularly checking - the issue is I don't need (or want) it to check sleeping drives. I'll do some more playing with settings and see what happens. If it keeps doing it I'll just bin it off.
  4. I'm pretty sure disabling the scheduler will stop the service trying to access those drives but it'd mean I'd have to regularly run scans myself (might as well revert to the free edition in that case..). I'm not quite ready to pony up for that sort of capacity of SSD just for long-term archiving...
  5. I can check, however I do want scheduled scans to run on the other drives as normal...
  6. I have an external JBOD with archive drives in which are set to spin down when not in use. 'Something' kept causing them to spin up randomly and for no reason (ie. no access was requested of the drive). I ran ProcMon and filtered the drives to see what process was causing them to wake - it turns out to be Mbamservice.exe. I've set each drive to be excluded from all detections, but Mbamservice.exe continues to wake the drives from sleep (Explorer.exe then has to do some volume queries once the drives are awake but it's Mbamservice that triggers it). Why is MWB ignoring the exclusion command and how can I ensure it leaves these external drives alone...? Cheers.
  7. nosirrah, have taken the new update and both the Creative Sound Volume Panel and Comodo Firewall issues are now fixed. Thanks for your fantastically fast response with this, top work!
  8. I too received this result after an update and new scan this evening on both my PC and laptop. Mine also flagged my Creative Volume Panel on the PC as being infected with the same thing. No other anti-malware and anti-virus reports back, so presume this is a MBAM issue...? Here's my scan result from the laptop: Malwarebytes' Anti-Malware 1.29 Database version: 1292 Windows 5.1.2600 Service Pack 3 20/10/2008 03:00:46 mbam-log-2008-10-20 (03-00-41).txt Scan type: Quick Scan Objects scanned: 52091 Time elapsed: 8 minute(s), 14 second(s) Memory Processes Infected: 0 Memory Modules Infected: 0 Registry Keys Infected: 0 Registry Values Infected: 1 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: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\comodo firewall pro (Trojan.Lop.H) -> No action taken. Registry Data Items Infected: (No malicious items detected) Folders Infected: (No malicious items detected) Files Infected: C:\Program Files\COMODO\Firewall\cfp.exe (Trojan.Lop.H) -> No action taken. First time around I allowed MBAM to delete the .exe files and have since done CFP re-installs on both machines. The results are still the same. Can anyone from MBAM confirm that this is an issue your end and not something to worry about? Many thanks.
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.