Is this a bug for v2.51.20?

Discussion in 'NOD32 version 2 Forum' started by Red Dawn, Mar 8, 2006.

Thread Status:
Not open for further replies.
  1. Red Dawn

    Red Dawn Registered Member

    Joined:
    Jun 28, 2004
    Posts:
    116
    I recently updated my version of NOD from 2.50.45 to version 2.51.20. No problems with the install or the like. I did notice though, that it won't update without manually choosing a update server for it. I have it setup to update automatically, like everyone else here I believe, and to choose a server automatically.. But I noticed it stayed with the same virus signiture that it had from the day I updated the software, when I would click update now, it would say my version was up to date. Came on the forums, noticed an update for today, went back, click the update now button, same thing, I get told my version is up to date. I then manually choose server: u3.eset.com, click update now, and I get the update for today, so what gives? Is this a bug or something?
     
  2. Lollan

    Lollan Registered Member

    Joined:
    Feb 2, 2006
    Posts:
    288
    Isn't 2.51 the 64 bit version?
     
  3. Red Dawn

    Red Dawn Registered Member

    Joined:
    Jun 28, 2004
    Posts:
    116
    32 and 64 bit version actually....
     
  4. shanijee

    shanijee Registered Member

    Joined:
    Feb 1, 2006
    Posts:
    107
    Location:
    Faisalabad(Pakistan)
    i know the answer delete the folder updfiles in <>:\Program Files\ESET
    and delete these file nod32.003 in <>:\Program Files\ESET
    then click update
    it download new scan engine and updates
     
  5. Red Dawn

    Red Dawn Registered Member

    Joined:
    Jun 28, 2004
    Posts:
    116
    Gives me an error when I try to do that "Error writing to disk"....
     
  6. Benvan45

    Benvan45 Registered Member

    Joined:
    Jul 27, 2004
    Posts:
    556
    Could you explain here why one should do this? On what is this move based?
     
  7. shanijee

    shanijee Registered Member

    Joined:
    Feb 1, 2006
    Posts:
    107
    Location:
    Faisalabad(Pakistan)
    nothing happened when i delete these no error go to safe mode and then delete or delete
    these files
    D:\Program Files\ESET\updfiles\nod7CB0.nup (it is 3.25mb)
    D:\Program Files\ESET\nod32.000 (it is 3.78mb)
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374

    That's because you deleted the updfiles folder while you should have deleted just its contents.

    If it doesn't help, then your registry must have gotten screwed up somehow. If that's the case, I'd suggest to continue as follows:
    - make sure that no registry protection tool is active
    - download a NOD32 2.51.20 installer
    - uninstall NOD32
    - reboot the pc
    - delete the program files/eset folder
    - install NOD32 2.51.20
    - reboot the pc
    - update NOD32
     
  9. Red Dawn

    Red Dawn Registered Member

    Joined:
    Jun 28, 2004
    Posts:
    116
    I un-installed and rebooted, checked after reboot my registery, found that the Eset keys had not deleted, got rid of them, re-install and now it works fine. Thanks
     
  10. am23

    am23 Registered Member

    Joined:
    May 17, 2006
    Posts:
    1
    Hello, I am too having the same issue. I followed the directions above to delete the files and to uninstall, clean registry, then reinstall NOD32. However I am still having the "Update attempt failed. Error writting to disk.) error. Before, it was stuck on update on 05012006, now it's on the default after installation.

    is there any other way to correct this error? Thanks.
     
  11. ejr

    ejr Registered Member

    Joined:
    Nov 19, 2005
    Posts:
    538
    Is there a way to get the program version to update automatically? I have the most recent signatures, but am still running V2.50.45.

    Any major changes in the most recent version? Am I still adequately protected using 2.50.45?
     
  12. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    Check here for program update info: http://www.eset.com/support/news.php
    However I'm 100% sure you are protected.
     
  13. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    NOD32 2.50 is perfectly fine if it's fully updated. There's only very minor differences to 2.51 (except the installer also contains 64-bit versions) and no need to update unless you have experienced one of the minor issues that have been resolved in 2.51. Marcos has posted about these elsewhere (authenticating with a specific type of router/proxy configuration and that sort of thing). I'm sure you haven't got any of these issues or you would have known about it already, so relax and enjoy your 2.50 :)

    Cheers :)
     
  14. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    No, not in this case, as it is not a required update except under specific circumstances.

    Cheers :D
     
Thread Status:
Not open for further replies.