Loading Profile...
What's with the Deep Scan Problems?
My Vipre stopped two nights ago and turned red when it was supposed to be scanning. Last night, it started a deep scan and this process continued for 4 hours (it usually takes an hour and 30 minutes). The four hour scan never did stop nor get to the cookies, even though it said 100% complete. What gives with these snafus?
I’m anxious and frustrated
7
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Try turning off "Scan inside of archives" in the Scan Settings screen.
If that helps, let us know. This is something we are researching. -
Inappropriate?Thank you for your post!
It sounds like there is something conflicting with Vipre on the system.
Please use the directions below to submit logs to us here at support so that we can better assist.
Please attach these in a reply email to us with a brief description of the problem.
First open VIPRE by double clicking on the VIPRE icon in the System tray (Down by the time on your computer)
Click on the word “Help” then “About”
Then click on the button labeled “Support tools” then “Run Diagnostics”
Make sure that all the boxes are checked and click “ok”
Once this starts, it will take a couple minutes while the utility gathers information. It will create a file on your desktop called “Sunbelt VIPRE Antivirus + Antispyware Diagnostics.rar”
After that file appears, run the following utility.
http://www.sunbelt-software.com/support/VC/VCInfo.exe
You will be asked for your support ticket number. You can locate this in the Subject line of this email.
Attach this log to a reply email.
I’m confident
1 Comment
Add a comment
This answers the question
-
I have the same problem. Shield turns red, scans don't run. This never happened prior to the update you relased a week or two ago. Something is wrong on your end sunbelt. -
Inappropriate?Alan, Thank you for posting your problem. It sounds like there is something conflicting with Vipre on the system as well.
We would also like you to send us some log information in order to help us resolve this.
Please use the directions below to submit logs to us here at support so that we can better assist.
First open VIPRE by double clicking on the VIPRE icon in the System tray (Down by the time on your computer)
Click on the word “Help” then “About”
Then click on the button labeled “Support tools” then “Run Diagnostics”
Make sure that all the boxes are checked and click “ok”
Once this starts, it will take a couple minutes while the utility gathers information. It will create a file on your desktop called “Sunbelt VIPRE Antivirus + Antispyware Diagnostics.rar”
After that file appears, run the following utility.
http://www.sunbelt-software.com/suppo...
You will be asked for a ticket number, which for you us 281152
Please attach this files to an email to be send to Support@sunbeltsoftware.com, Please put the ticket number 281152 in the subject line.
If you have any questions please let me know.
Also, Jim Here is your ticket number that you can use when the log utility asks for one, as well as for what you can put in the subject line of your email if you have not already sent it in, 281158
Thanks,
Peter
1 person says
this answers the question
-
Inappropriate?Over the weekend, the scans on Saturday and Sunday did take place. However, they lasted about 4 hours and 45 minutes each. In the past, they have lasted about an hour and a half. Something is still screwy. I did perform your analysis regimen and send it in to your company.4 Comments Add a comment
This answers the question
-
Jim, some users are experiencing longer scan times, Because of improved scan engine that detects more threats. We are working on improving this, as it should not increase by that much. Try this to improve your scan time for now. Open Vipre, click on file then settings, in here click on scan options, then uncheck the option to check in archives. Then try and run another scan and see if it improves the scan time.
Let me know if you continue to have problems or have any other question.
Thanks,
Peter -
I am going to try Peter's suggestions as well. My scans ran as high as 5 hours over the weekend, but "only" 4 hours 15 min. today. They used to be just slightly over or under 1 hour. I would love to get back to that, as I have it run while I'm out walking in the morning and would like it finished before I leave for work (when I put my laptop to sleep). Thanks to Peter and company for your efforts.
-
My scan this morning (after unchecking "check in archives") only ran for 61 minutes. That definitely did the trick, although the CPU usage is still high (35-50%). I'm away from the computer during the scan, so that doesn't bother me as it did when the scan ran for close to 5 hours.
-
Peggy, We are still investigating what is causing the much longer scan times when that option is enabled. If you would like to send us some log information from your computer to help us determine what is causing this please email support@sunbeltsoftware.com and put your ticket number 281634 in the subject line and we can send you the steps to get the information we need.
If you have any questions please let us know.
Thanks,
Peter -
Inappropriate?When I do a deep scan, the system says the scan is complete, 100%, and the time remaining shows zero but the clock is still running and the scan continues. I stopped the scan at 87 minutes when it looked like it was doing
Windows files, which is what it usually starts with, I think. It seems strange that by that time it had found no file problems, not even any Cookies. -
Inappropriate?William,
Because the scan estimates how long it is going to take based on previous scans that have finished, since it is not finishing it cant show you how much time is left. Try and let the scan continue to run, and let me know how long it actually takes to finish, and we can decide what to do once it finishes and we see how long it takes.
If you have any other questions please let me know,
Thanks,
Peter -
Inappropriate?I unclicked the archive reference and ran a deep scan. It took only 51 minutes.....found one cookie which got removed. The statistics as it ran seemed normal.
Thanks for the suggestion. -
Inappropriate?WIlliam,
Good to hear it brought the scan time back down, we are still working on resolving what is causing it on our end.
If you have any questions please let us know.
Thanks,
Peter -
Inappropriate?I tried the uncheck of the archive files and that did bring down the scan time to normal.
I’m feeling a little better.
-
Inappropriate?Jim,
Good to hear it brought the scan time back down, we are still working on resolving what is causing it on our end.
If you have any questions please let us know.
Thanks,
Peter -
Inappropriate?I am another satisfied user of the uncheck the "Scan inside of archives" button suggestion. Deep scan times went from ca. 980 minutes to ca. 82 minutes.
-
Inappropriate?I am another satisfied user of the uncheck the "Scan inside of archives" button suggestion. Deep scan times went from ca. 980 minutes to ca. 82 minutes.
-
Inappropriate?The scan time issue should be fixed now, even with "Scan Archives" enabled. It was fixed in a definition update in the past day or so.
-
Inappropriate?My deep scan time seems to be back to normal with everything enabled. Good job!
