Loading Profile...
Scheduled Scan Freezes Comp
Hey guys, I just got Vipre Antivirus + Antispyware and its been great so far except for one thing. Whenever a scheduled scan starts up my computer completely freezes!
Anyone got a fix?
Anyone got a fix?
2
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?Thank you for posting! I am sorry to hear about this problem with Vipre.
First lets check your Add/Remove Programs please make sure that there are not any other AV security programs installed per these can conflict with the Vipre scan engine.
Next please make sure that your definitions are current on the Updates section under the Main Overview Tab.
Now lets reboot the computer when Windows first starts up begin tapping the F8 Key>Select Safe Mode>Log in as Admin User Account> Agree to Safe Mode>Open Vipre>Run a Deep Scan>Clean. It will now be safe to reboot Windows into Regular Mode.
Please let us know if the problem persists.
I’m confident
-
Inappropriate?Thanks, I followed your instructions and it did the trick. There was another AV security program that was conflicting with Vipre.
Thanks for all the help!
I’m Content.
-
Inappropriate?I have a recent similar issue with Vipre Scheduled Deep Scan. It runs OK until it reaches about 75% complete and Vipre auto shuts down AP and I get the red icon.The Deep scan freezes and when I try to switch AP back on, the scan just ends and never finishes and there is no record that it ever even ran. I'm using versions: Software 3.1.2416, Vipre 3.2.1886.2, Defs: 5014.
I have a fresh install of Vipe, so no previous AV has been installed. I'm also using Sunbelt Personal Firewall.
I actually haven't seen this problem since the recent Defs updates. -
Inappropriate?Thank you for your post!
It is hard to say exactly what is causing this issue, did you notice what file the scan was getting hung on when the AP crashed? It may be that this is do to a conflicting program there is an update coming out tomorrow to address some issues with Vipre and the recent update since def 5003 has also made a lot of changes to the way Vipre scans for threats. If you experience this issue again.
Please send an email to us here at support@sunbeltsoftware.com so that we can gather some logs from your installation of Vipre to better assist with what is causing this to happen.
I’m confident
1 Comment
Add a comment
This answers the question
-
Hi Jacob. Working on a Sunday? I'm impressed. I find Deep Scan hangs up in a Flight Simulator folder on my G: Drive. I'm not sure what file, but I know files for FS can be rather large. Here are some things I have done. Deep scanned in Safe mode. Custom scanned my G drive in normal mode (which actually finished successfully!) and now the only recent change I made to my computer has been adding a USB drive (which is U3 and acts like a CD-Rom drive). I'm running a deep scan now with USB drives ignored to see if that may be the problem.
What I haven't tried yet was to disable Rootkit checking but in my mind what's the point to dummy down your Malware protection? But I'm going to try that next if ignore USB drives doesn't work. -
Inappropriate?CaptKirk,
If you're still unable to complete the deep scan please try a deep scan of the system with the rootkit detection temporarily disabled. This will tell us if this is the part of the scan that's causing the problem.1 Comment Add a comment
This answers the question
-
Yes I will try that, but again, if it is the Rootkit module, what's the point of doing a deep scan with that feature disabled?
-
Inappropriate?CaptKirk,
For the moment we're just doing this to determine if there is something on the system causing a conflict with the rootkit detection. If this is the case we'll have to see what on the system may be causing the conflict.2 Comments Add a comment
This answers the question
-
I'm running a deep scan with rootkit turned off as I write this. My disable USB drives did not matter. The program ceased after 72 minutes and AP
shuts off at file G:\microsoft games\Flight Simulator 9\MegasceneryLA\SanBer_w\Texture\003002232201112Fa.bmp. I will report if disabling Rootkit makes a difference.
Update: I just individually scanned the directory above with Rootkit enabled and it ceased with AP shutting off at file G:\microsoft games\Flight Simulator 9\MegasceneryLA\SanBer_w\Texture\003002232201112wi.brr -
I just scanned the same directory with Rootkit diabled and AP ceased with the red icon at file G:\microsoft games\Flight Simulator 9\MegasceneryLA\SanBer_w\Texture\003002232201113an.ag. I will check and reinstall the Megascenery procuct to see if these files are corrupted somehow.
-
Inappropriate?Yes please reinstall the FS and once reinstalled please add this to the always allows list for Vipre.
1. Within VIPRE, go to View > Manage Malware > Always Allowed.
2. From here you will be in the “Always Allowed” list, which lists everything you have set VIPRE to ignore, whether it be through an Active Protection popup or a scan.
3. To manually add something to the list, select the “Add” button at the bottom.
4. Now you will have to navigate to the folder of the program you want to allow, which is the first option. If its just a single file, select the third option, Allow files by file name only, and navigate to the specific file. If you are unsure what file or folder to add, just email me back with the information VIPRE flagged, and I’ll let you know what to add.
Once you have added the file, you should see it listed in the Allowed List section and VIPRE should not flag this file or program anymore.
If you need any further assistance, just let me know.
I’m happy
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
Jacob, I reinstalled the Megascenery product and that allowed Vipre to complete a full Deep Scan. Very interesting that corrupt file(s) (how they were corrupt I have no idea) would cause this strange behavior from Vipre. At least this was an interesting exercise to troubleshoot the problem and that in actuality, it wasn't the fault of Vipre. Thank you for your help in this matter.
