Samoréen

Hi, After installation of the 111.4.472 Dropbox update, you get the following message from he Dropbox app if you are using Eset NOD32 : "Cannot establish secure internet connection". The fix is as follows : - Open the ESET configuration panel - Hit F5 to go to the Advanced settings - Go to Web and Email | Protocol filtering - If protocol filtering is enabled, exclude both Dropbox.exe and DropboxUpdate.exe - Restart the system I never had to do this before this new release.

OK. Meanwhile I have seen that the site returns a SEC_ERROR_REVOKED_CERTIFICATE error. So the problem is on the server's side. Sorry.

Hi, Both domains are unduly blocked since yesterday. Pausing ESET protection doesn't allow access. The sites are blocked anyway when Web access protection is disabled. I don't understand.

https://www.ghacks.net/2019/04/11/oh-look-another-broken-windows-update-kb4493472-and-kb4493446-causing-issues/ Thanks.

Hi, I have switched to Outlook 2019 a few days ago and since then, I have not experienced duplicate messages after re-enabling "Integrate into Microsoft Outlook" and all the scan options except "Sent email". Keeping fingers crossed...

Checking upon inbox change and scanning of read email are already disabled. Only scanning of received email is enabled. So, to summarize : - If I enable the Outlook client plugin, I get duplicate emails. - If I disable all client plugins but leave "Enable email protection by client plugins" checked, I get the warnings about my system being at risk. - If I uncheck "Enable email protection by client plugins", ESET is quiet but I have no protection. I'm living with this problem since five years so I guess I can wait for a new version of the plugin (provided it will work with Outlook 2010). All my emails are now going through my Fastmail account before landing in my Outlook inbox. So I guess I will now rely on Fastmail for virus checking and disable this feature in ESET.

Hi, https://forum.eset.com/topic/1917-duplicate-emails-in-outlook/ This problem has been reported in 2014. I have provided a lot of log files and the french support has acknowledged the problem, then closed the ticket. Problem still here 5 years later. If the developers are unable to fix this issue, I'd like to disable ESET integration into Outlook without getting those warning messages stating that my system is at risk. Currently, if I disable integration for all email clients, I get the attached warning. This doesn't make sense. Either I get duplicate messages or I get useless warnings. Please allow me to get rid of this.

Hi, No problem today. I'm wondering what could cause this strange behavior for a few days. I'm not aware of any change in my system.

Exactly. However, I had to reboot my system this afternoon and the problem didn't re-appear. Don't ask me why. Let's see what will happen tomorrow... Thanks.

Hi, I'm not talking about the splash screen which I have disabled. Usually, the Eset window doesn't open upon startup. I just have the icon in the system tray. Since a few days, the Eset window is showing upon startup and remains open. I don't see any option for controlling this. I have looked at the command line in the registry : "C:\Program Files\ESET\ESET Security\ecmds.exe" /launch /hide which seems to be OK. Any clue ? Thanks.

Hi, This new thread refers to this archived one : https://forum.eset.com/topic/15480-error-when-applying-differential-update/?page=1 The release notes for version 12.0.31.0 say : ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 12.0.31.0 have been released and are available to download. Changelog: Fixed: After upgrade, "Modules update failed: Invalid digital signature" error ... So, after spending all this time looking for a problem on my system (this could allegedly not be a problem with the software itself), it was eventually a bug ? What a loss of time !

Problem apparently fixed. Thanks for the quick answer.

Hi, Today, ESET has started filtering genuine.adobe.com which is used by adobegcclient.exe , a legitimate program. I have added the IP address to the exception list but this is not correct. An old problem showing up again...

Since several workarounds have been suggested, I suggest that you try the driver re-installation first (if any event in the log is mentioning a driver installation failure - otherwise just forget it). It's faster than uninstalling/re-installing.

Rudolph, Something you could try : go to Tools | Log Files | Events and check whether there's a notification about failed installation of some drivers. If this is the case, navigate to this page and follow the instructions in order to re-install the drivers which failed to install.

