Discussion in 'ESET NOD32 Antivirus' started by BurtieLad, Jul 26, 2008.
This is pathetic. Still cannot update after clicking update 200 times.
I, too, am having this problem (ESET Smart Security 3.0.669).
I read elsewhere that a complete uninstall/reinstall would fix the problem, but that only brought me even back in terms of updates (3230 from 3302).
If this isn't fixed today, I will be a very upset customer.
P.S. First post - I just joined.
I appologize for being a v2 user it seems we are in the way of V3 users.
One thing for sure I'm not going to sit here and click all day to try to guess when v2 will be updated.
2 days since last update.
Worked for me on about the 5th attempt.
A 1265kb update was downloaded, and my signature is now at 3306.
Is there any reason that prevents you from upgrading to v3? If there is an unresolved issue you had with v3 in the past, сould you please provide us more details about it?
This is not working still, reinstalling is not an option as i have 230 users. The client on the server updates fine and is current. It is not installing correctly on any user. I am running the most current server version.
I'm using v.3.0.669 on 32 bit Vista Ultimate.
After reading about this problem here on the forum I noticed that my own copy was still at update 3304 from yesterday.
I tried manual update a dozen times to no avail. I was going to try clearing the cache, but Marcos gave the path for XP, and rather than go hunting for it I decided to just try a repair.
Went to Control Panel-uninstall a program- right clicked Eset and chose repair. I had to point it to my copy of the downloaded program, and reboot, but as soon as the computer rebooted Nod32 is at update 3306.
Just did this a few minutes ago, so don't know if it's fixed, or will be stuck on 3306 now.
Been a couple of hours now since I did the repair and got Nod32 to update to 3306. Just checked and see that 3307 is out but Nod32 has not downloaded it, and manual update does not find it.
Not a good sign.
Re: NOD32 no longer updating properly at all
I reinstalled v. 3.0.669 (the dutch version) and guess what
The database won't be updated for NOD says that i have the most current one, and that while my signature says 3220, and the most current one is 3306, even a manual update won't help (cause it doesn't do anything), NOD keeps saying that i have latest installed
According to me, it doesn't have anything to do with that giant update.
Re: NOD32 no longer updating properly at all
This is getting past a joke. I've recommended NOD to countless people, and they're going to be phoning me up soon!
Is there any word as to when everything will be functioning normally?
This was posted by Marcos:
None of my v2 users are able to update today, also my own systems are not updating. Are the Nod32 update servers running today?
I just received update 3307 automatically after having problems updating earlier this morning. Hopefully, things are improving.
My server is on 3307 my clients are on 3279. The server says that the installed version is 3307.
Our clients are updating to 3307 now after problems this morning also.
I am unable to update from 3304 (28th). Have given up.
Big update, too big for my 6.5Mb line
So I clicked it about 10 times, but it has now updated for the first time in 3 days.
If this continues, I think I might go back to Kaspersky.
Well, great. Now mine is reporting that it's antivirus module has failed to start up. What's next? A zombie invasion?
Hi. I use NOD32 AV v.3.0.667.0 on my Windows Vista Ultimate (32-bit) laptop and have had the same problem as listed above. The automatic updates fails and says the virus signature is current. I have two other computers using ESS v.3.0.669 on Windows XP SP3 and both, since yesterday, have had the same problem, freezing at the 3300 virus signature; manual update doesn't work either. This happended earlier before this year, but with NOD32 v.2. I hope it gets solved quickly, because it's highly frustrating to have such problems with such a good and dependable AV.
I want to add that with my EAV 3.0.667.0 cleaning the cache possibly helped, because after doing so, it only took two tries before the update process completed succesfully. By the way, the path for WinVista is C:\ProgramData\ESET\ESET NOD32 Antivirus\Updfiles.
Finally, I want to thank Marcos for his good support. Too bad that he seems to be the only one from ESET to be giving answers.
I have 3.0.669 installed on 3 computers. One is showing signature update 3307 and the other two are showing 3304. When I try a manual update on any of the computers it comes back immediately and says the an update is not necessary. Clearing the cache has no effect.
That is exactly what I have, alongside this.
Your problem is okay. It should be resolved soon.
I'm also stuck at 3304.
i'm one better, with 3305 on my laptop.
strangely my pc is completely up to date (3307).
Now at 3307 clearing the browser cache worked.
you win then! clearing the cache didn't work here, not too bothered at the moment, i trust eset to get it back on track.
I'm stuck at 3305. We'll keep monitoring the situation and consider dedicating some update servers just for v3 instead of both v2 and v3. As a result, v3 users will update faster and thus allowing more other v3 users to download the update, however, these servers won't be available to v2 users. You can imagine how big load it is given that 30 update servers have been fully loaded for about a day already. This reminds me sweet old times when 3-4 update servers were enough to serve all users
Edit: eventually updated to 3307
Separate names with a comma.