ESET 4.2.35 update information issue

The balloon show signature database 4998:


The main window show signature database 4999:

 

Same here on XP Home SP2. I've also had the amber icon at least twice today and warnings about update failures which disappear when I go online (I'm on dialup).

I wonder if one of the recent module updates is responsible for this?

 

LOL! That is a cute cosmetic bug! I have the same problem too...

 

Clear your update cache and try again, it's quite likely a minor bug.
See below screenshot and try updating again.

 

What's funnier is that now there appears to two signature versions with the number 4999. As in the update I received this morning was the same one from yesterday afternoon. #4999 even shows up twice on the official list and both copies are the same.

 

It appears to have been fixed (or to have fixed itself?), because both the taskbar and main program window are now showing 5000.

 

Well since 5000 was released. But 4999 was released twice. First it was last night, then this morning.

 

My log files show update 4999 was only released once.
Regardless, I think that we can move on unless others are having issues updating from update 5002 forward.

 

http://www.eset.com/threat-center/threatsense-updates
The database says othervise.

 

I'm sorry, would you be more specific, I have no knowledge of a recent update having been released twice. If this had been the case, one of the ESET Mods would have announced this.

Regards,

 

I suspect it was a mistake. I was notified twice of version 4999, and when I checked the list, it featured #4999 twice. Same number with same list.

 

This is interesting- Checking out the online database update record here does indeed show two v.4999 updates being released, namely NOD32 - v.4999 (20100404) and NOD32 - v.4999 (20100405), though the payload looks the same; as per BTIsaac, it's probably some kind of mistake by Eset.

 

It is a glitch with the US virus signature database as the EU site does not reflect the same information, also, if the virus signature database update has/had the exact same code your software would not poll it twice.

We need to know if the OP has resolved her/his issue, most importantly.