Do I always need to update to the lastes version?

Discussion in 'ESET NOD32 Antivirus' started by tuvi123, Jul 10, 2008.

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

    tuvi123 Registered Member

    Joined:
    Jun 20, 2008
    Posts:
    25
    Do I always need to update to the latest version?
    if I stay with 3.0.621 version and update it (update modules and signature updates)
    so will it be like 3.0.669 version?
    Do I always need to update to the latest version?
     
  2. Capp

    Capp Registered Member

    Joined:
    Oct 16, 2004
    Posts:
    2,125
    Location:
    United States
    It is not required. It is recommended when you are able to though, simply because the build updates contain fixes for bugs and tweaks to existing features. The product continues to get better and better through these updates.
    Updating to the newest build just ensures you have the most stable version available too, but its your decision. If you feel comfortable with the version you have installed and are not having any problems at all, then keep your current version. It's your decision :)
     
  3. tuvi123

    tuvi123 Registered Member

    Joined:
    Jun 20, 2008
    Posts:
    25
    1) So are you saying that ny version v3.0.642 (fully updated with modules and signature updates with eset u[dater) is lack of features/ fix for bugs

    2) Does the modules not suppose to update you to the latest tweaks and fixes?

    btw- sorry for my bad english.
     
  4. rothko

    rothko Registered Member

    Joined:
    Jan 12, 2005
    Posts:
    579
    Location:
    UK
    you can see what fixes,etc have been made since 3.0.642 in the changelog here
     
  5. Capp

    Capp Registered Member

    Joined:
    Oct 16, 2004
    Posts:
    2,125
    Location:
    United States
    1) No, i'm not saying yours is "lacking" anything. I currently have an old build on my systems as well simply because I haven't needed to upgrade yet. If yours is working and you are not having any problems, you don't have a need to upgrade right away. I did not mean that there are new features that you do not have.

    2) The module updates fix issues within the modules themselves and these do need to be updated, but you don't have to updated the actual program build right away unless you are having problems.

    See the first sticky post of the forums and they will tell you when new builds are available and what fixes were made in them. If they contain a fix for a problem you are having, then yes, get the newest version, but if not, keep what you have and just make sure it is up to date.


    No worries :)
     
  6. tuvi123

    tuvi123 Registered Member

    Joined:
    Jun 20, 2008
    Posts:
    25
    I did not understand what you are saying.
    can you be more specific?

    I heard that there is advantage of updateing to the latest build number.

    thank you.
     
  7. Capp

    Capp Registered Member

    Joined:
    Oct 16, 2004
    Posts:
    2,125
    Location:
    United States
    To put it another way, there is rarely any downsides to upgrading to the latest build. They do a lot of testing of the builds before they release them to the public, so you are safe to upgrade if you want to. But you don't have to if you don't want.

    About the module upgrades. if there is a Heuristics Module update, for example, it is generally to fix something within the heuristics specifically or make it run smoother and these do need to be updated, but its not going to be any major changes to the program itself. Make more sense?

    Those updates will be pushed out through the built-in update feature sooner than having the program update sent out itself.
     
  8. Bubba

    Bubba Updates Team

    Joined:
    Apr 15, 2002
    Posts:
    11,271
    As noted in the change log for the recent build .699, there was a quirk in the scheduler. This was not fixed by a module update but was fixed by a newer ekrn.exe file. That can be construed as an advantage for those experiencing the scheduler problem, which most were, some knowingly some un-knowingly.

    There have been other quirks that were fixed in past builds and they also were fixed with a new ekrn.exe file. Module updates would not have fixed those quirks.
     
Thread Status:
Not open for further replies.