Jump to content

Malwarebytes FREE scan ends too quickly

Recommended Posts


I have the  problem(?) with Malwarebytes FREE after the update program to latest version.

Usually automatic ''Threat scan''  on my PC scans in 40 min-1 hour, and now only 6-10 minutes. But the number of scanned files is the same.

Attached Files - Log Scans

''Scan Log'' from scan before updating Malwarebytes -  Scan 2014.10.21.txt

Thread Scan Time -1h.17 min

''Scan Log'' from current scan  -   Scan 30.10.2014.txt

Thread  Time -10 min

-Scan Logs are from in Polish languages

Scan 2014.10.21.txt

Scan 30.10.2014.txt

Link to post
Share on other sites



It's a bit hard to say for sure without a bit more information.

The scan time for one from 10.30.2014 looks about what one would expect - ~10 min and ~400K files.


Please read the following and post back attached to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)

The staff and experts will review the scan logs already posted AND the diagnostic logs.

Then they will advise you further.



Link to post
Share on other sites



There are many factors that determine scan times. It's impossible to predict exactly how long it will take to perform any particular scan on any particular computer. :(
However, this entry in your log is abnormal:

User Account type:                 Administrator
OS:                                Windows 7 Service Pack 1 Service Pack 1 64 bit Operating System
Current Version and Build:         6.1.7601.0
Malwarebytes Anti-Malware:
Installed On:                      2014/10/24
Malware Database:                  0000.00.00.00
Rootkit Database:                  0000.00.00.00

So, until a staff member has a chance to review your logs, you might want to please try a clean reinstall of the program.
To do so, please carefully follow the steps here: MBAM Clean Removal Process 2x
Then you might want to fully disable Windows Defender from the Control Panel (as you already have ESET NOD32 as an anti-virus (AV)).
Then, you might want to set mutual exclusions between MBAM and ESET (the instructions are at the bottom of this reply).
If you are still experiencing problems after all that, please create a NEW set of fresh diagnostic logs.
To do so, please carefully follow the steps here: Diagnostic Logs
Before running FRST again, please place a check-mark in the option for "Addition.txt".
Then, please post back with all 3 new logs (and a new MBAM scan log).

Please exclude the following files from your Antivirus Software for your version of Windows:

For 32 bit versions of Windows XP, Windows Vista, Windows 7 & Windows 8:

  • C:\Program Files\Malwarebytes Anti-Malware\mbam.exe
  • C:\Program Files\Malwarebytes Anti-Malware\mbamdor.exe
  • C:\Program Files\Malwarebytes Anti-Malware\mbampt.exe
  • C:\Program Files\Malwarebytes Anti-Malware\mbamservice.exe
  • C:\Program Files\Malwarebytes Anti-Malware\mbamscheduler.exe

For 64 bit versions of Windows Vista or Windows 7 & 8:

  • C:\Program Files (x86)\Malwarebytes Anti-Malware\mbam.exe
  • C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamdor.exe
  • C:\Program Files (x86)\Malwarebytes Anti-Malware\mbampt.exe
  • C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamservice.exe
  • C:\Program Files (x86)\Malwarebytes Anti-Malware \mbamscheduler.exe

Note: If you are using a software firewall besides the built in Windows Firewall, you'll need to exclude MBAM.EXE and MBAMSERVICE.EXE from it as well.

Note: Once that's done, please make sure that if either of those programs has any sort of web filter, that you add the following as a trusted site:

Link to post
Share on other sites

MBAM has been re-installed (clean install).  Exclude files added in Eeset NOD 32.  The situation has not changed.




cyt''However, this entry in your log is abnormal:''


Ok , but in scan log we have information:



Baza danych malware: v2014.11.02.03
Baza danych rootkitów: v2014.11.01.02'''



All logs added









Scan Log 2.11.2014.txt

Link to post
Share on other sites

Thanks for the new logs.


That entry in the mbam-check log may be a logging bug. :unsure:
We'll need to wait for the staff to review the new logs,
but the MBAM scan log looks OK to me.
(I don't speak Polish, but I assume that was a Threat scan log?)
There are so many different variables that determine scan times, it's impossible to predict.
Some variables tend to speed up the scan, and others tend to make it longer.

Some factors can be dealt with, and others not as easily.

These include:
Size of disk
Disk type
Disk speed
Disk caching
CPU speed
Controller type and speed
Operating System used
Amount of files (including temp files!)
Amount of folders
Amount of archived files such as zip, rar, sfx, etc. (if this is enabled)
Rootkit scan or not (if this is enabled)
PUM/PUP scans
Other security programs running at the same time that may potentially be monitoring all file accesses by any other process, including subtle conflicts or clashes with the user's antivirus
Drive integrity - if a drive is failing it can take a long time to ignore and bypass sectors on a disk or simply fail period and hang the scan.
Other ongoing disk I/O processes
Malware infection
Size of the MBAM database

(Sometimes slowdowns are not due to conflicts between MBAM and the AV, per se, but rather to older hardware, insufficient RAM, cluttered disks, excessively tight security settings, etc.)


Thanks for your patience,

Link to post
Share on other sites

Maybe this is no problem ?. (Scan time). Maybe something in the new version has improved and now MBAM scan is faster. In the previous version of MBAM were long downtime between the scanned files, but now now there is no such downtime.







We'll need to wait for the staff to review the new logs, but they look OK to me.
(I don't speak Polish, but I assume that was a Threat scan log?)''



The same log (but in English) added ;)

Scan Log 2.11.2014 EN.txt

Link to post
Share on other sites

  • Staff

we did make some changes on the database recently and fixed heuristic bugs in certain situations. you were probably affected by this and thats why the scan times are quicker now. 2.03 resolved quite a few scan times bugs also. the long pause in heuristic part of scan was one of these that were corrected.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
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.