Samoréen 8 Posted September 1, 2016 Share Posted September 1, 2016 Hi, Even after returning to version 9.0.386 after the problematic 9.0.402 update, I'm still getting the following messages in the log: 01/09/2016 23:23:37;Personal firewall;An error occurred during installation of the epfwwfpr driver.;01/09/2016 23:23:36;File-system filter;An error occurred during installation of the eamonm driver.;NT AUTHORITY\SYSTEM What does this mean ? There's no Personal Firewall in ESET NOD32 or am I that blind ? I'm not running Eset Smart Security and never installed it, even as a trial. It seems that there's some kind of mix-up here. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,298 Posted September 2, 2016 Administrators Share Posted September 2, 2016 There's a part of the firewall included in EAV too which is responsible for protocol filtering. I'd suggest running the uninstall tool in safe mode and installing 9.0.386 from scratch. However, there can be a system problem (e.g. with incorrect registry permissions) which could prevent EAV from installing the epfwwfpr driver. It'd require further investigation if installing it from scratch doesn't make any difference. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted September 2, 2016 Author Share Posted September 2, 2016 Marcos, Could you please tell me which registry permissions I should check ? I'm a system engineer / software developer and I can deal with such things. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted September 2, 2016 Author Share Posted September 2, 2016 OK. I have fixed the installation problem for epfwwfpr by installing it manually from the command line which seems to demonstrate that I didn't have a permission problem. If I can install manually while ESET itself cannot install, the problem is elsewhere. However, I still cannot install the eamonm driver . Link to comment Share on other sites More sharing options...
Samoréen 8 Posted September 2, 2016 Author Share Posted September 2, 2016 OK. Continuing helping myself... I could install the eamonm.sys driver in safe mode. So it's not a permission problem either. No more errors in the ESET log files but I'm afraid they will come back with the next updates if the problem is not fixed meanwhile. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,298 Posted September 2, 2016 Administrators Share Posted September 2, 2016 Drivers are installed by the operating system. If you are able to reproduce it with a clean install, it'd be great if you could generate a log with Process monitor during the install. Link to comment Share on other sites More sharing options...
Recommended Posts