Unable to update definitions

Discussion in 'ESET NOD32 Antivirus' started by Carbonyl, Oct 6, 2010.

Thread Status:
Not open for further replies.
  1. Carbonyl

    Carbonyl Registered Member

    Joined:
    May 19, 2009
    Posts:
    256
    Hello.

    This morning I find that my version of NOD v4 is unable to update its definitions. The ESET Threatcenter shows that version 5509 are available, but my installed NOD is showing 5507 as the currently installed definitions version. Attempts to manually update result in a message that an update is not necessary - that version 5507 is the most current version. I know this isn't correct.

    I've attempted to clear the cache as is described in the knowledge base. But this still results in NOD telling me that the updates are current at 5507.

    Can anyone please advise? Thank you.
     
  2. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    I had a customer with this very problem - they were stuck on 5460 I think - their version of ESET was 3.0 - installation of 4.2 did not fix the problem.

    I had to remove ESET antivirus - did a safe-mode startup - ran the ESET removal tool - manually deleted the ESET folders from the machine, then installed the latest 4.2 - this got them up and running again. It was very odd.
     
  3. Carbonyl

    Carbonyl Registered Member

    Joined:
    May 19, 2009
    Posts:
    256
    That is quite peculiar. I'll keep that in mind if I get to the point where I'm unable to update for a long while.

    I just started up my OS X machine, which is currently running the latest Beta of ESET cybersecurity. The same problem is persisting on that machine, despite the difference in physical hardware and operating system. My OS X machine is stuck on version 5506.

    Both computers continue to say that an update is unnecessary, and that definitions are current. I would be inclined to call this a server-side issue, given that two machines both developed the same problem simultaneously, but if it were server side I would expect a different error. Apparently the server can be contacted, but in both cases returns that no updates are necessary? I'm not sure. I'd at least expect the OS X machine to update to 5507 if that were the case.
     
  4. metalalbert

    metalalbert Registered Member

    Joined:
    May 22, 2008
    Posts:
    46
    I have the same problem. I can not update.

    I installed 4.2 and now I'm stuck with very old updates.

    Fix this please!
     
  5. metalalbert

    metalalbert Registered Member

    Joined:
    May 22, 2008
    Posts:
    46
    UPDATE: NOD32 4.2 just updated. Guess this was a server side issue at ESET?
     
Thread Status:
Not open for further replies.