Marcos

Customer care can submit a market requirement if there's a demand for a specific feature. If the demand is high enough,it will be cosidered for future versions.

AppLock prevents applications from starting. It does not block already running applications. The list you are referring to are applications that are running in the background. You can close a particular application, e.g. by dragging it to the right and you should not be able to start it then.

AppArmor is not supported. I don't think it's possible to work around it but you can contact customer care.

If you mean upgrading ESMC, send an ESMC upgrade task to it.

Unfortunately I have no clue what you mean by "recents". On my Android phone there is no such feature to show recently used applications. You can contact customer care via the built-in form but we cannot guarantee we will be able to do anything about it. The thing is 3rd party vendors are limited by Android itself and by customizations that the mobile maker implemented.

If you perform a server-assisted installation, agent will download certificates from the server.

What ESET product / version do you have installed?

ESET does not log blocked communication by default. And in automatic mode, all non-initiated inbound communication is blocked. Logging of blocked communication can be achieved by creating a general block rule with diagnostic logging severity that you put at the end of the rules list.

Please post a screen shot for clarification.

If you check Endpoint's gui, is it reporting that Windows updates are available?

1, Do you see LiveGrid settings in the advanced setup? 2, Do you remember from what version of EIS you upgraded to v12? If you use custom settings, export the configuration, uninstall v12, install it from scratch and finally import your settings.

The Update module is updated on a per-need basis,approximately 3-4 times per year.

If one module updates fine (e.g. the engine), the others must update fine too. What makes you believe that other modules are not updated? Please post information about installed modules from one of the troublesome machines.

The following are last operations performed before ERAAgent exists so I assume that reinstalling Visual C++ 2015 redistributable might fix the issue:

If you are getting too many prompts from Webcam protection, please make sure that you have the latest version 12.0.28 installed.

Please provide ELC logs as well so that I can determine the cause and know what to focus on in the Procmon log.

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.