Get your own customer support community
 

VIPRE will not scan cookies

New VIPRE installation on WinXP SP3 PC will not scan cookies using Quick Scan or Deep Scan (cookie scan options are checked). I know cookie scanning is not working properly because there are numerous cookies in the IE default location, but VIPRE reports "0" cookies scanned at completion. However, a Custom Scan does properly scan the cookies and reports the correct number scanned, as well as detecting some that need removing.

I installed VIPRE on a second, similar PC, with the same operating system, and it does everything it is susposed to do, so I don't think my problem is operator error.

It is obvious that Quick and Deep are looking in the wrong location for the cookies. While trying to solve this problem, I discovered they are looking for the cookies in a C:\Windows\temp\cookies folder, rather than the IE default location where they are actually stored. I verified this is where Quick and Deep are looking for cookies by copying a sample set of cookies to that location and running scans. Both Quick and Deep reported that they had scanned the number of cookies that I had copied to C:\Windows\temp\cookies. A Custom Scan ignored the cookies in that location, and instead reported the correct number of cookies scanned that were in the IE default location.

In addition to Quick and Deep scans not working properly, the History Cleaner Tool does not delete the IE cookies, apparently because it is also looking in the wrong place for them.

I searched the registry for possible entries that might be confusing VIPRE, but did not find any suspicious entries.

I contacted Sunbelt tech support regarding this probem, but the only suggestiion I was given was to remove and reinstall the software, which did not do any good.

I would appreciate any suggestions on fixing this issue, if the problem is with my PC setup. In the meantime, maybe VIPRE programmers should check the code for differences between Custom and Quick/Deep scans that allow Custom scans to work properly when the other scan modes will not. A nice addition to VIPRE would be to allow Custom scans to be scheduled, which would provide an acceptable work-around for this problem.
 
sad I’m frustrated
Inappropriate?
1 person has this problem

User_default_medium