Marcos

We will consider it again, however, the last time we analyzed the possibilities of implementation it turned out to be more complicated and challenging than it initially seemed to.

Please raise a support ticket via the built-in contact form and let logs be submitted to ESET for perusal.

Do you mean that you hadn't experienced this issue before a particular module or program update? Could you elaborate more on the issue? Do you get any errors on the home screen and the protection status changes?

A typical infection vector is RDP nowadays. If attackers managed to log into your system with administrator permissions, they could disable or remove ESET and run malware, typically ransomware. In case of an incident you should avoid formatting the hard disk in case you want to investigate the issue and possibly restore encrypted files. Without proper investigation, changing AVs will not make your system safer if you do not secure the attack vector.

What version of ERA are you using? I'm asking cause all versions of the legacy ERA up to version 6.5 already reached EOL and are unsupported. We strongly recommend upgrading to ESET PROTECT as soon as possible. As for module updates, they are dowloaded from the locations that you set up. By default our security products update modules from ESET's update servers, however, you can configure the products to update from a local mirror.

The most recent Patch Tuesday includes a fix for the previously disclosed and actively exploited remote code execution flaw in MSHTML. The post Microsoft Patch Tuesday fixes actively exploited zero‑day and 85 other flaws appeared first on WeLiveSecurity View the full article

The agent log states that the remote server is localhost so it attempts to connect to the ESET PROTECT server on the same machine. Try re-installing the agent and specify a correct IP address of the server.

Have you rebooted the machine in the last 2 days? We have found a bug in the HIPS module 1420 which was put on the pre-release update channel a week ago and then slowly released to all users with a full release on this Monday. Until Itman reported the issue, we hadn't received any reports from users. A reboot fixes the issue. Today we're going to release a hotfix update of the HIPS module which addresses the issue.

Should be soon. Today is a national holiday in Slovakia so I can't confirm the date right now.

I've checked it in the internal bug ticketing system and the bug was created on that date immediately after developers confirming it. Not in the case of business products. We plan to release an uPCU update to v8.1 30-60 days after the release of the upcoming service release of Endpoint 8.1 for all v8.0.x and 8.1.x users.

As I mentioned, the rules are expected to be triggered seldom or often based on what scripts that you use do. If you get too many alerts, it's better to disable a particular rule if it cannot be tuned up, e.g. using a permissive rule for files or processes that you use.

Unfortunately this is not a quick question but an issue report. Please sign up for the ESET forum and re-post in the appropriate product subforum. How do you receive email? Do you read email in a web browser or use an email client? If the former, does temporarily disabling protocol filtering in the advanced setup actually make a difference?

Not really. The bug with "Disable checking upon inbox content change" was discovered and confirmed by developers on July 23, 2021. We have already rolled out a uPCU to the latest v8.0.2039 for users with older Endpoint v8.0. As for uPCU to v8.1, a new service build is going to be released within a few days. After 30-60 days it will be released as uPCU. You could avoid sync issues by reading email only on one device. Accessing it from more devices with ESET installed and Outlook email protection enabled at a time increases the chances of sync issues.

aus01.safelinks.protection.outlook.com was erroneously blocked in the night and was unblocked after 2 hours. We apologize for the inconvenience.

Since this is not a quick question but an issue report, please sign up for the ESET forum and re-post in the appropriate product subforum. Also provide logs collected with ESET Log Collector as follows: - enable advanced antispam logging in the advanced setup -> tools -> diagnostics - reproduce the issue - disable logging - collect logs with ESET Log Collector.