Marcos

In Endpoint on clients you can configure notifications in the email client protection setup:

Please do not post your email address publicly in the forum. It's in your interest to protect your privacy. As for the last email address you provided, we don't have any license registered to it on files. Again, I strongly recommend contacting your local customer care that should be able to assist you.

First of all, please keep in mind that this forum is not supposed to be a means for reporting or disputing detections or blocks and it's necessary to report it to ESET as instructed also in the FAQ or here: Please read this before you post . In this case, removing the reference to setforspecialdomain.com should cease the detection.

They aren't. There are fully tested modules that are typically released to all users after a few days or weeks without any change. Of course, we don't recommend enabling the pre-release update channel on production machines, however, on non-production systems it'd be good if at least technically savvy users enabled it. Should a problem occur, it's possible to switch back to the release update channel which won't help if a module has been already released for the general public. Before putting modules on pre-release servers we use them to update a lot of production machines in HQ so we are pretty confident about the quality.

Have you already tried this? - uninstall ESET - reboot the machine - install the latest version from scratch with default settings - reboot the machine - launch Firefox and try to reproduce the issue. If it doesn't make any difference, also try switching to pre-release updates to get the very latest modules.

We don't have any license like that. Please contact your local distributor and make sure that a valid license is registered to your email address. The license should be issued by your local distributor. I was able to find only 2 trial licenses issued by ESET LLC from the US plus one for ESET Smart Security Premium which is not for business users and cannot be managed through ELA/EBA. Also I don''t fully understand why you posted screen shots from ELA and EBA. Once you have migrated to EBA, you won't be able to log in to ELA any more.

If it becomes a popular standard, we should support it. I'd say it's too early now to speculate about it and we'd tell more in due course.

1, No license with that public ID exists. 2, There are several TRIAL licenses registered to your email address. All trial licenses are due to expire today. 3, You seem to be from India but the trial license were provided by ESET LLC in the US which can be a problem. You need to have India set as your country if you're from there. You have only one trial license for ESSP registered with a correct country but ESSP is a consumer product not manageable through EBA. If you want to purchase a license or need some additional time for testing, please contact your local distributor. For contact information, please visit https://www.eset.com/in/about/contact/.

We replied in another topic that update to v12.2 will happen automatically for those with pre-release updates enabled most likely within this week. The others will receive it gradually within the next few weeks or will be able to update earlier by manually running update.

What if you apply an agent policy with a blank password set?

ESET detected Spigot PUA which is correct, isn't it? Most of other AVs would not probably detect it at all. ESET JS/Spigot.B application potentially unwanted Symantec clean Avast clean Microsoft clean Avira clean DrWeb clean Bitdefender Application.Redirects.B JS Kaspersky not-a-virus:AdWare.JS.ChromeExt.i McAfee clean To prevent Chrome from downloading Spigot again and again, one may need to disable syncing of Chrome extensions as per https://support.eset.com/kb6551/. I'm failing to see what the problem is. Please elaborate more on the issue you are having.

Logs are generated providing that you have the appropriate option enabled:

Yes, I've realized that it was actually a VM with Windows 7 without SP1. All attempts to install it failed so I gave up, however, the issue was reproduced also on Windows 10 but it took effort and it was not easy to reproduce. It appears that the issue could be caused by some changes in a recent update of the Cleaner modules. We're on it and investigating the issue. Will keep you posted.

After I clicked a link pointing to eicar in a document and saved it, the download url could be seen after checking details of firefox:

First of all, EEI basically shouldn't have FPs because it doesn't say what is malicious and what is clean but informs you about suspicious and non-standard operations performed in your network. They can be legit or malicious; for legit ones it's possible to create exceptions so that such alerts are no longer triggered and reported.

Could you please post a screen shot from English version of Endpoint? Honestly, I don't see any issue there since the additional text was added in an image editor. The best would be to see the original window in English.

ESET Endpoint Encryption 5.0.3 is fully compatible with Windows 10 update 1903.

That is the problem. The Configuration Engine is different for ERA/ESMC so you will need to mirror also the "era6" folder and point ESMC to update from it. However, in order to save Internet traffic I would recommend using HTTP Proxy instead of a mirror created by the Mirror tool which downloads a lot of update files with each update that will never be needed / used by clients. By contrast, HTTP Proxy caches only update files that were actually requested by clients.

Unfortunately, the log seems to be from time when no startup scan was running. Please do the following: - create a complete application dump of ekrn (adv. setup -> tools -> diagnostics -> create) when a startup scan appears to be running - after a reboot enable oper. system advanced logging under tools -> diagnostics, wait until a startup scan completes, disable logging and eventually provide us with C:\ProgramData\ESET\ESET Security\Diagnostics\EsetPerf.etlthe etl log (you'll need to upload it to a file sharing service and provide a download link because of the size).

The issue should be fixed and re-sending a verification email should work now.

Hello, It looks that no startup scan was run while the Procmon boot log was being generated.

Ideally pcap logs should be analyzed by the firewall maker Fortinet, otherwise it's more just speculations as to what happened and if there was a malicious activity or if the detection was a result of some non-standard communication that was detected by the firewall, maybe correctly or incorrectly as a false positive.

So it happens also if you uninstall ESET and install the latest version from scratch with default settings? I'd suggest: - temporarily disabling real-time protection in the advanced setup - creating a Procmon boot log (stop logging after a reboot only after the notification about the startup scan being run goes away)

Unfortunately, it's difficult if not impossible to understand what you mean. Try using Google Translate to translate your post from Polish to English. Also since it's Polish which slightly similar to Slovak, you can try posting in Polish as well. What "threats" did ESET miss? How do you know they were actually threats? Did you submit them to samples[at]eset.com and were confirmed to be threats? Even then, keep in mind there's nothing like 100% malware detection and ESET is an excellent AV. There have been many users who started using ESET because they got hit by ransomware when using another AV. Also ESET is often the only AV (or one of the other two-three) to detect new script malware injected in legitimate websites.

Does temporarily pausing the firewall make a difference? What ESET product do you use?