Problem with latest virus defs? 1.1087

That will have to wait til later. I have to go to work now.

Here it is.

 

Well, I checked my disk (error-free), my registry (no problems there) and clean-installed a freshly downloaded copy of NOD32 version 2.50.25.

And, I'm still having the same problem.

NOD32 dowloads the update. (I see the download percentage counting-down.) Then the new update is reported as 1.1087. Then, I click for a manual download and get a dialog box asking for an update of 1.1087 at 0Kb - which I also click. After this, the update finally registers with the correct number.

See below for the latest event log:

Time Module Event User

7/2/2005 6:47:09 AM Kernel The virus signature database has been successfully updated to version 1.1160 (20050701).

7/2/2005 6:46:53 AM Kernel The virus signature database has been successfully updated to version 1.1087 (20050503).

6/30/2005 20:46:20 PM Kernel The virus signature database has been successfully updated to version 1.1159 (20050630).

Any more thoughts?

Thank you,
Rivesaltes.

 

Still having the same problem, but now NOD32 is reporting version
1.1160 instead of 1.1087.

=================================================================

NOD32 dowloaded the 1.1162 update normally. (I saw the download
percentage counting-down.) But, the new update was reported
as 1.1161.

Subsequently, I clicked for a manual download and got a dialog
box asking for permission to download a 0 Kb sized 1.1160 update.
I clicked "OK" to give my permission. Then, NOD32 reported 1.1160
as the current update.

The above was repeated several times; until, the update finally registered
with the correct number, 1.1162.

See below for the latest event log:


Time Module Event User

7/6/2005 16:54:14 PM Kernel The virus signature database
has been successfully updated to version 1.1162 (20050706).
7/6/2005 16:53:50 PM Kernel The virus signature database
has been successfully updated to version 1.1160 (20050701).
7/6/2005 16:53:20 PM Kernel The virus signature database
has been successfully updated to version 1.1160 (20050701).
7/6/2005 16:53:11 PM Kernel The virus signature database
has been successfully updated to version 1.1160 (20050701).
7/6/2005 16:53:00 PM Kernel The virus signature database
has been successfully updated to version 1.1160 (20050701).
7/6/2005 16:52:47 PM Kernel The virus signature database
has been successfully updated to version 1.1160 (20050701).
7/6/2005 16:52:38 PM Kernel The virus signature database
has been successfully updated to version 1.1160 (20050701).
7/6/2005 16:52:00 PM Kernel The virus signature database
has been successfully updated to version 1.1161 (20050704).
7/4/2005 19:37:48 PM Kernel The virus signature database
has been successfully updated to version 1.1161 (20050704).

Should I learn to live with this problem?

Any ideas or comments would be appreciated.

Best Wishes,
Rivesaltes.

 

Hi Rivesaltes, have you followed Marcos's suggestion in post number 75?

Cheers

 

Yes. (See post # 77.)

I downloaded a fresh copy of NOD32. Then, I uninstalled my old
copy of NOD32 and deleted its directory.

Ran chkdsk. No errors found.

Checked and cleaned the registry. No errors found.

Installed NOD 32 using the new download. Then started updating.

The problematic results of those updates are seen in post # 77 and # 78.

Thank you,
Rivesaltes.

 

The latest update was more of the same but now we are back once
again to registering version 1.1087.

Time Module Event User

7/8/2005 18:04:20 PM Kernel The virus signature database
has been successfully updated to version 1.1164 (2005070.
7/8/2005 18:04:08 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
7/8/2005 18:03:59 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
7/8/2005 18:03:52 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
7/8/2005 18:03:36 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
7/6/2005 16:54:14 PM Kernel The virus signature database
has been successfully updated to version 1.1162 (20050706).

Any suggestions?

Thank you,
Rivesaltes.

 

With this issue can you please send an email to support@nod32.com and place a link to this thread. If you do not hear from Eset within 3 days (allows for weekends), please advise us here...

We would appreciate if you could keep us in the loop with your progress, as we all learn this way…

Cheers

 

This has happened to me a couple of times, but only with update 1.1087 - 5/3/05, reappearing.
I just manually click update, one or two times, and it registers correctly.
The last time it happened:

Time Module Event User
06/29/2005 16:35:16 PM Kernel The virus signature database has been successfully updated to version 1.1158 (20050629).
06/29/2005 16:35:07 PM Kernel The virus signature database has been successfully updated to version 1.1087 (20050503).
06/29/2005 16:35:00 PM Kernel The virus signature database has been successfully updated to version 1.1087 (20050503).
06/28/2005 15:46:32 PM Kernel The virus signature database has been successfully updated to version 1.1157 (2005062.

 

Hello Rivesaltes,

Could you send a Belarc Advisor report to support@eset.us please? (http://www.belarc.com/free_download.html)

Thanks,
Bandicoot.

 

Just happened again for me... after the original update, I clicked *update now* two times, then it registered properly:

Time Module Event User
07/14/2005 7:58:33 AM Kernel The virus signature database has been successfully updated to version 1.1168 (20050714).
07/14/2005 7:58:25 AM Kernel The virus signature database has been successfully updated to version 1.1160 (20050701).
07/14/2005 7:58:14 AM Kernel The virus signature database has been successfully updated to version 1.1160 (20050701).
07/13/2005 5:06:47 AM Kernel The virus signature database has been successfully updated to version 1.1167 (20050713).
07/11/2005 15:40:40 PM Kernel The virus signature database has been successfully updated to version 1.1166 (20050711).
07/11/2005 11:06:39 AM Kernel The virus signature database has been successfully updated to version 1.1165 (20050711).

Interesting footnote:
I just checked my NOD updfiles folder, to see the dates of some of the files.
The two files dated 7/6/05, nod76C3.nup - version=1.1160 (20050701)... and
nod6F35.nup - version=1.1087 (20050503) - - interesting because those are the two updates, that have come back to haunt future updates.

I don't know if it means anything, but thought it worth noting

 

Can you please follow the advice of Bandicoot as well.

Let us know how you go...

Cheers

 

still looks like one of the update servers is failing to update or something...

 

That's as it should be. However, there should be another nup file with version 1.1168 in the header if your NOD32 is actually up to date.

 

Those were the one's that I thought were interesting
They both have come back to life, and were of the same modified date.
I actually have 13 *nup* files... the last is the latest update (version=1.1169 (20050714)).

Thanks!

 

I was going to do that, then I remembered a couple of months back, I had some strange computer problems, which started simultaneously with installing Belarc Advisor. I was getting all these trojan warnings with TDS-3, which stopped when I uninstalled Belarc.
While I don't think Belarc is bad, for some reason my computer was allergic to it.
So it's probably best not to reinstall it

The update issue happens so rarely, that it never really bothered me.
I only posted because the thread was already here, and I wanted to do my part in helping NOD get even better.

 

It actually downloads the update, and after installing it, it displays the wrong number. When I click update now, it doesn't download it again, it just pauses, then spits out the proper revision number & date.
Thus, I think it's the program itself, rather than server related.