NOD32 installer detects nonexistent Avast?

Discussion in 'ESET NOD32 Antivirus' started by hamble, Apr 27, 2008.

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

    hamble Registered Member

    Joined:
    Apr 27, 2008
    Posts:
    2
    Hi All,

    I have installed NOD32 on a number of systems with no problems whatsoever. Today, I was assisting a relative over the phone in upgrading NOD32 and ran into a new problem.

    He is a long time 2.7 user whose license just expired, so we decided to renew and install 3.0 at the same time on his Windows Vista Business system.

    We uninstalled 2.7 without issue and rebooted, and then purchased and downloaded NOD32 Antivirus 3.0.

    When running the installer for the first time it warned that Avast Antivirus was detected on the system.

    This user has never had anything but NOD32 on his system. I had him check his program files directory, and there was no trace of any Alwil/Avast folders, it was not in the start menu, nor was it in the list of installed programs that could be removed.

    No trace of Avast whatsoever, and this is not the type of user who would have ever installed it in the first place.

    So, the question: has anyone run into false detections like this in the NOD32 installer? Should I just proceed with the install, or is there something else I could have him check?

    Any advice would be appreciated.

    Thanks!
     
  2. The Hammer

    The Hammer Registered Member

    Joined:
    May 12, 2005
    Posts:
    5,619
    Location:
    Toronto Canada
    Iv'e never seen this when installing NOD. I am using the latest build of V3.
     
  3. proactivelover

    proactivelover Registered Member

    Joined:
    Apr 7, 2006
    Posts:
    840
    Location:
    Near Wilders Forums
    it's a known fp in v650 installer
    nothing to worry
     
  4. hamble

    hamble Registered Member

    Joined:
    Apr 27, 2008
    Posts:
    2
    Thanks. Is this just a Vista thing, or is there something in particular that's triggering the false positive?
     
  5. proactivelover

    proactivelover Registered Member

    Joined:
    Apr 7, 2006
    Posts:
    840
    Location:
    Near Wilders Forums
    i got this fp on winxpsp2
    i only download avast setup but donot install it
    must be fix in future installer
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Please export the HKLM\Software key to a file and send it to support[at]eset.com with this thread's url enclosed.
     
  7. proactivelover

    proactivelover Registered Member

    Joined:
    Apr 7, 2006
    Posts:
    840
    Location:
    Near Wilders Forums
    ohh sorry i forgot i run the avast setup but did not install it
    v650 installer pick this reg key
     

    Attached Files:

    • df.jpg
      df.jpg
      File size:
      11.9 KB
      Views:
      1,223
  8. coolboi007

    coolboi007 Registered Member

    Joined:
    May 16, 2008
    Posts:
    2
    Got the same situation here. I extracted avast, but i did not install it. nod 32 detected the avast software. so what will i do to remove Avast? shall i simply delete the registry entry? or is there a right process? thanks.
     
  9. GAN

    GAN Registered Member

    Joined:
    Mar 3, 2007
    Posts:
    355
    In case avast is not installed just delete the key.
     
  10. vlk

    vlk AV Expert

    Joined:
    Dec 26, 2002
    Posts:
    618
  11. coolboi007

    coolboi007 Registered Member

    Joined:
    May 16, 2008
    Posts:
    2
    so there's an avast Uninstall program... just like norton... anyway, thanks:D
     
  12. rpremuz

    rpremuz Registered Member

    Joined:
    Jan 18, 2005
    Posts:
    100
    Location:
    Croatia
    I also had this issue when installing ESET NOD32 Antivirus 3.0 Business Edition for Win XP/2000/2003/Vista ver. 3.0.672 downloaded from http://www.eset.com/download/business.php

    I created an installation package in ERA Console and tried to do push the installation. On many computers the installation was not successful.

    After trying the installation manually, the "Avast detected" message appeared. So it seems that this issue is still present in installer for NOD32 AV ver. 3.0.672.

    The log written to the einstaller.log file was not very helpful for solving this as it contained only the following:

    [2008-10-30 14:10:46.772] Status 1, ID 21: ESET Installer (2.0.110) is preparing to install.
    [2008-10-30 14:10:46.772] Status 1, ID 23: ESET Installer is trying to connect to 'myserver:2224'.
    [2008-10-30 14:10:46.803] Status 1, ID 25: ESET Installer is creating a temporary file.
    [2008-10-30 14:10:46.803] Status 1, ID 27: ESET Installer is downloading an installation package 'NOD32 Antivirus 3.0 BE for Win 2000-XP-2003-Vista' from server 'myserver:2224'.
    [2008-10-30 14:10:50.990] Status 1, ID 8: ESET Installer is preparing to install the package.
    [2008-10-30 14:10:50.990] Status 1, ID 92: ESET Installer is installing the package.
    [2008-10-30 14:11:07.490] Status 1, ID 93: Installation package launch finished.
    [2008-10-30 14:11:07.490] Status 1, ID 96: ESET Installer is trying to reconnect to 'myserver:2224'.
    [2008-10-30 14:11:07.506] Status 1, ID 94: Reconnected to 'myserver:2224'.
    [2008-10-30 14:11:07.506] Status 1012, ID 90: Failure during the package install - exit code: 1603, description: Fatal error during installation.
    [2008-10-30 14:11:07.834] Status 20006, ID 105: Service stuff cleanup finished with return code 0.

    The solution was to remove the "HKLM\SOFTWARE\Alwil\Avast" key from the system registry (the key existed although the Avast was not installed actually).

    -- rpr.
     
Thread Status:
Not open for further replies.