Marcos

Do you want to protect files with certain extension in a particular folder and prevent them from being deleted?

Please provide logs collected with ESET Log Collector on your machine so that we can check the version of installed modules as well as the configuration of your ESET product.

Yes, it works for any version of the product that you purchased.

No problems here opening the website in Chrome with SSL scanning enabled: Try the following: - disable SSL filtering and click OK - with browsers and email clients closed, re-enable SSL filtering and click OK - check if the issue still persist.

That's weird since the %SystemRoot% variable expands alright under the local system account according to my test:

Do you mean you were attempting to ESET File Security for Windows servers ? If so, please generate install logs as per https://support.eset.com/kb406/ Besides the install log, please provide also logs collected with ESET Log Collector.

If it works with 0-8008, 8010-65535, use these ranges. Here I suggested more exclusions as per Google's KB article: Please check my previous suggestion at Probably within this week a newer version of the Internet protection module 1375 will be available on the pre-release update channel which will address the issue without defining any exclusions in your ESET product. If everything goes well, the module will be distributed to all users afterwards.

I would say you'll need to use ESET's API to scan files and evaluate the result based on the return code. However, since I'm not an expert on the API and probably nobody else will be able to provide you with a satisfactory answer here, I'd recommend opening a support ticket with your local customer care.

You could use HIPS to block files with certain extensions in a particular folder. However, HIPS doesn't currently support detection of file types other than by their extension.

According to the version number, it seems you have Endpoint Antivirus installed, don't you? Could you try uninstalling Endpoint (you have a quite old version 6.3) and install Endpoint Antivirus v7 with default settings to see if it makes a difference?

It could be a conflict with another plug-in. If you have some other plug-ins installed, try disabling them temporarily and leave only the ESET plug-in enabled. For further troubleshooting, please create a support ticket with your local customer care. A diagnostic version of the plug-in will need to be installed and logs generated for further analysis.

As stated in Please read this before you post: Do not report blocked websites After cleaning a website from malware and taking measures to prevent further re-infection, request a re-check as per the instructions in the FAQ. This forum does not serve as a channel for requesting website re-check or disputing blocks or detections. Please continue as per the instructions above. Having said that, we'll draw this topic to a close.

There are "Failed to create rule" errors logged in the firewall log. It appears that automatic firewall mode is enforced by a policy. In automatic mode (default) without any custom rules all outgoing communication is allowed and only non-initiated incoming communication is blocked. I see that you have 3 permissive rules created so these should not block any communication. Did you set the policy to replace the existing ones on clients or to be appended to the existing ones? Did you intentionally remove pre-defined fw rules from the policy? Please enable advanced network protection logging under Tools -> Diagnostics, reproduce an issue with blocked communication and provide fresh ELC logs.

Please open a support ticket with your local customer care and provide them with logs collected with ESET Log Collector. Prior to collecting logs, select "All" in the ELC list so that a registry dump is included in the package as well. The case will need to be looked at by developers.

Still, MariaDB is not officially supported. While it may seem to work, you may run into issues later. Please consider changing the db to MySQL.

You can run a task on a static or dynamic group that will run a particular command on the clients.

This is not possible. Agent on clients doesn't currently check for system uptime so the value cannot be used in expressions for dynamic groups.

Please contact your local customer care and open a support ticket since this issue will require a deeper investigation.

Release Date: July 30, 2019 ESET Mail Security for Microsoft Exchange Server version 7.1.10009.0 has been released and is available to download. Changelog Version 7.1.10009.0 Fixed: Deleting of SCL before scan should be based on a setting (checkbox in GUI) Fixed: Various localization bugs Known Issues To review a detailed and up-to-date list of known issues, see Known issues for version 7 ESET business products. Support Resources For more information and to download the product, visit the ESET Mail Security for Microsoft Exchange Server download page or contact your local reseller, distributor or ESET office.

Do you have ESET Internet Security installed? It contains a firewall which, however, allows all outgoing communication. Does pausing the ESET firewall actually or disabling protocol filtering in the advanced setup make a difference?

Ak mate na mysli archivovane "topic-y", v ktorych nikto neodpovedal, toto by sa nemalo stavat a v kazdom by mala byt minimalne reakcia od ludi z ESETu. Mozno sa jedna o nejake velmi stare zalezitosti, kde k tomu mohlo prichadzat castejsie, bolo by preto vhodne, keby ste nam dali linku na konkretny "topic", ktory ostal bez odpovede a neda sa nan uz momentalne reagovat.

If you check Device Control logs in Endpoint logs directly on the client, are the events logged only once?

Perhaps the best course of action would be uninstalling ESET and installing the latest version 12.2.23 from scratch. As staskz mentioned, it appears you had ESET Smart Security installed in the past which changed to ESET Internet Security as of v10. Although the upgrade should have been seamless, the ProgramData folder didn't change from ESET Smart Security to ESET Security for some reason.

I see that you use MariaDB which is not officially supported and issues may occur.

Yes, they do. However, if a scheduled scan uses a profile that has logging of all files disabled, it shouldn't generate big logs either.