Problem with latest virus defs? 1.1087

All sorted now guys, no idea what was wrong but those hard and late working guys at eset have resolved. Update NOD32 and all will be OK.

 

All fixed here!

Very fast in response.

Thanks again!

 

I never had a problem earlier

controlmind

 

I never had this bug at all.....it updated without any problems from 1.1147 to 1.1149 and now I also have recieved 1.1150.....

 

Firecat, you missed out on something...

 

I'm not sure if anyone else already stated this, since I sort of skimmed this thread, but...

This last update was apparently associated with a NOD32 engine update, that is why the update was reported as including outdated signatures.

The engine update was probably frozen for QA testing and eventual release with the specific signatures of that particular day. However, as soon as I ok'ed the engine update and rebooted the computer, the current signatures were once again downloaded and applied. Anyway, that's what it looked like based upon what my computer exhibited.

 

I'm speculating here, but people who may have received the updated engine in some other manner, perhaps by manually downloading updated NOD32 code or beta code, probably would not have noticed anything at all since they wouldn't have received the automated engine update which included the outdated signatures.

 

My experience was a bit different. I got the 1.1147 update three (3) times (at 5:01:37 a.m., 17:01:42, 18:01:39) and then finally the 1.1150 update at 19:07:37 U.S. time. Since updates are cumulative, I assume that everything is ok?

 

But I used the updater just as usual.

 

No, you must have misunderstood, by your own words, you manually downloaded and installed the new version 2.50.25. Many of us chose not to do so and just waited for 2.50.25 to be released via automatic program components update. What I noticed on my machine was that on 6/21/2005, during the update process rather than downloading a simple signature update, NOD32 downloaded a program components update (upgrading my code to 2.50.25) along with signatures 1.1087 (20050503). When initially downloaded, the virus signatures were reported as out-of-date, but NOD32 informed that a program components update had been downloaded and requested permission to install the update, and then after approval requested permission to reboot my computer. After the reboot, it downloaded the current virus signature update and everything was back to normal. You apparently (according to your June 15 post) had already manually installed 2.50.25 and so you shouldn't have seen a program components update.

 

No - I think the timeline was that the component update came down a couple of days before this erroneous definitions update. The 1.1087 update was a step back of ONLY the definitions, and did not coincide with an engine update.

regards

Greg

 

Yes, you are right - I had misunderstood. Thanks

 

You may be correct, I can only tell by what seemed to occur on my machine:

Code:

Time	Module	Event	User
6/21/2005 15:47:56 PM	Kernel	The virus signature database has been successfully updated to version 1.1087 (20050503).	
6/21/2005 15:47:55 PM	Update	NOD32 program components have been updated successfully. For changes to take effect, a computer restart is required.
6/21/2005 15:46:06 PM	Kernel	The virus signature database has been successfully updated to version 1.1087 (20050503).

However, I'm currently on a laptop and I often hibernate the machine rather than do a full power cycle, so I guess it's possible that I received the program components update previously and just didn't know it. The only problem with that theory, though, is that right during the 1.1087 update cycle I received a NOD32 pop-up specifically asking me whether I wanted to install the program components or not. That's seems to be just a little too coincidental to not have been downloaded during the same update as the 1.1087 virus signatures.

 

My NOD32 seems to update to the proper virus definitions, but
then lists 1.1087 as the current definition.

Requesting another update, triggers NOD32 to download 1.1087
again but at a 0kb size. This can happen several times until
finally the correct definition is shown.

See below for the Event Log of my most recent update:

Time Module Event User
6/28/2005 19:51:27 PM Kernel The virus signature database
has been successfully updated to version 1.1157 (2005062.
6/28/2005 19:51:06 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
6/28/2005 19:50:52 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
6/28/2005 19:50:42 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
6/28/2005 19:50:33 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
6/28/2005 19:50:19 PM Kernel The virus signature database
has been successfully updated to version 1.1087 (20050503).
6/26/2005 17:00:23 PM Kernel The virus signature database
has been successfully updated to version 1.1155 (20050626).

Best Wishes,
Rivesaltes.

 

It appears to me you 100% don't update your NOD32 for Eset's servers.

 

Okay, so what am I doing wrong? Or better yet, how do I fix this?

Best Wishes,
Rivesaltes.

 

May be you are using some of the "innoficial" update servers. Which is one of the thingies on my "Don't ever try this" list...
Try one to set update servers to "choose automatically"...

 

Marcos just means to say that he thinks you are not updating NOD32 from Eset servers and have custom-added some server from which you are updating. Thats a definite no-no...

Do as mrtwolman said, try setting update servers to choose automatically

 

that would make sense - if a non-official and no longer current update server was somewhere in the middle or the list of official servers, it could be used occassionally, and that would be one explanation as to how the old update keeps re-appearing...

 

Thank you all for your comments.

I have the Server selection set to <Choose automatically>.

The list of servers in my NOD32 has not been modified in any way.
To the best of my knowledge, these are official servers. The servers
- that are listed - are as follows:

u1a.eset.com
u3.eset.com
u4.eset.com
82.165.250.33
A:\nod_upd\
V:\nod_upd\
W:\nod_upd\​

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

My latest update went pretty much as before. My NOD32 seems to
update to the proper virus definitions, but then lists 1.1150
instead of 1.1087 as the current definition. Requesting another
update, triggers NOD32 to download 1.1150 again but at a 0kb
size. After two attempts, the virus definitions was listed
correctly. See below:

Time Module Event User

6/29/2005 17:28:27 PM Kernel The virus signature database
has been successfully updated to version 1.1158 (20050629).

6/29/2005 17:28:14 PM Kernel The virus signature database
has been successfully updated to version 1.1150 (20050621).

6/29/2005 17:28:00 PM Kernel Statistical information has
been sent to Eset.

6/29/2005 17:27:57 PM Kernel The virus signature database
has been successfully updated to version 1.1150 (20050621).

6/29/2005 17:26:35 PM Update Error connecting to server
82.165.250.33.

6/28/2005 19:51:27 PM Kernel The virus signature database
has been successfully updated to version 1.1157 (2005062. ​

Thank you,
Rivesaltes.

 

Do you have a mirror version running, or a regular version?

Do you have the folder nod_upd located at the root level of any of your drives?

 

Not sure what you are asking, here. But, if it helps, mine is a standalone NOD32 running on a single PC - with no network connection - updated through a dial-up provider.

Nope, double-checked everything. (A:\;V:\ and W:\ are - respectively - a floppy drive, a DVD drive and a DVD burner.)

Thank you,
Rivesaltes.

 

Can you please post a screenshot of your update servers. This can be found here.

Cheers

 

What about installing NOD32 from scratch as follows?
- download the latest version 2.50.25 from Eset's website
- uninstall NOD32 and reboot the machine
- delete the program files/eset folder
- run the installer you downloaded

If there is a problem with some registry values, this should definitely fix it. Also, I'd suggest that you run some diagnostic tools that check disk and registry and can repair possible problems.