Samoréen 8 Posted January 15, 2017 Share Posted January 15, 2017 (edited) Hi, Now that I have updated ESET NOD32 to version 10.0.386, I have a new problem. After each boot, I systematically get a notification from Windows telling me that both Windows Defender and ESET NOD32 are disabled. See ESET2.JPG. ESET itself shows a warning ESET1.JPG. And the ESET user interface displays strange numbers along with each section name (ESET3.JPG). In the dialog box shown by ESET2.JPG, I set ESET NOD32 ON but after each reboot, the same mess starts again. This problem is new to version 10.0.386. Edited January 15, 2017 by Samoréen Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 I'm running Windows 10 64-bit 1511. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 Shown below the Windows security status after each reboot. Setting ESET NOD32 ON fixes the problem for the current session only. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 Windows Security status after I have enabled ESET NOD32. As stated above, this will be reset after the next reboot. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,071 Posted January 15, 2017 Administrators Share Posted January 15, 2017 Probably something's wrong with the WMI repository. You can try the following: 1, Run "ecmd.exe /registeravsoft" in the ESET install folder with elevated administrator rights and restart the computer. 2, Rebuild the WMI repository as per the instructions at https://blogs.technet.microsoft.com/askperf/2009/04/13/wmi-rebuilding-the-wmi-repository/ Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 The WMI rebuild didn't help. The WMI consistency check says "WMI repository is consistent". Anyway, I didn't have any problem with the previous version. This bug appeared just after installing version 386. Sigh! I miss the times when ESET NOD32 was an "install-and-forget" software. Times are a changin'. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 Maybe a signature problem ? Why do I have to trust ecmd.exe ? Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 I'd like to test what happens if I reset all the settings to default values. How do I backup my current settings ? Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 Below, the warnings sent by Windows upon each reboot. Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 15, 2017 Author Share Posted January 15, 2017 (edited) OK. Problem spotted after looking at the log files. This is a similar problem as the one described here : The cause is the same (Eset drivers not installed) but with different consequences. The fix is the same, though : This problem with these drivers that are not installed (epfwwfpr and eamonm) is not new. It appeared on my system with version 9.0.402 and now, I have to apply the fix after each release or update. I never got any help from the support about this issue. Edited January 15, 2017 by Samoréen Link to comment Share on other sites More sharing options...
Samoréen 8 Posted January 16, 2017 Author Share Posted January 16, 2017 Hi, The Event Viewer shows an error at ESET NOD32 installation time when trying to install eelam.sys. This driver is the only one that has a time stamp of 07-20-2016. Is it valid ? Should it be there ? Can it be the cause of the installation failure ? Thanks Link to comment Share on other sites More sharing options...
itman 1,659 Posted January 16, 2017 Share Posted January 16, 2017 7 hours ago, Samoréen said: Hi, The Event Viewer shows an error at ESET NOD32 installation time when trying to install eelam.sys. This driver is the only one that has a time stamp of 07-20-2016. Is it valid ? Should it be there ? Can it be the cause of the installation failure ? Thanks Eset uses the Win 10 Early Launch Antimalware driver i.e. ELAM. I just upgraded to Smart Security .386 and the Eset ELAM driver was not updated and shows the same date. I don't know of any reason why Eset would update its ELAM driver unless there was a change in the corresponding Win 10 ELAM driver. Link to comment Share on other sites More sharing options...
Recommended Posts