Automatic Updates Do Not Seem To Be Working In VIPRE

Sorry, I misread the original question and I was mistaken, there was the 2165 update this morning, and as to why it wasn't picked up by the scheduled check, I don't know but we'll certainly check into it.

Ok, if it happens again, let us know!

The same exact problem is occuring on my computer. I have to manually click on update to obtain the latest definitions. I waited 3 days for it to update automatically and it would not. Can you just implement the check for updates @ log-on like in CounterSpy? I never had a problem with that.

I completely agree with Greg3000's suggestion about checking for updates @ log-on. That always worked well for me with Counterspy. I also don't think automatic updates are working for me either & I have it set to check for updates every 2 hours. I've been manually updating updates instead. By the way, the updates are lightning fast, unlike Counterspy. I like everything about Vipre so far, except for the automatic updates.

It appears to be a 'bug' in VIPRE. I contacted their tech support and let them know my work around. I've found that automatic updates can be forced to happen by leaving the "make up missed scans with a Quick scan" option box checked (the default) AND making sure the scheduled scans are enabled for every day of the week (also default). VIPRE checks for updates just before it performs a scan, so you will then receive an update (and a quick scan) 5 minutes after the computer is powered on. (I had to discover this myself after many hours of changing settings and looking at logs.)

I usually like to decide when to run my own scans, so I had changed the defaults. I found out after I did that with auto-updates set to 1 hour, if your computer is on less than 2 hours and 40 minutes (as is often the case), I would never receive an update automatically, except of course when I did happen to run a manual scan. This leaves old definitions being used for real time scanning until I happen to run the next scan or leave the computer on for an extended period. I think this is a bad bug. (I hope their virus scanning portion is better thought out.)

I'm not sure if your problem is the same, but I checked the operation on my three computers, all of them did the same thing.

I hope this will help others until Sunbelt updates their program. I'm waiting to see how they do in Virus Bulletin's testing. I hope they do well, as I like everything else about VIPRE. I wanted a non-bloated AV and this is it. I heard they will be adding a firewall to it later this year. If so, I hope they will still offer the AV only, or at least an option to disable the FW in case you have your own favorite.

Sorry for the long post, but it is a complex problem until you discover the work around.

Make sure your computer is Not Going To Sleep due to your Power Setting Options. I have changed my Sleep Power Setting to "Never" and VIPRE Updates seem to be working fine.

Lou, i never set any of my computers to sleep so I know that can't be the problem. It's something written in the code that is screwing up because I have 2 other computers that do exactly the same thing.

Hi Lou,
I was able to reproduce this. We are checking the on the problem now and should have it fixed very soon. I believe the problem is here not in Vipre.

On a new install of v3.1.2243, on two different PCs (Win XP, no proxy), I do not seem to get any automatic updates to the risk definitions. In both cases, updates are enabled, the PC is booted, I login and wait, but nothing happens. Update frequency set to 1 hour for testing.

As I type this message (8/28/08 16:23 ET) one PC shows definition 2206 (8/27/08 10:32 AM), which I know is out of date because I updated another PC manually to 2207. Clicking the Check for Updates button downloads and installs a new definition set immediately (2208).

There are no problem conditions reported in the Vipre console log.

Is VIPRE normally capable of updating the engine automatically, or do program updates need to be manually installed?

I downloaded and upgraded to .2315, which downgraded my definitions from 2208 to 2205. 15 minutes later, no automatic update.

I will leave this PC as is and online overnight to see if the updater kicks off.

I have finally observed a 3.1.2315 instance auto update the definitions. Based on the system log, the system started at 7:54:03 PM, and the scheduled definition check occurred at 9:28:05 PM.

I observe two problems here: The update check is set to 1 hour, but the first check occurred more than 1.5 hours after start. More importantly, it appears if a system is started, used for a brief time, then shutdown, updates may never occur.

I have finally observed a 3.1.2315 instance auto update the definitions. Based on the system log, the system started at 7:54:03 PM, and the scheduled definition check occurred at 9:28:05 PM.

I observe two problems here: The update check is set to 1 hour, but the first check occurred more than 1.5 hours after start. More importantly, it appears if a system is started, used for a brief time, then shutdown, updates may never occur.

Where do you get version 3.1.2315? I'm still running 3.1.2249.

Sorry about the delay in response. I didn't notice the post. You can download the latest version at the following link.
http://go.sunbeltsoftware.com/?linkid...