Marcos

If you have ESMC installed the best would be to add licenses by adding an EBA account to ESMC and add licenses to EBA (eba.eset.com). Some products, such as ESET Dynamic Threat Defense, won't work without that.

Please carry on as follows: - temporarily uninstall EAV - install ESET Internet Security and activate a trial version - in the advanced setup -> tools -> diagnostics enable advanced network protection logging - reboot the machine - disable logging - gather logs with ELC and provide me with the generated archive.

Did you check the licenses and seats in EBA?

I don't think that EAV v4 for Linux supports updates through https. Try using http.

AppArmor is not supported.

Does temporarily pausing real-time protection make a difference? If so, generate a Procmon log so that we can see what files are being accessed / scanned when cpu goes up. 6% utilization is not high, e.g. if a lot of files are actively being scanned.

Does the problem go away after uninstalling EEA? Since Endpoint v5 is in basic support phase, I'd strongly recommend upgrading to EEA v7 first before troubleshooting the issue further. Basic support means: Availability of regular engine module updates Availability of module updates is not guaranteed Product is no longer available for download from ESET download servers technical support is no longer available, no bugs will be fixed

Please read https://forum.eset.com/topic/16908-downdiskcleandrcomplugin/ and continue with the discussion there.

Install the latest version of v9 which is the last one that officially supported Windows XP.

Antispam works only in supported email clients.

I would recommend: - removing the licenses from ESMC - creating an EBA account via eba.eset.com - adding the license (and possible future licenses, e.g. for ESET Dynamic Threat Defense) to EBA - link your EBA account with ESMC in the EMSC License manager. Afterwards you should be able to select a license when creating software install tasks.

Please check if you have protocol filtering as well as http scanning enabled in the advanced setup.

You can export/import policies in the Policy manager:

We will release EFS for MS Azure v7 once MS has fixed a bug with reporting to the Security Center. Without that, the new extension could not report to it and register in the system.

It is currently possible only to export the whole policy / configuration.

Errors like "file is corrupted", "invalid signature", "connection interrupted", etc. are typically caused by proxy servers on the way. In such case, follow my instructions posted above. The best course of action would be contacting your local customer care to ensure that the case is tracked properly.

As for the tag message in emails, it's added only to infected emails by default. It is not good to rely on the information in the message since authenticity cannot be ensured and malware could add a message that the malicious attachment is clean even though it isn't.

One more thing, use the built-in form to contact customer care so that logs from the phone are provided to customer care as well.

Please continue as follows: - enable advanced network protection logging in the adv. setup -> tools -> diagnostics - click Scan your network - after the scan has completed, disable logging - gather logs with ELC and provide the generated archive.

If you are able to reproduce the issue in the future, we'll need you to enable: - advanced update engine logging - advanced network protection logging in the advanced setup -> Tools -> Diagnostics and run update. Next disable logging and gather logs with ELC.

No, the same level of protection cannot be achieved with an extension. Injection into a browser is a must to keep the current level of protection. To my best knowledge ESET doesn't inject into Edge because it runs sandboxed.

So far it was not confirmed to be a bug but rather an annoyance causes by early access to the webcam before Device control is fully initialized. It is still being investigated as we understand it's annoying for users. As for v12, it should be available later this year.

Not everything is feasible since we are limited by how the operating system works and what it enables installed applications to do. If it is that the web camera is accessed prior to device control gets fully initialized, there's probably hardly anything we could do.

Since the discussion has already turned into ranting and even personal offenses, we'll draw it to a close.

I would suggest contacting customer care and providing also information about the brand and model of the mobile phone. Some are known to use aggressive battery savers or power saving modes which can kill even security applications.