It takes longer to quick scan since update.

[Daveski17]

I had a strange update today. I am fairly new to MBAM so I am not sure how it upgrades. I routinely update my freeware version daily & today it seemed that I got an upgrade. I think from 1.61 to 1.62? This could be my imagination however . I have noticed that it can take 12 - 13 minutes for a quick scan now instead of the 5 mins or so it normally took. Is this because it has been improved & is more thorough? I only asked in case I should worry about something. I have been a little paranoid ever since I got a trojan once. Anyway, keep up the good work. Death to all malware

[mona7865]

I don't think you have anything to worry about as the quick scan indeed takes a bit longer than usual, after updating to version 1.32:

Malwarebytes' Anti-Malware 1.32

Database version: 1618

Windows 5.1.2600 Service Pack 3

5/01/2009 17:10:18

mbam-log-2009-01-05 (17-10-18).txt

Scan type: Quick Scan

Objects scanned: 65202

Time elapsed: 10 minute(s), 15 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: 0

Usually, a quick scan took about 5

[RubbeR DuckY]

Hi guys,

I'll be sure to make an improvement in the next version. Thanks!

[lordpake]

I had similar experience also (11min Quick scan). However I had some software running in background and uncleaned TEMP folders.

Re-scan with extra stuff closed and after running CCleaner went normally (3+ mins.)

[Daveski17]

Thanks for the replies. The fastest I can seem to get it is around 10 mins. Which is around twice what 1.31 was. I don't mind it being a bit longer in 1.32 if it means it is more efficient. It makes me wonder how long the full scan would be. The last time I ran one of those it was two hours long! That's what I call a thorough scan. Anyway, as long as I have nothing wrong with my computer I am satisfied.

[SoulTrane]

MalwareBytes,

I am also seeing an increase in the scan time - but am noticing something I have not yet seen mentioned (at least in this thread). After updating to the latest version, I tried doing a quick scan and the application got "stuck" files. The first one took a LONG time but finally progressed (after much disk activity). The second time it got "stuck" along with the higher than normal disk activity - I noted the file was around 1k and should not have caused all of this activity. I let it run for a long time (longer than the 1st time it got stuck) and then finally tried closing the application. During this time (before trying to close - while stuck) - the program window title showed "(Not Responding)". The "pause" and "abort" buttons were not responsive (I got an hourglass while inside the window). I tried clicking the big red "X" (upper right corner of window) to close the app but this did not work even after responding "Yes" (or "OK" or "affirmative" or whatever it is) to terminate the process.

I also noticed that while Malwarebytes was non-responsive, there was a second process in task manager (same title "Malwarebytes' Anti-Malware" also shown as "Not Responding"). I tried to "End Task" on this one as well but neither process would terminate.

I am running the program again now and it appears responsive - although with Task Manager open - it often shows "Not Responding" for a brief moment. Sometimes, a second instance of "Malwarebytes' Anti-Malware" appears.

I never noticed this with the previous version. As a side note - with the previous version all scans were done while I was watching (quick scans like this one).

[RubbeR DuckY]

Hey everyone,

We have pinpointed the slowdown to a faulty definition type that we created with version 1.32. The latest database suppresses this definition type until we can get it's speed improved in version 1.33. Please update to the latest database version and you should see a significant speed increase in scanning.

[gerardwil]

Malwarebytes' Anti-Malware 1.32

Database version: 1619

Windows 5.1.2600 Service Pack 3

5-1-2009 21:47:55

mbam-log-2009-01-05 (21-47-55).txt

Scan type: Quick Scan

Objects scanned: 49125

Time elapsed: 2 minute(s), 35 second(s)

This looks pretty normal now to me

Gerard

[DaChew]

Malwarebytes' Anti-Malware 1.32

Database version: 1619

Windows 5.1.2600 Service Pack 3

1/5/2009 4:28:57 PM

mbam-log-2009-01-05 (16-28-57).txt

Scan type: Quick Scan

Objects scanned: 47677

Time elapsed: 2 minute(s), 27 second(s)

Malwarebytes' Anti-Malware 1.32

Database version: 1617

Windows 5.1.2600 Service Pack 3

1/5/2009 4:07:57 PM

mbam-log-2009-01-05 (16-07-57).txt

Scan type: Quick Scan

Objects scanned: 47674

Time elapsed: 3 minute(s), 30 second(s)

I wondered this morning when I updated and scanned why it was slower?

