How does 40.474 installation handle NOD32 signatures

Discussion in 'ESET NOD32 Antivirus' started by aapapapa, Dec 9, 2009.

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

    aapapapa Registered Member

    Oct 20, 2009
    Just updated NOD32 AV to 4.0.474 from the previous one.
    I didn't observe the date of signature file before this program update. So I can't say how was the date of signatures directly before this procedure. But I assume that was up to date - I didn't have probs with signature update.
    After the program update completed I could see the date of signatures was something like 20091122.
    Is this true?
    Does NOD32 AV installer really overwrite the installed signatures with those it brings along, regardless which of the both is newer?
    The logical strategy would be to leave untouched the signatures already present in NOD32 installation if this is up to date.
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Nov 5, 2007
    Lansing, Michigan
    The installer packages use the signatures they are bundled with and then immediately checks online for a signature or program component updates once the kernel starts up (though I do not think the GUI shows this).
  3. WayneP

    WayneP Support Specialist

    Apr 9, 2009

    SmackyTheFrog is correct about the software using the definitions that are packaged with it and then checking for updates once it is fully installed. Usually the program will pull the latest updates as soon as the install is finished but the GUI will not show this happening. You should have the latest definitions within a minute or so if the update info that you entered was correct.
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.