Updating NOD32

Discussion in 'NOD32 version 2 Forum' started by DavidH, Feb 7, 2006.

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

    DavidH Registered Member

    Joined:
    Nov 1, 2002
    Posts:
    40
    Location:
    Fort Worth, TX USA
    Hello,

    Lately, I have been having trouble updating NOD32. As an example, my definitions currently read Feb 3. And of course, there are later definitions than that. I have had this problem twice (reinstall fixed it the first time) and noticed a pattern. NOD always seems to stop updating on a Friday, which happens to be the day that clean the registry, MRU, file system, etc. If I try a manual update, NOD acts like it is contacting the upgrade server. But, it never updates.

    I suspect the problem might be something that System Mechanic 6 is doing as I never noticed the problem before upgrading to that version.

    My question is, what file or registry key could possibly be involved here?
     
  2. pykko

    pykko Registered Member

    Joined:
    Apr 27, 2005
    Posts:
    2,236
    Location:
    Romania...and walking to heaven
    Well, David, just try reinstalling NOD32 but with a small difference.

    Uninstall and then delete the ESET folder under Program Files. Than install again. This might help you out. :)
     
  3. DavidH

    DavidH Registered Member

    Joined:
    Nov 1, 2002
    Posts:
    40
    Location:
    Fort Worth, TX USA
    Hi pykko,

    Thanks very much for the reply. I really do appreciate it. In fact, I have found a solution and part of it involves your advice. In the past when I tried reinstalling NOD32, I did it over the top of the existing installation and selected the option to keep the old settings. This was a mistake. Here is what I did tonight to solve the problem.

    1. Quit the NOD32 active monitor.

    2. Uninstalled NOD32 and restarted the computer.

    3. Deleted the ESET file folder. This was probably one of the key steps. Thanks again pykko.

    4. Used JV16 Power Tools to remove the ESET software entries from registry.

    5. Rebooted

    6. Reinstalled NOD32 and rebooted.

    7. When I attempted to update, I got an error concerning the TEMP and TMP Environment Variables. I did not get this error before. Perhaps my previous NOD settings somehow resulted in suppression of this error. I cannot be sure. Anyway, I checked the TEMP and TMP Environment Variables and found them to point to C:\Windows\Temp. After checking, I discovered that I did NOT have this directory. Perhaps it was deleted by the System Mechanic application. I will definitely check next time I use System Mechanic. Anyway, I manually created the Temp directory under C:\Windows and THAT FIXED IT.

    8. NOD32 now updates properly and properly shows the current virus database version.

    Anyway, your advice and also a short search of this NOD forum with regards to the TEMP and TMP Environment Variables helped me to solve this problem. I certainly won't forget what I learned in this case. Thanks again for your help.

    Have a good day. :)
     
  4. pykko

    pykko Registered Member

    Joined:
    Apr 27, 2005
    Posts:
    2,236
    Location:
    Romania...and walking to heaven
    It was my pleasure, David! Anytime I can help you and you have a problem I'm here! :D
     
Thread Status:
Not open for further replies.