NOD32v4.0.474 Installation Questions

Discussion in 'ESET NOD32 Antivirus' started by rnfolsom, Jan 10, 2010.

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

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    The announcement of NOD32 AV v4.0.474 says that "You can download the new build from the download page and install it over the current version."

    1) If I do that, do I first disable (or do something else) real time file system and antivirus and antispyware protection?

    2) And should I be connected to the internet, or not connected?

    Thanks for any help.

    Roger Folsom
     
    Last edited: Jan 12, 2010
  2. nikanthpromod

    nikanthpromod Registered Member

    Joined:
    Oct 9, 2009
    Posts:
    1,369
    Location:
    India
    Dont do anything . Just install that new version .
    Internet connection is not needed at that time. U have to restart ur computer after installing.
     
  3. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    You may install a new build over a previous build provided that it is of the same build version family, v4.0 etc.
    If all applies to the above, you will be prompted during a custom installation to maintain current settings, otherwise the installer will override any personalised customisations done to the previous installation.
    Or in the event you have not succeeded in maintaining your current settings.
    Export my ESET security product settings to an .xml file

    You should not be connected to the Internet while doing this as your AV is in a state of flux where it is not completely functioning.

    A reboot will require the services process to complete and the virus database to be brought back to current status once you go back online.
     
    Last edited: Jan 11, 2010
  4. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,770
    Location:
    Texas
    Export your current settings, if you have changed them, to a file so you can import them to the latest version if need be.
     

    Attached Files:

  5. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    Installation over the old version is supported (you dont need to disable anything), you can also choose normal (typical) installation instead of custom. The installer will detect all current settings and will display them for you to alter or continue using the same settings.

    Of course, making a back-up of the current settings file is recommended as ronjor pointed out.
     
  6. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Thanks to everyone:
    nikanthpromod, siljaline, ronjor, and Brambb.

    I definitely needed the confirmations that installations of new builds (but not of new versions, e.g. 4.2 when it comes out of Beta) "over the current installation" can work,
    and the clarifications that I can save my current settings by using a custom installation and then following the prompt to maintain current settings, or that I can use a normal (aka typical) installation so that the installer reviews all current settings and allows me to make changes.

    Also useful were the reminders to make a backup-export of my current settings, and to be disconnected from the internet when exporting or importing settings and also when doing the installation.

    Previously I had wondered whether I could use exports and imports to copy settings from my computer to to my wife's computer, or whether exports had some unique characteristic that would make a mess if imported onto another computer, even if they had the same operating system (as my wife's and my computers do). For my last NOD32 upgrade on my wife's computer (so that her's would match mine) I redid her settings manually. This time, knowing I can use exports and imports will be an enormous time saver.

    Thanks again, everyone.

    Roger Folsom
     
  7. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Happy to have assisted you in a positive way where you got the answers that you needed to allow you to get on with your day.

    Best regards,
     
  8. jimbobaloo

    jimbobaloo Registered Member

    Joined:
    Jan 18, 2004
    Posts:
    11
    Location:
    Michigan, USA
    I beg to differ with you on this. You can install a new build or even a new version over the the existing one as the installer will uninstall the previous one and can keep your settings and user name and password. I have done this since ver 2.7 and have seen no issues whatsoever.;)
     
  9. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Why don't we agree to disagree, then we are both happy.
    If whatever tweaks you use to do this, that is fine but not necessarily for public consumption.
     
  10. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    SUMMARY: INSTALLATION OF A NEW BUILD ON TOP OF THE CURRENT BUILD
    A Somewhat Enhanced Summary of the information in this thread --- excluding the experience of jimbobaloo in thread message 8.

    To anyone reading this: Please advise me if I am wrong about either a) or b) below.

    a) For an upgrade from a 4.0 build to a 4.2 build (as distinguished from a more massive upgrade from version 4.x to 5.x), Eset would recommend uninstalling the 4.0 build first.

    b) Anything else where my wording may be wrong or at least misleading.

    Roger Folsom

    P.S. For the record, I have successfully installed NOD32 AV 4.0.474 on top of 4.0.467, retaining my 4.0.467 settings.

    ----------------------------------------------------------------

    INSTALLATION OF A NEW BUILD ON TOP OF THE CURRENT BUILD

    As stated above in this thread (aside from jimbobaloo's less conservative experience described in his message :cool:, installations of major new versions (e.g. from version 2.w or 3.w to 4.x, or from 4.0.y to 4.2.z) do require uninstalling the current version first. At least, that's Eset's recommendation, at http://kb.eset.com/esetkb/index?page=content&id=SOLN2116.

    However, installations of new builds of the current version (e.g. from version 4.0.467 to 4.0.474) do not require uninstalling the current version first (although uninstalling the current version first won't cause problems). As a convenience, the new build can be installed "on top of" the currently installed build.

    To install a new build on top of the currently installed build:

    1. Download and save the new build's installation (.msi) file.

    2. Restart the computer into the Administrator account.

    3. Disconnect the computer from the internet.

    4. On the ESET main screen, select Setup, Import and export settings, and export the current settings to a backup XML file. (These settings can then be imported on the same computer, or on a different computer that has the same NOD32 version and build.)

    5. Double-click the new build's installation (.msi) file.

    6. To continue using the current build's settings, check the "Use Current Settings" box, and then follow the prompts to continue the installation and maintain current settings.
    OR:
    To review and possibly change the current installation's settings, UNcheck the "Use Current Settings" box, and in the dialog box's Installation Mode section, select either
    "Typical (recommended best settings)" or
    "Custom (allows for more detailed configuration)."

    7. After the installation is complete, restart the computer.

    8. Reconnect the computer to the internet, and check for signature updates.
     
  11. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    ESET Announces Plan to Discontinue NOD32 Antivirus 2.7, so that would be moot.
     
  12. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Roger,
    I have asked an ESET Moderator to reply to your last query as it is beyond my depth of knowledge of the product.
     
  13. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Generally speaking, that will work, however, performing a clean install gives you the opportunity to not just review any new options in the new version, but changes to options that were available in the previous version.

    Regards,

    Aryeh Goretsky

     
  14. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Mr. Goretsky:

    I'm very confused here: What do you mean by "that"?

    I would think that your "that" referred to jimbobaloo's message #8, given that you quoted it:
    But on the other hand, the message immediately preceding your post was:
    Is it possible that you were that ESET Moderator, and that your "that" means my attempt, in message #10, to summarize when to install a new build on top of an old build, and how to do it?

    After all, in the announcement "ESET NOD32 Antivirus 4.0.474.0 released" thread (https://www.wilderssecurity.com/showthread.php?t=259044) it was your message #2 <grin> that included the statement "The new builds . . . can be installed over a previously-installed version," thereby inspiring this entire thread.

    Presumably, if a new version's first number changes (e.g. from 3.w to 4.x), that's a major upgrade for which you would recommend uninstalling the old version before uninstalling the new one: a clean install of the new version. And siljaline's message #3 implicitly says that even if the first number does not change, a different first decimal number (e.g. from 4.0 to 4.1 or 4.2) also needs a clean install.

    But is it really true that if the initial and first decimal number do not change, i.e. if only the build number changes, that installing the new build "on top of" any previous build (same 4.n) always is appropriate?

    In short, I (and perhaps also siljaline and others) would like to know whether my message #10 needs revision.

    For example, given your post's point that a clean install allows reviewing and changing new settings not in the old build, my message #10's implicit assumption that a mere build upgrade (e.g. 4.0.467 to 4.0.474) never would contain new settings may be wrong.

    Maybe, when deciding whether a clean install is needed, users need to rely on whatever the announcement recommends. If so, an announcement of any new versions should remember (as your message #2 did) to include a "clean install" vs "on top of" recommendation.

    In other words, perhaps users need to follow Knowledge Base Solutions ID: SOLN2116 (http://kb.eset.com/esetkb/index?page=content&id=SOLN2116)
    unless the new version announcement explicitly suggests an "on top of" installation.

    Since my message #10 is trying to fill a documentation gap that comes up almost every time ESET issues a new major version or merely a new build, I'd like it to be accurate.

    Thanks for any improvements you can suggest, not only about the clean vs "on top of" install, but also about my "on top of" installation steps.

    Cordially, Roger Folsom
     
    Last edited: Jan 17, 2010
  15. jimwillsher

    jimwillsher Registered Member

    Joined:
    Mar 4, 2009
    Posts:
    668
    Using ERAC, I pushed out 4.0.x to nearly 100 3.0.x clients and they all upgraded successfully. So I think the statement regarding "same build version family" is perhaps incorrect. I'm sure it's probably cleaner to uninstall 3 before installing 4, but in our case all 90+ clients upgraded successfully without uninstalling 3.x on any of them.



    Jim
     
  16. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Jim Willsher

    Thanks for that input. You are not alone with such successful experiences. E.g. jimbobaloo in message #9. And if Mr. Goretsky was in fact replying to jimbobaloo rather than to me, that's further support for the idea that it's not necessary (although may be useful, as in Mr. Goretsky's example) to uninstall any previous version of NOD32 before installing a later version.

    Roger Folsom

    P.S. I was curious about what ERAC meant, so I asked Google to define it. The definition that came back was:
    "Formed in 2003, a partnership of BC school districts to generate financial savings on the evaluation and aggregated purchase of software, video ..."

    I'm guessing you had some other meaning in mind? Or maybe you were distributing 4.0.x to a number of schools?

    I know you are busy, no need to reply to this curiosity bump of mine (aka I'm being nosy).
     
  17. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    ERA (ERAC/ERAS) = Eset Remote Administration (Console/Server)

    Just like jimwillsher I also updated numerous of V4 clients over the top. Even did a few installations from V3 to V4, all with succes. But as said, its was always suported but not recommended as a clean installation is less tricky to perform.
     
  18. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Apologies for my imprecise language. Allow me to re-express myself:

    Generally speaking, installing a new build of the software (i.e., going from 4.x.y to 4.x.z) or new version of the software (i.e., going from 3.x to 4.x) will work, however, performing a clean install gives you the opportunity to not just review any new options in the new version, but changes to options that were available in the previous version. ​
    The idea is that while one can simply install a new version over an older version, it may not always be desirable to do so, since there are small changes to settings one may wish to review first instead of continuing to use the options the previously-installed version.

    Regards,

    Aryeh Goretsky


     
  19. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Branbb:

    Thanks for your response, and for the explanation of
    > ERA (ERAC/ERAS) = Eset Remote Administration (Console/Server) <

    Roger Folsom
     
  20. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Aryeh Goretsky:

    Thanks, very much, for the clarifications.

    I do hope that future announcements of new builds will do what you have done in this case (in your message #2 in the .474 announcement, plus your message #13 here):
    1) Mention that the user can install a new build or a new version over an earlier build or versions (unless in some particular case doing so would likely create a real mess), but also
    2) Note that installing on top of a previous version "may not always be desirable . . . since [with new versions] there are small changes to settings one may wish to review first instead of continuing to use the options the previously-installed version."

    I'm assuming that a new version has a new initial number and/or a new first decimal, but that builds are always denoted by a change after the second decimal.

    Thanks again.

    Roger Folsom
     
  21. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Your feedback has been noted.

    ESET currently uses the following versioning schema on ESET Smart Security and ESET NOD32 Antivirus:

    {major version number}•{minor version number}•{build number}•{trivial version number}

    Here is a quick explanation of how these can be interpreted:

    {major version number} - denotes a particular generation of a code base, i.e., v2.x, v3.x, v4.x

    {minor version number} - denotes a particular level within a particular generation of a code base, i.e., v2.70, v3.0, v4.2

    {build version number} - denotes a particular release within a particular level of a particular generation of a code base, i.e. v2.70.39, v3.0.694, v4.0.474

    {trivial version number} - denotes a trivial change to a particular release within a particular level of a particular generation of a code base, i.e., v4.0.474.0, v4.0.474.6, v4.0.474.10

    The trivial version number has not been used as often by ESET, but does get updated from time to time when a release is made for a reasons other than adding or improving features, or fixing bugs in the engine. Examples of things which have generated a release with a trivial version number include address changes for a distributor, updates to language in the EULA, translation fixes, trial mechanism fixes and so forth.

    Please keep in mind this is a very rough explanation, and there may be times when these conventions are not followed for various internal reasons.

    Regards,

    Aryeh Goretsky
     
  22. rnfolsom

    rnfolsom Registered Member

    Joined:
    Nov 9, 2005
    Posts:
    247
    Location:
    Monterey, California
    Mr. Goretsky:

    It took me awhile to get back to this, but I very much appreciate your summary of ESET's system for version numbers.

    Thank you very much.

    Roger Folsom
     
Thread Status:
Not open for further replies.