Marcos

Please create a Procmon log during install. If install fails, provide the Procmon log (compressed in an archive) as well as logs gathered by ELC.

Since this forum is not a channel for disputing detections, we'll draw it to a close. For information how to report possible false positives to ESET, refer to the link above.

Does the issue affect both http and https websites? Does temporarily disabling protocol filtering make a difference? Please gather logs with ESET Log Collector and post the generated archive here.

I'd start off by checking C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html and trace.log on troublesome clients for possible errors.

We have received no reports of activation issues recently. Are you still getting this error?

We have offered help. Also uninstalling v12 and installing it from scratch would work. We assume that the issue must have been there since older non-GDPR compliant versions, ie. versions from before March 2018. We have already gathered stuff from a machine where the issue manifested and are analyzing it. Please let us know if you have the LiveGrid section empty in the advanced setup when the issue occurs. If anybody runs into this issue, the solution is to uninstall ESET and install v12 from scratch. If you use custom settings, export them prior to uninstalling ESET and import them after installing it from scratch.

Since the first fix concerns an issue with upgrade from v6 to v7 and you are already on v7, it's irrelevant for you. As for the other fix, it concerns Web Control. Again, if you don't experience any issues with it, it's not important to upgrade as soon as possible. Nevertheless, we encourage you to upgrade to newer versions of Endpoint on a regular basis since not all fixes and changes under the hood may be necessarily listed in the changelog.

Please clarify what product and version you have. Make sure that you have the latest version of ESET Internet Security v12 installed. Then check if temporarily pausing the firewall or disabling it completely in the advanced setup make a difference.

We'll need a Wireshark log with the network communication captured from time when the error "Failed to configure EPNS resource" is logged.

The machine cannot connect to epns.eset.com. Also make sure that a newer OS than Windows XP is installed.

I'd suggest uninstalling the following applications that use drivers and see if the issue goes away: "WinDivert1.3" = "c:\program files\freedownloadmanager.org\free download manager\windivert32.sys" "TuneUpUtilitiesDrv" = "c:\program files\avg\avg pc tuneup\tuneuputilitiesdriver32.sys" "SysInfoDetector" = "c:\windows\system32\sysinfodetector.sys" "AscRegistryFilter" = "c:\program files\iobit\advanced systemcare\drivers\win10_x86\ascregistryfilter.sys" "AscFileFilter" = "c:\program files\iobit\advanced systemcare\drivers\win10_x86\ascfilefilter.sys" If removing these applications doesn't make any difference, try renaming the following drivers in safe mode: "HDD Filter Driver" = "c:\windows\system32\drivers\sahdia32.sys" ; Disk Filter Driver ; Corel Corporation ; "Volume Filter Driver" = "c:\windows\system32\drivers\saibia32.sys" ; Disk Filter Driver ; Corel Corporation ; "PxHelp20" = "c:\windows\system32\drivers\pxhelp20.sys" ; Px Engine Device Driver for 32-bit Windows ; Corel Corporation ;

Please stay tuned, we'll update you very soon.

If you know your registration email address, enter it here and you should receive a license email within a few moments: https://www.eset.com/int/support/lost-license/. Otherwise contact the seller from whom you purchased your license.

Of course : ) It was just a typo.

IDS monitors all communication unless you specify exceptions. Exceptions should be defined only in case of false positives.

This is an example of how Fortinet corrupts files. In the left pane you can see data being replaces with zeroes: Usually at offset 1MB (including HTTP header), a 73-byte section is zeroed. This problem occurs with large files like em002_32_l0.dll.nup, em002_64_l0.dll.nup, em002_64_l1.dll.nup, em023_64_l0.dll.nup, em023_64_l1.dll.nup. Not sure if creating an exception will be enough, please try.

Unfortunately you didn't run ELC as an administrator and therefore a lot of logs are missing. Please gather fresh logs with ELC run as an administrator.

To start off, please gather logs with ELC and upload the generate archive here.

Please provide us with: - ELC logs (with a registry dump included) - a Process Monitor log created at the time you make the selection about the LiveGrid feedback system - if possible, provide information about older versions that you had installed before if you installed newer versions on top without uninstalling the previous version.

There is a default task "Regular automatic update" which is run when the systems starts. There's usually no need to run another update when the gui starts. You might be surprised but there are still rural areas where dial-up is used by quite many people. Also when using DLS, one needs to connect first when the system starts which is also detected as a dial-up connection.

As far as I know, the Japanese partner has not released Endpoint v7 in Japan yet.

Couldn't it be that you use Fortinet or another firewall? It is a known issue of especially Fortinet firewalls that they corrupt update files.

The name of the application should be listed in the prompt window that pops up when an untrusted certificate is detected.

1, Update at logon has always been disabled by default: 2, "That suggestion should be submitted to the requested "Future Changes" thread." That's not really needed. This information was removed intentionally since the version of the detection engine doesn't matter much nowadays in the era of LiveGrid and streamed updates.

Not only an idea but reality. We've been using automated detections for years and this system has developed over time.