Adwcleaner 8.2 nearly doubles the scanning time

[Beenthere]

Hi

Just updated to 8.2

Scanning time is 37 seconds.

My last scans with previous versions are as follows

# Duration: 00:00:15
# Duration: 00:00:20
# Duration: 00:00:14
# Duration: 00:00:20
# Duration: 00:00:21
# Duration: 00:00:16
# Duration: 00:00:14

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the AdwCleaner Help forum.
In order to help us assist you to resolve your issue, please post or attach your latest AdwCleaner log files with your post. https://support.malwarebytes.com/hc/en-us/articles/360039021593

Someone will reply shortly, but in the meantime here are a few resources which may help resolve your issue:

• Malwarebytes AdwCleaner guide
• A malicious element isn't being detected? Submit the sample here!
• Need help with another Malwarebytes product or malware removal?
  • Click here for home support
  • Click here for business support
  • Click here for malware removal help

Thanks in advance for your patience.

-The Malwarebytes Forum Team

 

 

 

 

[Beenthere]

Nevermind, it was because it was a first run, now it's fine.

[exile360]

In case you're curious why this happens, it's due to disk caching.  The same thing happens with Malwarebytes free/Premium where subsequent scans during the same Windows session occur much more quickly than the first scan during that Windows session because most of the file/data reads from disk are cached, speeding things up tremendously.

If you restart your system and scan again, the scan time will likely be around the same as the first slower scan you ran, and scans afterwards during the same Windows session will be shorter, just like the other scans you ran.

Edited March 24, 2021 by exile360

[jboursier]

Hello,

This is still abnormal, but I suspect it's related to the network and it has something to do with the definition updates check at the beginning of the scan..

On 3/24/2021 at 10:38 AM, Beenthere said:

Nevermind, it was because it was a first run, now it's fine.

I think that it took a long time to download the latest definitions and that subsequents scans didn't have to do it since they were already up-to-date. In case it happens again in the future, could you try enforcing using the bundled definitions (see there ) and enabling a debug log?

Thank you,