Jump to content

Eta76

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Eta76

  1. Ah... I edited my post, while you were replying...

    Marcos Posted 13 minutes ago ·

    Edit-----

    Be aware the installer is installing 10.1.204.0. And when the software connects to the internet, it detects it can directly upgrade to 10.1.207.0, which fails

    So when the next installer with 10.1.207.0 in it gets released, I would not have ran into this problem.

    Until the next driver update, which would then still fail :-)

    But I understand the new installer will fix this

     

    Edited 10 minutes ago by Eta76

  2. The clean install only installs 10.2.204.0, the first internet check, downloads and upgrades to 10.1.207.0

    it was not in this folder I checked multiple times. The .inf file was in C:\Windows\System32\DriverStore\FileRepository\ did was from the older version. But I could not find the eamonm.sys file. Maybe it is compressed in some other location.

    For now my problem seems to be solved. Thanks

  3. @Marcos I had re installed multiple times, InternetSecurity, SmartSecurityPremium, and I also got a download link to SmartSecurity (normal non-premium).

    You are correct my temp folder is located on another SSD.

    Completely removing all data and oem*.inf data did not work.

    For some reason Windows kept installing an older eamonm.sys, I tried searching for a DriverCache/DriverStore/Repository/.. But I couldnt find the location, from which the older driver was retrieved.

    I got a working solution based on this one:

     

    Which suggests to reboot in safe mode, then I could rename the eamonm.sys to _eamonm.sys and place the new version (found in C:\Program Files\ESET\ESET Security\Drivers\eamonm) in the system32\drivers folder: 

    I now have a 10.1.207.0 version installed of the eamonm.sys and it seem to work correctly.

    I hope the upgrade/installer gets fixed before the next driver modification.

     

    Edit-----

    Be aware the installer is installing 10.1.204.0. And when the software connects to the internet, it detects it can directly upgrade to 10.1.207.0, which fails

    So when the next installer with 10.1.207.0 in it gets released, I would not have ran into this problem.

    Until the next driver update, which would then still fail :-)

    But I understand the new installer will fix this

     

×
×
  • Create New...