Eta76

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

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

I did a safe mode reboot, I couldnot replace the driver, but I could rename the file to _eamonm.sys Then I could place the new file next to the _eamonm.sys and reboot. My system is working for now! Thanks for the hint. I still have no clue where the older eamonm.sys file is coming from....

@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

same problem here. For some reason it keeps installing older versions of the required drivers: C:\Windows\System32\drivers\ 09/03/2017 - version 10.1.3.0 eamonm.sys edevmon.sys eelam.sys ehdrv.sys ekbdflt.sys epfw.sys epfwwfp.sys

Same problem here. Repair of installed ESET Internet security is working. When downloading a new installer, it also installs 10.1.204.0, so maybe the 10.2.210.0 is not completely released yet? Since this ticket is started 2 weeks ago, I would have expected a fix :-)