Tetranitrocubane 0 Posted September 20, 2018 Share Posted September 20, 2018 Hi All, Recently, ESET auto-updated its modules (just a few minutes ago). I'm currently on the latest version of Windows 10 (NOT in the insider program). I only noticed the modules were updated, because ESET started throwing errors. The following error popped up in the lower right of my screen: Afterward, ESET said to reboot, so I did. After rebooting, everything seemed fine, but ESET took a while to fully load. Then, once loaded, I noticed these errors in the Event log: Is this a problem? Is ESET working appropriate now, or is something broken? It appears to be functioning as expected, and isn't throwing any errors at me now. But if there were errors with driver installations, doesn't that mean ESET is just broken now? Any help would be greatly appreciated. Thanks much! Link to comment Share on other sites More sharing options...
Administrators Marcos 4,482 Posted September 20, 2018 Administrators Share Posted September 20, 2018 Please gather logs with ELC and provide me with the generated archive. I'd better check and make sure that you have the latest drivers properly installed. Should the issue occur again in the future, a Procmon log from upgrade will be needed. Link to comment Share on other sites More sharing options...
Tetranitrocubane 0 Posted September 20, 2018 Author Share Posted September 20, 2018 7 hours ago, Marcos said: Please gather logs with ESET Log Collector and provide me with the generated archive. I'd better check and make sure that you have the latest drivers properly installed. Should the issue occur again in the future, a Procmon log from upgrade will be needed. Thanks very much! I've sent along the ESET Log Collector logs in a private message. Any help you can provide would be greatly appreciated. Should it happen again, I'll do my best to collect a Procmon log for certain. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted September 20, 2018 Share Posted September 20, 2018 Hi, I had a similar problem in the past. This driver and 2 others wouldn't install during an update. I had found a temporary fix described here :https://forum.eset.com/topic/11967-hips-disabled-after-nod32-update/ Link to comment Share on other sites More sharing options...
itman 1,470 Posted September 20, 2018 Share Posted September 20, 2018 As far as I am aware of Eset's driver files are only replaced as a result of a product upgrade installation. Did an upgrade to version 11.0.63 for example occur on 9/19? Link to comment Share on other sites More sharing options...
Recommended Posts