I see several discussions on failure to update and am wondering how frequently one should expect an update of the virus signatures. I had assumed that any new signature at the ESET site would be available if I did an manual update. Instead, I get a response that my database is current when it clearly is not absoluetly current. One PC running v. 2.7 is now 3 days behind but manual update says it is current. I am trying v 4.0 on another PC and get a similar response, although newer signatures show at the ESET site. I'm not anal enough to need constant updates but it is troublesome to be told I am current when I am not. Is this a ESET server issue or what? Thank you any insight.
What OS are you using and are you running additional security software that might be interferring with NOD?
Win XP Pro SP3. No other AV. Never had this issue until the last few days. Have not installed anything during tha time. So, should I be expecting actual current updates as posted on the ESET site?
Both PCs did update - one was 3 days behind. Neither would update manually. Patience is not a problem. This only came to my attention because the v 2.7 was clearly not current and manual update insisted that it was. Since I am in Hawaii, perhaps the ESET servers which I connect with are busier at the times I am checking. Easy enough to practice patience. Thank you for your responses.
V2 uses larger update files so if a large update is released it may take some time until it's downloaded by all v2 users. I'd strongly recommend upgrading to v. 4.0.437 or 3.0.684 at least. You may want to apply for a trial license of ESS which you can also use to download and update the full version of EAV for 1 month.
I've seen this happen before as well. It happens with both 2.7 and 4. At first I thought it was a problem with the install and have tried uninstalling and reinstalling, which sometimes fixes it, but not always. I think what happens is that if the Eset servers are too busy, instead of giving an error that it can't connect to the server, NOD32 incorrectly states that it is up to date (even though I've seen it happen on new installs when the definition is months behind.) The only solution I've found is to click "update" repeatedly, sometimes 20 or 30 times until it finally decides to do an update. I've seen this happen on a lot of different machines but I've never seen a common thread between them other than having NOD32 installed. T
If you're a registered user with v3/v4 installed, updates should very rarely be downloaded after several attempts. If you're having such problems with update, contact customer care and provide them your program configuration as well as your username and password (should be included by default when you submit a request using the in-built support form).
My concerns are satisfied by knowing that others have had similar experiences. Honestly, if NOD32 did not respond by saying the database was current [when it is clearly at least slightly out-of-date], I think there would be no issue. The sometimes misleading response is the vexing issue, not any minor delay in the actual update.
I'll try that next time, but generally I'm in a bit of a rush, and can't wait the 48 hours it takes to hear back from customer service. T