Peter, The only difference with other sensitive files that I can think of is the way these files are following to reach my PC. I agree with Itman's statements but I'm sure I have downloaded a lot of files that would have been rejected if they were corrupted. Well, we are now aware that the problem was due to some corruption caused by an SNR value on my DSL line that was too low. What we don't know is what was actually corrupted. Referring to a message from Itman at the beginning of this thread : Eset modules use a code signed Eset certificate. This cert. is not stored in Windows root CA store. As such, cert. "pinning" path to root CA issuer must be validated via Internet connection. If this chain validation lookup is blocked locally, Eset certificate validation will fail. So maybe the files themselves were not corrupted but something repeatedly went wrong during the exchange mentioned by Itman OR the firmware of my DSL box was not able to recover FEC errors (which are normally recoverable) during this exchange because of the SNR value. The exchanged data during the certificate validation could have a particular "signature" that caused the bug while other certificates are not affected. I guess we'll never know.

Additional information about this issue... The problem now appears to be clearly related to my DSL box settings. Quoting a previous message : As soon as I have tried to lower again the acceptable SNR value, the problem re-appeared within the next 24 hours. After setting it to a higher value, it was gone again. Now, I'm still wondering why this caused problems to ESET NOD32 updates only. I'm downloading a lot of files that have to be error free (images, Windows updates, installation files, etc.) and I never observed a file corruption or a failure due to a corrupted file. These downloads are too frequent to merely consider a coincidence. No idea about what could make ESET downloads specific.

And when the warning points to an Eset product, there's no way to decide that this warning is irrelevant ? I must admit that I have difficulties to understand this. Granted, this is apparently Google code only but you said "we warn". If Eset was involved in this code, disabling irrelevant warnings should have been easy. I'm confused... OK, not a big deal as far as security is not compromised.

Or maybe it's because the problem had already been reported once to Google ?

Hi, There's definitely something I don't understand in this discussion. I'm using Eset NOD32, latest version. When I opened the Chrome settings a few minutes ago and activated the Cleanup Computer option, Chrome told me that I should remove Eset Endpoint because it's a harmful software. However, this Chrome module is obviously the result of a collaboration between Eset and Google. This inconsistency has certainly been observed during the development phase. It's almost the same as an Eset scan reporting Eset as a virus. So it shouldn't be a big issue to exclude Eset products from the list of "harmful software" that Chrome is possibly reporting. Now another inconsistency... The first time I ran the Cleanup Computer feature of Chrome, I had this odd message. The second time, after re-launching Chrome ( Version 69.0.3497.100 ), it told me "No harmful software found".

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/

OK. The problem didn't re-appear since more than one month. Nothing has changed on my system beside what's explained above. So there's a good chance that this was the problem - crossing my fingers - (although I still don't understand why only the ESET update files were affected).

I have understood that the tool must be running when the problem occurs. If the problem was related to my internet connection, it should not re-appear. If not, I will see it again one of these days and it will happen more than once. So if I see it again in the near future, I will activate all the available reporting tools and wait for the next failure. Re: disk failure If you re-read this thread, you'll see that I have done everything I could do to confirm or invalidate this possibility. For the moment, I exclude the idea that the 2 SSDs that are/were used to store the update files are having problems only with ESET update files.

Phil_S, It would be interesting to see whether we get these notifications for the same updates. They might be triggered at a different time (or date) but they can be identified by their version number. For example, the last one that failed for me was this one Time;Module;Event;User 08/08/2018 17:11:56;ESET Kernel;Detection Engine was successfully updated to version 17850 (20180808).;SYSTEM The above is the success notification after 2 failed attempts.

Hi Peter, The problem didn't re-appear since 12 days now. Meanwhile, I noticed that something had been changed (by my ISP) in the settings of my DSL box. The acceptable margin for the SNR (signal noise ratio) has been set to a higher value, which means that the box is now less tolerant to transmission errors. This could explain why the problem didn't show up since almost 2 weeks although I never had any file corruption problem with the previous settings (with exception of the ESET updates). I don't see why only the ESET update files should be corrupted. Maybe they go a specific route where some device between your servers and my PC is generating the problem. Anyway, I will download the tool and use it if the problem shows up again.