nod32 v4.0.437 - ehdrv.sys installation fails

Discussion in 'ESET NOD32 Antivirus' started by wlk, Aug 7, 2009.

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

    wlk Registered Member

    Joined:
    Aug 7, 2009
    Posts:
    2
    Hi,

    I'm keeping having installation failures during installation on Windows 2008 SP2 32 bits, with nod32 v4.0.437.

    ehdrv.sys installation always fails, and setup asks to reboot because a previous installation wasn't completed.

    I never had other antivus installed on this system, other than a previous v4 release, that have been uninstalled as it should have been.
    I did the safe mode boot, removed any traces of former drivers/programs as documented on ESet KB, also used the ESETUninstaller tool provided there (that does the same thing as I did manually).

    Enabling msi traces, I have this error in 'setupapi.app.log':

    and this one in 'setupapi.dev.log':

    Enabling the installer traces:

    ESETUninstaller.exe in safe mode log:


    Seems the driver won't register correctly, but I have no clue why (especially since it did successfully once in the past).
    Any help/advice/suggestion is welcome :)
     
    Last edited: Aug 7, 2009
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello,

    If you are having problems installing v4, then you should try running the Uninstaller utility again from Safe Mode and then installing v3. If it installs fine, then you should try upgrading to v4.
     
  3. tanstaafl

    tanstaafl Registered Member

    Joined:
    Apr 8, 2005
    Posts:
    207
    Actually, not sure why an ESET Moderator would say that...

    There are in fact a LOT of reported problems with v4 on servers...

    It is highly recommended that you stick with 3.0.684 on servers, and 4.0.437 on workstations.

    And be sure to add all of the Microsoft recommended exclusions - and have fun with that since ESET doesn't seem to care that not providing a simple way to do this by ticking a checkbox (that should be enabled by default at install time) really makes this a much more complicated and error-prone process than it needs to be.
     
  4. trencan

    trencan Eset Staff

    Joined:
    Nov 21, 2008
    Posts:
    120
    One thing is sure, Uninstaller didn't catch anything suspicious. Please check manually that there is no registry key HKLM\System\CurrentControlSet\Services\ehdrv before installation.

    Then you can try to delete cache file: c:\windows\inf\infcache.1 Sometimes this file gets corrupted what causes problems with driver installation. It's only cache for inf files, it will be recostructed by Windows at next driver installation.

    If still unsuccessful, you can try to run ProcMon utility while installing NOD and upload the log file here.

    And one more note, look at this:
    https://www.wilderssecurity.com/archive/index.php/t-233756.html
    "Problem solved in vista, nod32 4.0 is depended on "Base Filtering Engine" service, while 3.0 was not (and yes i had it disabled),"
     
  5. wlk

    wlk Registered Member

    Joined:
    Aug 7, 2009
    Posts:
    2
    You got it :thumb:

    My 'Base Filtering Engine' was set on manual and was not running.
    Installer could at least check and complain more clearly about that dependency.

    Thanks for the help.
     
Thread Status:
Not open for further replies.