Using the latest webroot V184.108.40.206 on my windows 7 pc. With the latest version scans are now taking about 19 mins. I submitted a support ticket last week. I uploaded logs as requested on thursday and as I had not recieved any response to confirm they had been recieved I contacted weboot. I spoke to a representative this afternoon who said the logs where being analysed and I would recieve a response either today or tomorrow. Just a few momments ago I got a response saying they had not recieved the logs and could i send them again. What is going on? I have replied and sent the logs a second time. Not very good customer service!
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
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:
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.
Webroot Sr. Global Escalation Manager
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 / 220.127.116.11 which came out a short time back.
I've pulled the case, and the logs from the XP machine. Have you ran the utility for the Windows 7 machine?
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 V18.104.22.168 for the time being w/o being auto-updated?
Our Win10 ThinkPad is unaffected .... Thanks for your investigation and help.
Oddly seen the same for my webroot, the scan before this one was 20m 38s an the last scan I had was only 10m 48s and I have seen similar things with it running apparently slow still then picking back up again at the end too.
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 have also been experiencing slow scans probably for the past 7 to 10 days. I'm guessing it has to do with Software Version 22.214.171.124. Daily scans used to take 5 minutes and now are taking 30 minutes. It stays in "Performing Central Analysis" for a long time. It's a Windows XP machine but it's got a Core 2 Quad CPU Q8200 @ 2.33GHz with 2.00GB of RAM. There haven't been any known changes in my PC's configuration. No new programs, no new hardware, etc.
I haven't tried uninstalling/reinstalling but I did uncheck the box under Advanced Settings > Scan Settings > Allow files to be submitted for threat research. This made no difference in scan time.
Hopefully, a resolution to this recent slow scan issue can be resolved in a new Software release.
as I mentioned on the beta thread:
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.
An old, spare Dell Optiplex GX620 running Windows 7 Pro SP1 32-bit, 2 GB RAM, primary boot partition 100 GB (65 GB free)
Version state: PBN: 09001831, DBN: 09001426, HVN: $Revision: #25 $
Initial automatic scan - 6 min, 6 sec
Manual scan - 3 min, 45 sec
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%.
I am on version 126.96.36.199 and do not see the slowness symptom as I had with my Dell Win 7 Pro desktop back in April when testing beta 188.8.131.52.
So maybe issue is isolated to either certain machines and/or Webroot backend versions / servers?
Still showing v184.108.40.206
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 220.127.116.11 too
I observed the other night the first approx 50% completed in 4 minutes. And the scan still took a total of 80 minutes to complete. I've observed most of the scan time is spent in the last part, Central Analysis, approx 80% of total scan time.
Thanks for hanging in there trying to solve the slow scan issue. Per your request using Process Explorer.