Central analysis taking way too long

  • 5 November 2018
  • 4 replies

Userlevel 1
I see others have had this problem before me so I've tried all possibilities set forth here such as installing & reinstalling and the like. Performing central analysis is just taking way too long approx 2 hours and change for the total deep scan. Nothing had changed on my system in the last few weeks. No major installs or uninstalls. 


Any ideas or solutions would be appreciated before I send in a ticket.

Best answer by TripleHelix 13 December 2018, 21:53

View original

4 replies

Sorry, @, to see you have had no reply to this issue from a Forum Community member. Also did you get a satisfactory response from Webroot Support?
Actually, I encountered this problem about the same time as you, and as I'd never seen this before, I assumed it was a bug that would be sorted out in the next few days. I came back to the issue today and decided to do a test and, lo and behold, I still have the problem.
Here is the data:
  1. My Windows 7 machine: this is the device I saw this problem on last month, and so I began today by testing with this machine. Scan Time: 1h2m of which 45 minutes was "Performing Central Analysis". A curiosity was that the number count of Files Scanned increased considerably during this last phase.
  2. My Windows XP machine: Scan Time: 1h9m. I was unable to count the time it was "Performing Central Analysis" but it was certainly long, and possibly longer than with my Windows 7 device. Also the Webroot GUI curiously recorded a Scan Time of 7m5s, no correlation to the observed scan time. Also, in WRLog and in the Scan Log, the Scan Start Time is shown but not Scan Finish Time. (This is not so in my Windows 7 Webroot logs where the scan start and scan finish times show correctly)
  3. My Windows 10 machine: the scan executed normally with a scan time of 2m36s.
It is interesting that this behaviour manifests itself on my 7 and my XP but not on my 10. Could this possibly be a bug associated with Windows 7 and earlier? Or maybe 8 and earlier???
Can anyone who has a machine operating Windows 7 or earlier test to see if they have similar behaviour? And, if possible, post here to say if they are encountering similar behaviour and equally if they are not encountering this behaviour? Also, what operating system are or were you using, @?
Can you help, @?
Userlevel 7
Badge +36
I'm honestly not sure. As you mentioned, support is the best path for getting this resolved.
Userlevel 7
Badge +63
I don't see any issues on my Windows 10 x64 build 1809 so it's best to contact support.

Beta release v9.0.24.49 (released yesterday) appears, on my side at least, to have resolved the problem of long scan times that some of us were encountering and that seemed to begin with the consumer version (released Nov 27th and still current). Hopefully, users encountering this problem of excessively long scan times will see it resolved when this beta version is released to consumer version.