Jump to content

mbmo

Members
  • Content Count

    36
  • Joined

  • Last visited

About mbmo

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm referring to manual full system scans which on my computer take around a half hour (or less). I have the free version of Malwarebytes.
  2. When Malwarebytes scans it uses 100% of the CPU. Could that cause damage if done too often (such as on a weekly or monthly basis)?
  3. Sorry, wasn't able to get to it yet. If I post the logs next week, would you be able to look at it?
  4. Sure. But first just take a look at this two logs, the first is when "Custom scan" was selected {with C and E drives clicked), while the second was the regular "full" scan. Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 6/28/17 Scan Time: 9:52 PM Log File: Administrator: No -Software Information- Version: 3.1.2.1733 Components Version: 1.0.141 Update Package Version: 1.0.2251 License: Trial -System Information- OS: Windows 10 CPU: x64 File System: NTFS User: PC\Main -Scan Summary- Scan Type: Custom Scan Result: Completed Objects Scanned: 402967 Threats Detected: 0 (No malicious items detected) Threats Quarantined: 0 (No malicious items detected) Time Elapsed: 46 min, 31 sec -Scan Options- Memory: Enabled Startup: Enabled Filesystem: Enabled Archives: Enabled Rootkits: Enabled Heuristics: Enabled PUP: Enabled PUM: Enabled -Scan Details- Process: 0 (No malicious items detected) Module: 0 (No malicious items detected) Registry Key: 0 (No malicious items detected) Registry Value: 0 (No malicious items detected) Registry Data: 0 (No malicious items detected) Data Stream: 0 (No malicious items detected) Folder: 0 (No malicious items detected) File: 0 (No malicious items detected) Physical Sector: 0 (No malicious items detected) (end) ------------------------------------------------------ Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 6/29/17 Scan Time: 7:25 PM Log File: Administrator: No -Software Information- Version: 3.1.2.1733 Components Version: 1.0.141 Update Package Version: 1.0.2258 License: Free -System Information- OS: Windows 10 CPU: x64 File System: NTFS User: PC\Main -Scan Summary- Scan Type: Threat Scan Result: Completed Objects Scanned: 397145 Threats Detected: 0 (No malicious items detected) Threats Quarantined: 0 (No malicious items detected) Time Elapsed: 2 min, 11 sec -Scan Options- Memory: Enabled Startup: Enabled Filesystem: Enabled Archives: Enabled Rootkits: Enabled Heuristics: Enabled PUP: Enabled PUM: Enabled -Scan Details- Process: 0 (No malicious items detected) Module: 0 (No malicious items detected) Registry Key: 0 (No malicious items detected) Registry Value: 0 (No malicious items detected) Registry Data: 0 (No malicious items detected) Data Stream: 0 (No malicious items detected) Folder: 0 (No malicious items detected) File: 0 (No malicious items detected) Physical Sector: 0 (No malicious items detected) (end)
  5. Just did a custom scan on a SD card but included the C drive to enable rootkit scanning as well. This scan took 45 minutes. Apparently my suspicion that the first "regular" scan didn't scan anything was correct.
  6. Just installed Malwarebytes on a new Windows 10 laptop. 1) The first scan took 1 minute, a subsequent scan (with rootkit detection turned on) took 2 and a half minutes. I like fast scanning, but is that fast even possible to scan a drive with 40GB on it (of Windows files and Asus bloat)? 2) Why did it use 100% of the CPU (of a 7th i5)?
  7. I know that. I didn't direct that question at you personally and no offense was intended . I just meant to ask if you were aware why Malwarebytes is having trouble since the release of version 3. Too true. Nonetheless, MBAM 2 was relatively stable and reliable, while MB3 has been one big mess for many.
  8. Do you know why for months following the release of version 3 there's still one bug after another, and one issue following the next? (Earlier versions never had these problems.) This program used to be reliable.
  9. Since MB3 was released I re-installed the latest version (or mini version 3.x) several times, each time another issue comes up. Am I going to have to keep on re-installing the latest mini version each time for it to work, otherwise one thing or another will go wrong? This kind of thing never happened with MBAM 2, when I had it older (mini) versions worked fine. When I buy a new computer with a more recent OS can I expect similar issues to keep on coming up with MB3 as well?
  10. As it relates to FRST, I assume these are false positives? Thanks.
  11. After trying to do a full scan twice, this was the result after two plus minutes and three plus minutes respectively.
×
×
  • 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.