Loading Profile...
Erroneous Out of date Risk definition report
Why does VIPRE claim my risk definitions are out of date when I have checked the SunBelt Software site to confirm the fact that I have the latest definitions?
3
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?I too have this problem, and my defenitions are up to date (5111)1 Comment
Add a comment
This answers the question
-
I too have this problem, and my defenitions are up to date (5111)
I have the same issue. Ditto for me. My definitions are up to date.
Questions:
Why doesn't the software contact the server to check the update status? Or maybe it does?
Secondly, you have issued 17 updates since April 15 up through April 24. You have not issued an update since then. Is this just a weekend issue and there was nothing pressing on Monday? The 2 previous Mondays you issued 3 updates. Just curious?
I just like keeping my computer protected. -
Inappropriate?Why does VIPRE claim my risk definitions are out of date when I have checked the SunBelt Software site to confirm the fact that I have the latest definitions?
Ditto. Vipre shows that they are out of date on the Overview tab. Clicking Update shows out of date, too.
I’m ambivalent
-
Inappropriate?5112 has now propagated. My definitions have been updated. The timestamp on 5112 is 4/27 16:44:11, which is 4/28 04:44:11 here in Taipei. (We are 12 hours ahead of EDT)
As of 13:30 Taipei (01:30 EDT), 5112 had not propagated; Vipre defs were not updated. I shut down my computer and restarted at 14:43 Taipei. The defs updated at that time.
I’m amused
-
Inappropriate?Hello Murray,
I apologize for the inconveniences.
Try shutting your computer off like JerryZ did to see if Vipre automatically updates to latest definitions. You can always go to FIle from the main menu of VIpre>Settings>Check for Updates.
If you are still receiving the definitions being out of date please check the date and time of your computer and see if they are set correctly. If the date and time is not set correctly on your computer Vipre will always tell you that you are out of date on the definitions even though you aren't.
If you have more questions or need further assistance please feel free to contact me. Have a marvelous day!
Thank You,
Sean Donnelly
1 person says
this answers the question
3 Comments Add a comment
This answers the question
-
All very convenient to say that our computer clock is incorrect. It is obvious that sunbelt stuffed up here and would have appreciated a statement to that effect. Totally unacceptable that these issues are encountered. Most obvious problem was Sunbelt had not uploaded the new definition file however the server was expecting a new file therefore the out of date message. If Sunbelt are interested in good customer experiences they should get their act together and actually check that definition updates have propogated to the servers that customers download from. These problems are not acceptable.
-
I agree Derek. The clock on my computer was correct - in fact I have five computers all of which displayed the "Definitions out of date" report. All computers updated their definition files once Sunbelt provided an update The whole issue arose because of Sunbelt's failure to upload a new definition file in a timely fashion.
-
Try shutting your computer off like JerryZ did to see if Vipre automatically updates to latest definitions.
Sean, I put my computer on standby because I was leaving for several hours. I don't believe that there is anything wrong with my computer clock.
I, too, suspect a propagation issue. This has occurred before at Sunbelt. What I suspect is:
>> Our clients are contacting the server to check for out-of-date status, and the server is delivering a false status.
>> Or, the status server has not been notified of the new update.
>> Or a myriad of other reasons.
I trust Sunbelt. I have been using CounterSpy and SB firewall for a while. I recently dropped my old CA eTrust AV and installed Vipre AV. I count on Sunbelt to handle the updates flawlessly and seamlessly. Occasionally a problem is encountered in the update process. Please let us know when you encounter such a problem. Occasionally, we customers will find it first; if so, please take responsibility and accountability for the problem. IMHO, that is how to increase trust.
Even an "I don't know. Let me check." is greatly appreciated. Blaming computer clocks can come across as a dodge. -
Inappropriate?Thanks.
My virus definitions have now updated to 5112. The problem is now resolved. -
Inappropriate?Hello Edmonds,
I apologize for the inconveniences and misunderstanding on my part.
I was suggesting that it was possible that the date and time on your system clock could be off because the update section of Vipre/Counterspy tends to tell you that you are out of date even though you are up to date. This doesn't take in to account that your computer ended up updating on it's own and fixing the issue. We apologize for the inconveniences on our behave.
I will definitely pass on all of your suggestions as far as making sure that our website gets updated with the most recent definitions especially when they are released right away. We really want to keep and increase your trust.
If you have more questions or need further assistance please feel free to contact us.
Thank You,
Sean Donnelly -
Inappropriate?In my opinion, this is a bug. I had a trial version of Vipre which I installed in May, now in July I paid for it, and it cannot update with "out of date" nonsense, and cannot get past the may 2009 signature. I tried re-installing software. Finally, HERE IS THE FIX: I selected 'shutdown vipre'
and deleted the contents of the program files\sunbelt software\vipre\definitions folder. This changed by definition number to zero, and it updated properly to the current definition and now it works correctly.
Come on software QA people, it ain't that hard!!!