[Maurice Naggar]

Just over 5 minutes for a Quick Scan.

Malwarebytes' Anti-Malware 1.32

Database version: 1619

Windows 5.1.2600 Service Pack 3

2009-01-05 15:06:52

mbam-log-2009-01-05 (15-06-52).txt

Scan type: Quick Scan

Objects scanned: 69178

Time elapsed: 5 minute(s), 13 second(s)

[Daveski17]

Malwarebytes' Anti-Malware 1.32

Database version: 1619

Windows 6.0.6001 Service Pack 1

05/01/2009 22:04:04

mbam-log-2009-01-05 (22-04-04).txt

Scan type: Quick Scan

Objects scanned: 49354

Time elapsed: 6 minute(s), 11 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: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

This seems about right to me now. I am using a Belnea o.book 3 laptop if that is any help to anyone (I believe laptops can be a bit slower at times).

[Daveski17]

I tried again after updating to 1620 & it seems to be really shifting now! Now that's what I call a quick scan!

Malwarebytes' Anti-Malware 1.32

Database version: 1620

Windows 6.0.6001 Service Pack 1

05/01/2009 22:14:59

mbam-log-2009-01-05 (22-14-59).txt

Scan type: Quick Scan

Objects scanned: 49352

Time elapsed: 4 minute(s), 29 second(s)

[SoulTrane]

I'll try the latest definitions. Here's a little more documentation around my slowdown. Notice that this single file is taking at least 15 minutes! Also, the scan time - thus far (it's still scanning) is 41+15 = 56 minutes. As I'm typing this message, I am up to 20610 objects and 1 hour 9 minutes.

Finally completed:

Malwarebytes' Anti-Malware 1.32

Database version: 1619

Windows 5.1.2600 Service Pack 3

1/5/2009 4:22:25 PM

mbam-log-2009-01-05 (16-22-25).txt

Scan type: Quick Scan

Objects scanned: 50490

Time elapsed: 1 hour(s), 9 minute(s), 24 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: 0

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:

(No malicious items detected)

[SoulTrane]

Updated to latest definitions (1620) which cut roughly 30 minutes off the quick scan - but there are still issues. Several files are still getting "stuck".

C:\WINDOWS\Installer\18f06c.msi

C:\WINDOWS\Installer\MSI95C.tmp (same issue as previously documented - around the same time to "process" the file.

C:\WINDOWS\Installer\6b563.msi

Note: this is not a complete list of stuck files as I was not careful to document each file which got stuck. It is interesting that all the stuck files seem to be in the same directory. Also, be aware that the 1st time I noticed this issue was on a laptop. I then replicated this issue on a desktop machine (different hardware) and documented the findings in my previous post. This third run, documented in this message, is also on the desktop machine in order to maintain consistency.

==============

Malwarebytes' Anti-Malware 1.32

Database version: 1620

Windows 5.1.2600 Service Pack 3

1/5/2009 5:09:51 PM

mbam-log-2009-01-05 (17-09-51).txt

Scan type: Quick Scan

Objects scanned: 50655

Time elapsed: 36 minute(s), 47 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: 0

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:

(No malicious items detected)

[SoulTrane]

Updated to latest (even more than last post. This time = 1621) file and watched the entire process. Here is a complete list of "stuck" files for this run. By "stuck" I mean that the program showed "Not Responding" and that this event occured long enough for me to switch to a text editor and write down the file name - then switch back to to Malware and watch until the file finally was processed. Times are approximate as I'm watching the lower-right clock. Total run took the same time (around 40min).

List of "stuck" files this run:

C:\WINDOWS\Installer\19a31.msi (5 min)

C:\WINDOWS\Installer\b6ad2.msi (nearly a minute)

C:\WINDOWS\Installer\e0ccb.msp (nearly a minute)

C:\WINDOWS\Installer\e0d81.msp (~30 seconds)

C:\WINDOWS\Installer\MSI959.tmp (7 min)

C:\WINDOWS\Installer\19d9953.msp (6 min)

C:\WINDOWS\Installer\9f24a.msi (6 min)

=============

Malwarebytes' Anti-Malware 1.32

Database version: 1621

Windows 5.1.2600 Service Pack 3

1/5/2009 6:14:38 PM

mbam-log-2009-01-05 (18-14-38).txt

Scan type: Quick Scan

Objects scanned: 50593

Time elapsed: 36 minute(s), 43 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: 0

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:

(No malicious items detected)