Samoréen
-
Posts
257 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Samoréen
-
-
Still the same old story...
I just installed 10.1.204.0 manually (because 10.0.390.0 still said "up-to-date") and again I had to reboot in Safe Mode, install the above mentioned drivers manually and then reboot.
I have reported this last year and now, I'd really like to have information about the possible reasons for which these drivers do not install correctly in "normal" mode.
Running Windows 10 Pro 64-bit 1511.
-
Hi,
My copy is 10.0.390.0 and it is still saying "up-to-date".
Any advice ?
Thanks.
-
To be more accurate :
Windows 10 Pro 64-bit 1511.
-
Hi,
Not for me. Version 10.0.390 of ESET NOD32 antivirus still says "up to date".
-
Hi AndreyT,
Please have a look at this topic :
This solution applies to more recent versions. A fix would be preferable, though.
-
55 minutes ago, cyberhash said:
I'm the same as yourself, the eelam.sys driver was NOT updated along with the 386 upgrade, but all the other sys files were. File version just shows 10.0.0.0
Same here with Windows 10 Ultimate x64 1511.
-
5 hours ago, Marcos said:
I don't understand. It's not an issue those records in the log as it seems to be how ELAM works according to our investigation. Don't see problems where there aren't any
Marcos,
You should understand this : I'm facing a problem that shows up with every release since 9.0.402 and that forces me to manually install some ESET drivers in safe mode in order to get the product working normally (see other thread about that). I'm slowly getting tired of this. I never got any explanation about this issue and no indication about what I should check in my system (beside your suggestion about WMI). I didn't write the installation program and I'm looking for a possible cause of the installation failure for these drivers. Now I discover this strange behavior of the eelam driver. I'm trying to understand what's going on and I'm wondering whether this could be related to the installation problem.
-
On 04/11/2016 at 6:38 PM, Marcos said:
It is. As I wrote, we have figured out what is causing the issue and will prepare a workaround for this.
Currently, with version .386, the problem is still there, I'm afraid.
-
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
-
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.
-
Below, the warnings sent by Windows upon each reboot.
-
I'd like to test what happens if I reset all the settings to default values. How do I backup my current settings ?
-
Maybe a signature problem ? Why do I have to trust ecmd.exe ?
-
OK. But I'm wondering why this feature is applied when lists are populated. For example, List of Profiles, Excluded applications, Scan targets,... Such lists are here to be populated. So I think that marking them is not relevant.
Not a big deal anyway.
-
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'.
-
Hi,
What is the meaning of these blue bars and numbers on the left side of some settings ?
-
Windows Security status after I have enabled ESET NOD32. As stated above, this will be reset after the next reboot.
-
Shown below the Windows security status after each reboot. Setting ESET NOD32 ON fixes the problem for the current session only.
-
I'm running Windows 10 64-bit 1511.
-
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.
-
37 minutes ago, Marcos said:
Not all localized versions 10.0.385 are available yet. We'll update you by the beginning of the next week.
Thanks.
I'm using the English version. Is this considered as a localized version ?
-
Hi,
Check for Updates says that version 369 is up-to-date. Is something broken on my system or on the ESET server ?
Thanks.
-
Hi,
I'm unable to upgrade my Windows 10 to the Anniversary version and I'm always getting the following error :
0xC1900101 - 0x20017 "The installation failed in the SAFE_OS phase with an error during BOOT operation".
I have been told that this could be due to my AV locking or writing to the SRP (System Reserved Partition). Is it actually the case ?
Thanks in advance.
-
HIPS disabled after NOD32 update
in ESET NOD32 Antivirus
Posted · Edited by Samoréen
Diagnostic more accurate now
Hi,
I'm re-posting this issue with a title change since this problem is not version specific. It appeared with version 9.0.402 and is still there in version 10.1.204.0.
It seems to be Windows 10 specific.The problem seems to appear when your TMP/TEMP variables point to a non default folder
The problem :
After updating NOD32, the program tells you that your system is not protected. HIPS is disabled.as well as many features. NOD32 becomes totally useless. This is due to some drivers that could not be installed (see below).
My temporary fix :
Since the above mentioned drivers can be installed in safe mode (NOD32 not running) but not from an administrator account, it seems that NOD32 is shooting itself in the foot. Apparently, this is not a permission problem since only the installation of these particular drivers fails.
I didn't add C:\Program Files\ESET\ESET NOD32 Antivirus\Drivers to the exclusion list and I don't see any good reason to do that but who knows ? Just waiting for advice about that from the support or from the ESET reps on this forum. I didn't get much help since I reported this problem 9 months ago.