Loading Profile...
Build 5018 crashing VIPRE
The current VIPRE build that just arrived (5018) crashed VIPRE on my PC. After restarting the PC, VIPRE did not load automatically, and will not load manually. I have had NO problems with VIPRE before and have been running it since mid-2008. PC running XP-SP2, P3@1.2ghz (Tualitin), 1gb RAM. How do I roll back to build 5017 until this is fixed?
I’m amused (but only for the moment!)
8
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 have this same problem with defn 5019 - Win XP SP3
it doesn't load and when I try to load it manually, I get a 100% usage of CPU and it just won't load.
I’m frustrated
1 person says
this answers the question
-
Inappropriate?I also get 100% CPU usage when trying to re-light VIPRE. I'm going to de-install/re-install. I found the place on the website to get older defs:
http://www.sunbeltsoftware.com/Home-H...
I've downloaded and saved the 5017 file, as it was the last good update. I will load that after re-installing the VIPRE base load. I don't know what Sunbelt did to 5018 and 5019, but I'm turning off automatic updates until users get a notice that this has been fixed!!
I’m not amused.
-
Inappropriate?I reinstalled on my vista and my xp machines, I don't how they turned a good program into a steaming pile of crap...don't they test updates before turning them loose? IF I get calls from all my customers I'm giving them sunbelts phone and email..I refuse to cleanup their mess for free this time.
I did find a workaround while reinstalling, I just went into the definitions folder and deleted everything with a march date. Then I started up vipre and it came right up and updated completely. Try this instead of reinstalling.
I noticed they got rid of the incremental updates..it just gets them all in one go now.
Don't forget to go into file>settings>active protection, and uncheck "check files when they are opened or copied" leaving this checked will surely get you back to the high cpu usage again. Actually this setting should be off by default if I had my way.
Ok it's 3am and only one more xp machine to fix...thanks sunbelt, you guys owe me $$ -
Inappropriate?Hey Everyone,
I'm sorry about the problems. The high CPU issue is due to a major change in the definitions calculations, where we are switching over to a new detection method. Unfortunately, the switch takes awhile to perform. We have since pulled this update until we find a better way of updating to the new system.
If you are currently receiving persistent high CPU usage, you can do a full Definitions Update to wipe out all old defs and upgrade you to the new ones.
or, you can revert your definitions back to 5018 by following the link below.
http://www.sunbeltsoftware.com/Home-H...
or, you can uninstall and reinstall the program, which will also revert your definitions back to a previous version.
Again, I'm sorry for the problems. We are working hard to get everything back to normal.
Regards,
Jason Layman1 Comment Add a comment
This answers the question
-
Jason - I think you mean that we can revert our machines back to 5017?? 5018 is what started crashing VIPRE on our PCs. Also, once VIPRE is crashed, it will NOT run, so it's not possible to do a normal full defs update from within the program in order to clear the problem. Gordon's method above, or a full de-install/re-install if that fails, is the recovery method that seems to work. I also notice that def 5018 is still available in the list at the downloads page. That link should be removed entirely to prevent others from grabbing it manually. Is the def titled "Latest" now 5019?? Please note that another user reported 5019 causing the same problem. I am now back at 5017 and have auto updates turned off. VIPRE running correctly at that build.
Last request: For users who don't have a "Get Satisfaction" forum account, Sunbelt should be sure to send a general email to ALL registered users when this is fixed, so everyone gets the word. -
Inappropriate?5017 is the build that works for me on all my machines.. also one we end the SBAMsvs.exe process all the systems become inactive in the Enterprise agent and we can no longer push out updates to the clients. What is the best way to address this thru the Enterprise agent?
-
Inappropriate?I for one, am surprised and dissapointed at the issues I've had with this product during the past 2 weeks of slowly deploying it to > 75 clients.
Fortunately for SunBelt, this issue didn't occurr on any of Managements PC's, mainly becuase they fall into the "less than 2 year old" category.
Perhaps I should send in a few of my ordinary workstations for a "real-life" testing environment, so this can be avoided in the future.
Most of my production PC's are p4's < 3ghz packing 512mb of ram. Harldly light weights when one takes into account that these machines only surf the internet, collect mail, and run the occasional light-duty client db application.
This reminds me of an issue when I rolled out Symantec v10 to a v9 shop.
The Symantec client immediately starts a system startup scan, and brought the whole office to it's knees.
Only after fielding what I can assume was a flood of support calls did they issue a patch to reverse this behavior.
I've had to uninstall the VIPRE Enterprise client from at least 6 workstations and reinstall it, just to get folks working again.
I've decided to turn off automatic updates, and take the "wait and see" approach to program/definition updates, much like I do with Microsoft products....unfortunate, since this is MUCH more vital than an M$ patch, IMHO.
I’m not happy...
-
Inappropriate?Hi everyone, I do apologize for this issue that you have all had. The updates were on our server for an hour before they were pulled off because of this problem. We have taken internal actions to make sure this doesn't happen again and we will have definition update 5020 out as soon as we can which will NOT have this issue.
Sunbelt understands your concerns and we will do everything we can to make sure they are addressed.
Jamie3 Comments Add a comment
This answers the question
-
Jamie - Thanks for this message. I missed this before posting my most recent 'aktech' comment. I do note, however, that build 5018 is still available on the defs download page. The link to the build "Latest" (5019?) is gone, but 5018 is also the offender. Please remove that link as well. Thank you.
-
Hello! We are not seeing any crashing issues with 5018. So if you are having it with 5018 I would like a tech to take a look at your system.If this is the case please let me know and I will get a tech on the case. I assume you are running the consumer version?
Thanks,
Jamie -
Jamie - In response re: 5018. Yes, I'm using the consumer/home version. Several posters here report the same issue with 5018. Last night, as soon as VIPRE downloaded the 5018 update, it went down and severely impacted my PC. I restarted the PC, but two attempts to restart VIPRE resulted in high CPU utilization and no visible operation of the program (no icon in System Tray). Thus I de-installed/re-installed and rolled back to 5017. To have your techs look at my system, I would have to re-invoke the 5018 update, which I don't wish to do. Try this on your lab machines, please, running a fully patched version of XP Pro-SP2. If that is not failing in the lab, then I'm not sure what's going on. I'll wait for build 5020 before re-updating.
-
Inappropriate?Sunbelt: Are you listening well? Let's get this fixed TODAY!
When I first made the decision to switch to VIPRE in mid-2008(after using AVG and Counterspy for some time), I noted that the base load was only around 12mb (I still have the old setup file). Now it's 71mb and the update file is 110mb. Any list of defs must grow with present threats, of course, but I sincerely hope that VIPRE does not become another pig of bloated code like Norton. Your claim to fame was that VIPRE would be fast and light on its feet. The expanding program size and this current smackdown does NOT inspire confidence.
-
Inappropriate?Thanks for clarifying the problem. We have 5018 installed on most of our machines here. Most people encountered the problem when going from 5018 to 5019.
Hopefully 5020 will help in your situation. If you doesn't, please contact us directly in support, I'll have one of my lead techs assist you.
Our email address is support@sunbelt-software.com1 Comment Add a comment
This answers the question
-
Thanks Mike. I see that a new file "Latest" has been added to the defs download page. Is this in fact 5020? If so, when I go to update from 5017, will VIPRE first try to download 5018 as an incremental update, or will it simply go get the "latest"?
-
Inappropriate?Hi,
That link simply get's the latest posted version. It was created for people that have to manually update that way they don't have to keep changing the URL they download from.1 Comment Add a comment
This answers the question
-
Mike, you didn't really answer aktech's question. Is "latest" 5020 and will VIPRE download only latest or 5018 first then 5020? I am also having problems with 5018.
-
Inappropriate?Hi GinIT,
Sorry, That link has 5018 posted on it. it's just there for continuity.1 Comment Add a comment
This answers the question
-
Mike - thanks but this still does not answer these two questions. Several posters need this info specifically, please:
1. The defs page has BOTH a 5018 link and a "Latest" link. Is the latest link for 5020?
2. When VIPRE updates from 5017 (in my case), will it try to get 5018 first (as in an incremental update), OR, will it just skip to the "latest" file (whatever that is). -
Inappropriate?Hi Aktech,
On the manual updates page both the one listed as 5018 and latest have 5018 posted.
5020 hasn't been posted yet. It will be posted as an incremental update, so your VIPRE will first download and apply 5018 then immediately download and install 5020.
If you run into any trouble updating, the full definition file will posted for downloading on the manual update page.1 Comment Add a comment
This answers the question
-
Thanks, Mike. Several of us are indeed having problems with 5018, so in my case I will wait for the full 5020 def file to be posted in manual updates and then directly update from 5017.
-
Inappropriate?I updated to 5021. Still get 99 pct cpu usage and Vipre never completes start.
So I disabled Vipre and redeleted 5019 and later definitions and restarted Vipre. Runs fine. What now? When do we all get a working update?1 Comment Add a comment
This answers the question
-
David - How did you do an incremental disable (rollback) without de-installing the program?
-
Inappropriate?I went to my computer/ c disc / programs / sunbelt / vipre / definitions and put in time order, newest on top, and deleted the most recent, back to when vipre crashed.
I do get a more or less functional program. I had to disable vipre using administrative tools / services first, and stop the process with task manager. I think I'm going to uninstall entirely and switch to another program. I have 3 PC's each with a different AV program. Spydoctor is OK but slows down the system. Rising is on an old salvaged PC, which works fine. I can always come back and download a fresh copy of Vipre, once this mess is over. By the way, I have XP SP3 on all 3.1 Comment Add a comment
This answers the question
-
Thanks, David. If this helps, I switched to Vipre in July of last year and have had zero problems until this issue with build 5018 or whatever it was. I'm running on XP Pro SP2. The program has credibly intercepted some nasty stuff, and a side benefit is that it has a secure file cleaner utility. If you are intent on switching anyway, I think Bit Defender (NOT Windows Defender) is the top of its class and is about the same price as Vipre. But I would give the new Vipre build 5022 a try first. I completely de-installed and re-installed after that 5018 crash, and all is running smooth now on the new build.
-
Inappropriate?For those who continue to see high CPU usage even after a reinstall, follow the instructions below to remedy the issue.
Since the CPU usage is high, and the computer probably very sluggish, we'll have to first disable the service.
1. Click start then run, and type in "services.msc" then click "Ok."
2. In the window that opens find the service Named "Vipre antivirus + Antispyware."
3. Right click on it and go to "Properties." In here change the "Startup Type" to "Disabled" and hit "Stop" to stop the service, then click apply.
4. Now navigate to the following folder, C:\Program Files\Sunbelt Software\VIPRE\Definitions
5. Delete the files named "cadd.vtd" and "cdel.vtd."
6. Now restart your computer.
When your computer comes back up, everything should be back to normal. You can then go back into services and turn the VIPRE service back on.
Regards,
Jason Layman -
Inappropriate?Completely solved the problem by uninstalling Vipre completely, downloading a fresh copy, restarting and updating. Should have done that the first day.
I’m happy
1 person says
this answers the question
-
Inappropriate?I'm running successfully on build 5024. Looks like the crisis has passed. Thanks to all the posters and to Sunbelt for your guidance and attention. For those still having problems, the answers in this thread seem to be doing the trick for those that posted, so try the solutions as described, especially Jason Layman's suggestion from Sunbelt. Or just do a full re-install and get the latest update file to clear out the bad stuff.
I’m happy
