Marcos

Yes, a license key is valid for any version of the product that you have purchased.

You should only use the license key for activation that you have received after the purchase. Do not use leaked or someone else's keys. Not only it is illegal but also such keys have relatively short lifetime and being not protected with current modules will expose you at risk.

Since you are not using ESET, I'd recommend contacting your AV vendor for assistance.

What should be that port for? Didn't find it listed at https://support.apple.com/en-us/HT202944. If your Mac connects to another machine, don't specify the local port. If it's your machine that provides a specific service and other machines connect to it, specify the port as local and leave the remote port blank.

This would happen if edevmon.sys is removed from the disk without being properly uninstalled from the registry. It is not clear and doesn't make sense to me why enabling WD Application Guard for Edge would cause such crash. If you boot from a live cd/usb medium, does edevmon.sys exist in c:\windows\system32\drivers ?

I have no clue since I don't use Windows 10 Insider Preview. If there has been a new IP build released by Microsoft and addressing this issue, someone would have already informed us here I assume.

Re. Mojave Apple states "Coming later this year". We support only officially released MacOS versions. That said, once it has been released to the general public, ESET will support it.

It blocks user-defined numbers. The problem with pre-defined phone number blacklist is that phone numbers may change the owner over time.

It looks like you have ByteFence PUA installed. You should be able to uninstall it like any other application.

Are you able to reproduce it with Edge, IE or Firefox? Does it happen even if you have 1 tab open in Chrome? I'd suggest using Procmon to capture the operations that occurred during a freezing period: https://support.eset.com/kb6308 Does merely pausing the firewall from gui make a difference or it must be disabled completely in the advanced setup for the issue to not occur? At any rate, I'd recommend contacting your local customer care so that the case is tracked properly.

The blocked IP address was an FP and will be unblocked momentarily. Next time please report possibly erroneous url blocks as per https://support.eset.com/kb141.

The website appears to be clean now and thus will be unblocked momentarily. Next time please report possible blocks of already cleaned websites as per https://support.eset.com/kb141.

Unblocked now. It was blocked a couple of months ago and nobody has reported it until now.

Dobry den, zozbierajte logy s nastrojom ESET Log Collector a poslite mi vygenerovany zip cez sukromnu spravu: https://support.eset.com/kb3466/?locale=en_US&viewlocale=sk_SK

Most likely you have upgraded to the latest version of Windows 10 Insider Preview build. Microsoft is going to address the issue in one of the upcoming IP builds. Since we have a topic on this subject already open, we'll draw this one to a close. Please continue at https://forum.eset.com/topic/15949-hips-cannot-communicate-with-driver/.

Already discussed here: https://forum.eset.com/topic/15949-hips-cannot-communicate-with-driver/ Microsoft should release a build with a fix to the issue soon. In order to keep discussion on a particular subject at one place, we'll draw this topic to a close.

By the way, on Windows we strongly recommend preferring ESET Endpoint Security to ESET Endpoint Antivirus since it also contains Network protection module which can also protect unpatched computers from exploits in network protocols, such as SMBv1. With this protection, users of ESET Endpoint Security v6 were protected from the infamous WannaCry and other malware exploiting the EternalBlue vulnerability for spreading over networks. Also troubleshooting network-related or update issues is easier with EES since it enables logging of the network communication to a pcap log.

In the topic name you wrote "ESET Endpoint Security" but according to the screen shot you are eligible to activate only ESET Endpoint Antivirus and File Security.

What error do you get when you attempt to activate EES for Mac directly on the client?

Just out of curiosity I tested v11.1.54 and 10.0.390 and resizing columns worked like a charm with either one.

Please provide a Procmon log from install (refer to https://support.eset.com/kb6308) as well as logs gathered by ESET Log Collector. If it's not a c lean install, you may need to run the ESET Uninstall tool in safe mode.

Please provide install logs as per the instructions at https://support.eset.com/kb406/ as well as logs gathered by ESET Log Collector. The message you've mentioned is just informative and has no effect on the functionality.

If SSL/TLS filtering is not properly implemented then yes, it can cause more harm then good. However, that is not the case of ESET. Whether a website uses http or https doesn't tell anything about whether it can be trusted or not or whether it's benign or malicious. As we have already said, not all https communication is filtered and scanned; EV certificates and trusted sites are excluded by default.

Because they communicate over https and the certificate they use is not an EV certificate (typically used by banks for instance). You can exclude particular applications or certificates from filtering.

With SSL/TLS filtering disabled you can block the hostname, e.g. https://domain.com but not https://domain.com/malware and urls with a path on the blacklist won't be applied either. Also if an application (malware) communicates with a server over https, this communication cannot be scanned unless you enable SSL/TLS filtering.