Loading Profile...
CS V3 approaching endless deep scans?
Unlike some of those reporting longer VIPRE deep scans, I have CounterSpy V3.2315 which I don't believe is even the most current version of CS. Deep scans were taking about 1 hour until last week when it suddenly increased to over 2 hours. Last night, after updating the Definitions file, it took 3.5 hours. Is this trend going to continue?
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thank you for posting your problem.
We did improve the scan engine recently which can increase the scan time but it seems to be more then it should in your case.
Try this to resolve it, open Counterspy using the icon on your desktop or in the system tray, click on file then settings. In here click on the scan options tab, and uncheck the "scan inside archives" option for quick, deep, and custom scans, then click apply then ok. Now try and run another scan and see if the same thing occurs.
If you have any other questions please let me know.
Thanks,
Peter -
Inappropriate?Peter, I did as you instructed and indeed, the deep scan time, with the same definitions file that took 3.5 hours yesterday only took 43 minutes this time. But does having the same definitions file automatically speed it up the 2nd time around; (it has seemed so in the past)?
Secondly, what am I losing by not scanning inside the archives since I thought the purpose of the deep scan was to look at everything?
Finally, note that I am on CounterSpy V3.1.2315, which is, I think, a few versions back. So was the scan engine improved in later versions or in this one? If those improvements didn't come until later, then I wouldn't have them, would I? And if I don't, then that wouldn't seem to be the "culprit" that suddenly started causing the long deep scans a few days ago would it?
Thanks for your continuing help. -
Inappropriate?Tsquared, Having the same definitions on the machine should not affect the scan time in any way that I am aware of.
Having that option disabled will mean it does not scan inside archives, but we are working on resolving what is causing this to slow down the scans.
The new version 3.1.2710 has improvements to the scan engine, but they also change the definitions and the core scanner thru the definitions, so even if you are on that older version you are still getting the new core scanner updates. We only released these definitions a few days ago, which is why it just started to happen.
If you have any questions please let us know.
Thanks,
Peter
