Marcos

Just to make sure, could you confirm that it's a Chinese version? You seem to be from China so I ruled out that it's Japanese version for which 12.0.27.0 is the latest available.

The change you are referring to concerns ISPs that return an incorrect response in case a file is not found. That said, the change was not a fix of a bug but a workaround for scenarios where the provider doesn't adhere to the standards.

I assume that temporarily uninstalling ESET would not make any difference. Please try it in order to rule out ESET being the culprit.

Policies assigned to parent groups are also applied to child groups. If you want to avoid that, move the subgroup to a separate group or create a new group without any policies assigned and move both the computers and servers group into it.

Yes, trace log uses UTC intentionally and it cannot be changed to local time.

ESET servers are up and running all the time. Seldom there used to be issues with activation but these were resolved with priority quickly. The issue you mention could not be definitely caused by slow update servers; the infrastructure is robust and is capable of serving updates at all times. I rather assume the issue was between your machines and your ISP or between the ISP and ESET's infrastructure. Should you run into the issue again, please contact customer care for further troubleshooting.

ESET's EELAM driver doesn't load during system startup. I assume that uninstalling ESET would not make any difference with regard to the error. I was able to find only one report of this issue, however, it's not clear what actually fixed it for the user: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/measured-boot-library-encountered-a-failure-and/b3b41312-abb3-4ea0-9a7b-17c1a2ed5506.

You can use another security sofware in tandem with ESET, however, only as a second-opinion on-demand scanner, ie. with none of its drivers running.

Please start off by posting here the alleged spam email in the eml or msg format.

Please make sure the device is not marked as missing in the Anti-Theft portal. If it is, mark it as not missing and click refresh in Anti-Theft on the machine. If that doesn't help, please drop me a personal message with your my.eset.com registration email address and provide the name of the troublesome device as well.

Please contact Newegg or maybe ESET LLC. We have no clue as to what a "5 PS product key card" is.

Please make sure that the computer can access activation servers listed at https://support.eset.com/kb332/.

Did you try to check for a newer version manually?

If the agent still connects to your ERA/ESMC server, remove or change the password via an agent policy prior to uninstall the agent:

When there is news on integration with a specific router, we'll announce it via standard channels.

By default, logs with lower severity are removed after 1 month. This can be configured in the advanced ESMC Server setup: If you create a Web Control rule with higher severity (warnings / critical), the records are retained for 6 months. We do not recommend creating a Web Control rule that would log every accessed url or it will generate huge logs on clients and performance issues not only on clients but also on the ESMC server which may result in inability to log in due to server overload caused by processing a huge number of records.

First of all, you should take measures to prevent attackers from getting administrator access to the machine, typically via RDP. I will drop you a personal message shortly.

The error means a problem connecting to a proxy server. Is it disabled as shown below? Is it disabled on other machines where you successfully activated Endpoint as well?

It is only possible to block whole devices (e.g. hard disks), not only particular partitions. Check the system Device manager and post a screen shot of where the troublesome disk appear in the device tree.

I mean, what error do you get if you enter the license key here? A registration email sent after purchase contains the license key (not a file). You can try to retrieve it through https://www.eset.com/int/support/lost-license/ or by contacting the partner from whom you purchased the license.

You should be able to find the detection records in the Detected threats log.

Probably you have an adware-like browser extension installed. Try running Chrome without extensions, ie. with the "--disable-extensions" parameter or disable/remove extensions one by one until you narrow it down to the offending one.

I'll wait for ELC logs since only an xml file with exported configuration can tell if the rules are actually duplicate.

Please gather logs with ESET Log Collector and provide me with the generated archive. Couldn't it be that the path to an application changes? Isn't it applications installed in c:\Program files\WindowsApps folder that you are asked for an action repeatedly?