Correct Datestamp of Update 1.1750

Would appreciate clarification as to the correct datestamp of Signature version 1.1750, that appearing jn the info contained in the program’s auto updater download i.e:

NOD32 antivirus system information
Virus signature database version:1.1750 (20060911)
Dated: Monday, 11 September 2006
Virus signature database build: 7998

or that shown in the eset website at this link http://www.eset.eu/support/update-xy1 viz:

2006-09-12 00:24 Update 1.1750 (20060911)

 

This one is correct and the eset.eu site has now been updated to the same info.

Cheers

 

Many thanks Blackspear; confirms the info I posted in another Forum advising of this latest update.

 

My pleasure.

Cheers

 

Time Module Event User
12/09/2006 12:39:01 Kernel The virus signature database has been successfully updated to version 1.1752 (20060912).
12/09/2006 11:39:04 Kernel The virus signature database has been successfully updated to version 1.1751 (20060912).
12/09/2006 09:38:55 Kernel The virus signature database has been successfully updated to version 1.1751 (20060912).
11/09/2006 20:10:35 Kernel The virus signature database has been successfully updated to version 1.1750 (20060911).


Two 1.1751?

 

Hi guys any answear about two 1.1751 updates?

 

I guess your just lucky

 

Hi, I wish to recive a more profesional answer that "I guess your just lucky"

So again, why have I two 1.1751 updates?

Is it a Nod problem?

 

No idea, stop looking at your logs, you'll go blind

Cheers

 

ROFL

Seriously though, there was a thread with this question top of the list just two days ago here. I found it by searching the forum for 'same update'

At this time it is not known for certain what the cause is but the linked thread mentions a few possible causes.
Although it is not the very first time it has been asked about, it's pretty uncommon and it does not affect the correct function of NOD32 in detecting threats.
Also, since your NOD32 has already updated again it will not be possible to provide to the things required for a better diagnosis.
Blackspear is right - leave your logs alone, if you are actually getting updates and your NOD32 is working great then there's really no need to go there.

Cheers

 

Hello guillijan,
Here is a theory for the mutliple updates based on observing the process a few times when it occured.
If the update has "extra" components it is possible for the engine updates (av patterns) to be downloaded but the utilsmod or archs components to be interupted. Since the "normal" module was OK Nod32 will report the update. Later either on schedule, or by a manual check the other component is successfully downloaded and the update mechanics report the successful update to the same update as before because it is the same update.

 

Thanks for all.

I'm very sensitive with nod because I've used Kav for a long time, and Kis for the last four or five month. Each one makes (Kav 6.x.xxx) my pc very slowly so I try nod but have problems with the update so I decided to buy it so in this way I supose never have updates problems.
Really I haven't problems in this moment and I'm happy with Nod.
Perhaps Blackspear have the reason and I must take it an easy and don't look logs (at least for the next six hours )

 

Yes. Blackspear is right. Just use the updates thread in this forum and see which version you should be on. If you are behind, use the update now. Very stress free.