Slow scans

I'm looking at the logs now, and while I can see three scans, historically. All over 20 minutes, the first scan included three detection's as well. I'm not seeing a quarantine DB, which suggests that you manually overrode these files. This can have an impact on interrogations of files lengthening the scan since the system thinks it's still potentially infected. If these files were FP's please let us know, and we can correct the determinations.
System events provide the following messages as well:
Disk 7 Error None Stephen-PC The device \Device\Harddisk0\DR0 has a bad block.
further performance hits are likely due to this message:
Microsoft-Windows-Kernel-Processor-Power 6 - Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.

This suggests that the system isn't operating at peak performance. More information on this message can be found here:
https://social.technet.microsoft.com/wiki/contents/articles/3565.event-id-6-microsoft-windows-kernel-processor-power.aspx

While it's possible that any of these issues could cause longer than average scans, the fact that we see all three combined go some ways to explain the issues here. I'd consider looking into the disk and CPU settings, as well as the detection.

Thanks,
Lucas Moore
Webroot Sr. Global Escalation Manager

So do we have a fix for this EXACT same issue here... Out of the blue... Worked fine for years!
I am thinking from how they are saying, it is an on-going issue they are working on fixing and has to do with the last update to Webroot - Version / 9.0.26.61 which came out a short time back.

Hi @TechToc ,

Unfortunately Lucas, my wife currently has the Win7 ThinkPad and will be staying with her family out of town for another week. I returned home early after the 4th due to work commitments.

I'll try to ask her to pull logs but she may be reluctant due to being "less" than non-tech savvy (if such a level is even possible). As a non-smartphone person in her early-sixties, she always worries about messing something up, especially when she's away from home w/o me there physically to help.

I will pull logs from the Win7 ThinkPad upon her return in the worst case senario.

BTW, Is there any way to go back to V9.0.24.49 for the time being w/o being auto-updated?

Our Win10 ThinkPad is unaffected .... Thanks for your investigation and help.

@TechToc .... Thanks! Support reply just sent. RRod

My computer has been running slow and tonight froze and was almost crippled. I checked task manager and my cpu was running at 100%. I have shutdown webroot and my pc is back to normal. There is a problem with the latest version with slow scan speeds and excessive cpu usage. Feel fobbed off as support say there is no problem with the latest update.

For some unknown reason, today's scan dropped from 30m to 11m 58s. Still slows way down once it reaches 41% but at 70% it speeds back up. At 11m 53s it entered Performing Central Analysis for only 5s completing the scan at 11m 58s. Checked the Software Version thinking I might have been pushed a new version but it's still reporting 9.0.26.61. Still reports Files Scanned >56,000 files.

creakndale
Another update on my webroot, my webroot now scans around 5 / 6 minutes now total though still seems to eat up processor space, being that it runs still nearly 99% useage when running.

I've noticed this symptom in April when doing testing on Beta v9.0.24.49
as I mentioned on the beta thread:
https://community.webroot.com/wsa-for-home-beta-73/updated-file-for-wsa-pc-consumer-beta-systems-337909

During that time, there was mention of some beta users being on version/revision 25 vs 32. I was able to toggle between the 2 versions and definitely saw differences in scan time especially in the Central Analysis stage.
I don't have access to that machine right now to recreate with current production version but definitely isolated to that Win 7 desktop at that time and I was not able to recreate on my other laptop with Win 10.


Here's a cut and paste of my observations from one of my post on that thread.
===============================

I've decided to re-test the Revision 25 vs Revision 32 scan time comparison using a better way - by reinstalling the beta before each test. Results mimick what I have seen yesterday - Revision 32 scans significantly slower on my environment.

My computer:
--------------------
An old, spare Dell Optiplex GX620 running Windows 7 Pro SP1 32-bit, 2 GB RAM, primary boot partition 100 GB (65 GB free)
.
.
.

Results:
-----------
"Revision 25"
Version state: PBN: 09001831, DBN: 09001426, HVN: $Revision: #25 $
Initial automatic scan - 6 min, 6 sec
Manual scan - 3 min, 45 sec

"Revision 32"
Version state: PBN: 09001831, DBN: 09001426, HVN: $Revision: #32 $
Initial automatic scan - 30 min, 55 sec
Manual scan - 28 min, 18 sec. (Stays in "Performing central analysis" for last 5 min of scan)


Revision 32 scanning observations:
------------------------------------
Initially the scan runs quickly, churning through %, for the first few minutes. Once it gets to 41% scanning, it gets "slower" , seems to be taking more time scanning .exe & .dll files than before on Rev 25.
No apparent slowdown in computer response time as far as moving mouse around.
CPU usage around 52 % average. Physical memory used 32%.


--Patrick

Another update on my webroot, my webroot now scans around 5 / 6 minutes now total though still seems to eat up processor space, being that it runs still nearly 99% useage when running.Ran a scan moments ago and no change for me. Time elapsed 11m 51s. Average CPU usage 25% to 29%.

Still showing v9.0.26.61
creakndale

Nod, Mine apparently fluctuates now.

It can be anything from 5 to 6 minutes to up to 11 to 15 minutes, strange... it seems marginally better.

still also v 9.0.26.61 too

TechToc,
Thanks for hanging in there trying to solve the slow scan issue. Per your request using Process Explorer.
creakndale