![]() |
|
#1
|
|||
|
|||
|
I saw this issue being addressed a few times in the other sub-forum, so I know I'm not the only one having this problem, but I didn't see any answers, so I have no choice but to ask again.
NOD32's virus signature database didn't update since version 3808. When I try to update manually, it tells me that my virus signature database is up to date, even though the site clearly says that version 3808 is the latest one. I know my license is fine, since I'm not getting an 'Incorrect user name or password' message every hour. Besides, I bought it 6 months ago and it was supposed to last a year. I'd like to know what's causing this problem, will it be fixed automatically, or if not, how to fix it. |
|
#2
|
|||
|
|||
|
I am stuck on 3796
|
|
#3
|
|||
|
|||
|
Update 3815 (20090131)2009-01-31 09:32
Win32/Kapucen.NAM I can not update, I am in 3814, and 3815 and updated in this web, I do it manually several times and nothing. Any comments? Thanks |
|
#4
|
||||
|
||||
|
Quote:
|
|
#5
|
|||
|
|||
|
Oh? That's understandable. And in the same time, reassuring.
At first, I thought it was something my Windows update downloaded three days ago. Then I heard there was some issue with similar symptoms last year, and it required reinstalling NOD32. But it's maintenance. That's good to hear. |
|
#6
|
||||
|
||||
|
.......I installed the trial version 3.0.669.0 yesterday with the virus signature database: 3231 (20080701).
The virus signature database won't update. It says that I'm up to date but apparently I'm not. Server maintenance should be over by now but I still can't update the virus signature database. Any help would be greatly appreciated.......
__________________
--- Tommy --- |
|
#7
|
|||
|
|||
|
Quote:
I've just installed the EAV 3.0.669 trial version and it updated the signature database to the latest version immediately. Are you still unable to update? |
|
#8
|
||||
|
||||
|
.......it just updated from 3231 (20080701) to 2975 (20080326) which seems to be an even older virus signature database than the one before the update.
I tried again to update manually but it says I'm up to date which I'm not. I'm just in the process of switching from BitDefender to NOD32 even though I have nearly 3 years of a BitDefender subscription left but I'm having trouble with BitDefender for about a month now. The problem seems to go on with NOD32. I really want this to work because I like NOD32 better than BitDefender. Hopefully this can be sorted out.......
__________________
--- Tommy --- |
|
#9
|
|||
|
|||
|
Quote:
There's definitely something wrong with your EAV. Try uninstalling it completely and installing it from scratch. I assume you don't have any other security software installed that might prevent NOD32 from saving information to the registry or disk. |
|
#10
|
|||
|
|||
|
Although I have manually updated to the most recent signature (3816), the date I display (20090201) is different from the date shown on the website (20090131). I have never seen this before.
|
|
#11
|
||||
|
||||
|
The updates are issued from Bratislava. The update on the U.S. site uses local time and would indicate the time in the States as to when the update was posted.
|
|
#12
|
|||
|
|||
|
Thanks Ron for replying. My log file shows signature updated at 1/31/2009 at 10:29:02PM. Shouldn't date be 20090131?
The reason I am suspicious of this is an update problem I had on the beta as described here: http://www.wilderssecurity.com/showthread.php?t=231972 Last edited by Thankful : February 1st, 2009 at 11:23 AM. |
|
#13
|
||||
|
||||
|
I suppose the update would list the date in Bratislava. Technically, either one is correct depending on your location.
At the time of your beta update thread, Version 4 did in fact show the program as having updated although it was never listed on the update sites. The reason for this is unknown to me. |
|
#14
|
|||
|
|||
|
Mine went down to 2740
|
|
#15
|
||||
|
||||
|
Quote:
.......uninstalled and cleaned the registry and then a fresh install. Everything seems to be fine now. Updated automatically to virus signature database: 3817 (20090202) which is the latest one. Thanks a lot for the tip.......
__________________
--- Tommy --- |
|
#16
|
|||
|
|||
|
Is there something I can do?
|
|
#18
|
|||
|
|||
|
Quote:
Clean the registery and reinstal? How do I clean that? |
|
#19
|
|||
|
|||
|
Delete the HKLM\Software\Eset key in regedit and delete c:\Documents and Settings\All Users\Application Data\ESET (C:\Programdata\ESET\ESET NOD32 Antivirus in Vista) after uninstalling.
|
|
#20
|
|||
|
|||
|
Quote:
It still won't update. |
|
#21
|
|||
|
|||
|
Quote:
|
|
#22
|
|||
|
|||
|
Quote:
Yeah, I did all that, deteled the registry and nod32 after. Reinstalled the whole thing and it still won't update to anything newer than version 2740 which is dated 2007-12-21 ..... |
|
#23
|
|||
|
|||
|
Quote:
|
|
#24
|
|||
|
|||
|
Quote:
XP sp3 |
|
#25
|
|||
|
|||
|
^^ Yup when i try to update on my sp3 machine the database goes back to some v2967 or something. But updates nicely on my sp2 machine. I am using the trial version 3.0.669.0. Xp sp3 sucks.
![]() |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|