Aryeh Goretsky

I see, the latest version of ESET NOD32 Antivirus for Linux desktop is 4.0.95. While it's a legacy product, it can detect malware detected by the on-demand scanner in newer products for Windows. That said, if a detection was created for a malicious browser plug-in, it would be detected by EAV for Linux too.

I see that you have 2 licenses for ESET NOD32 Antivirus; one for 4 seats and the other one for 1 seat. Since you haven't changed the product with purchasing the renewal, you don't have to do anything but make sure that ESET is activated with the license key BCHP-XXXX-XXXX-XXXX-4MDU on not more than 4 machines and with BCHP-XXXX-XXXX-XXXX-4MDU on 1 machine at maximum. You can use the license manager at my.eset.com to manage your licenses.
When either license is due for renewal, I'd contact the seller (ESET LLC) and ask to merge the two licenses into one for your convenience.

ESET LLC doesn't provide a phone support for home users but they offer a live chat. Anyways, the issue you have described will require a support ticket to be created for further investigation and troubleshooting; it doesn't sound like anything that could solved over chat or phone call.
Regarding a comparison with MBAM, ESET detects all types of threats; from phishing through scam, adware, potentially unwanted and unsafe applications, suspicious applications to malware (worms, viruses, trojans which include also ransomware, backdoors, etc.). We just don't detect benign files, e.g. binary data files that might come with malware but can't be run and do not contain any recognizable data.

1, Correct, the module will be downloaded automatically with engine and other module updates.
2, Under Update -> Show all modules you can check the version of installed module. The version of the fixed Cleaner module will most be 1213.

I would recommend collecting logs as per https://support.eset.com/en/kb6159-run-the-info-getcommand-on-a-linux-virtual-machine-and-send-the-logs-to-eset-technical-support and opening a ticket with your local ESET support.

Also the problem here appears to be not Eset's eamsi.dll, but CSO's new "Trusted mode" feature that is also causing issues with other running software: https://www.pcgamer.com/csgos-trusted-mode-anticheat-system-is-live-but-its-causing-problems/
Believe this is something that needs to be reported to CSO's developers. Security software mechanisms that worked prior to Trusted mode implementation should also be allowed in this new mode.
Also of note:
https://blog.counter-strike.net/index.php/2020/06/30683/
It also appears that Symantec does offer Authenticode signed certificates: https://urlssl.net/symantec-code-signing-certificate.html . Therefore the issue is not with Symantec certs. per se.
-EDIT- Believe this is the issue with CSO. Eset's cert. for eamsi.dll is not an EV cert.. However, Eset also countersigned eamsi.dll with it's Microsoft issued driver cert. which is an EV cert.. This appears to satisfy most apps requirement for an Authenticode signed certificate, but not for CSO it appears. This is also why Code Integrity errors are being thrown by some apps.

If you ran a custom scan, make sure that you didn't enable scan without cleaning:
 

The only way to get rid of this detection is to get an UEFI/BIOS version from Lenovo that doesn't include the Computrace components and re-flash the UEFI/BIOS.

The above files were detected on the C drive according to the screen shot. However, it's unlikely to be FP and it's most likely Lojack by Absolute Software that Lenovo used to install to laptops.

EFI/Computrace detection is correct, it's not a false positive.

It's normal to be detected as a PUsA. Trojan detection is rather a FP.

Since this forum is not a channel for disputing detections and url blocks. we'll draw this topic to a close.
Only the security malware lab is entitled to make decisions about url blocks. In this case, the blocks appear to be ok. Aggressive or misleading ads are subject to detection as well.

The detection is correct. It's not that the website is on a blacklist but it's an adware javascript that was detected.

If it's a pre-installed application, it cannot be removed, only disabled.

I don't think it's possible. Moreover, I can't think of a good reason to not use the latest installer.

Please run the ESET uninstall tool in safe mode and after starting Windows in normal mode install EFSW 7.1 from scratch.

Update of ESET fixed the problem. Please close this post. Thank you.

Yes, it was a false positive created by the mechanism for automatic generation of detections.

Most likely you are still on an older engine. The current one is 21448 which doesn't detect the file any more and 21449 is going to be released momentarily.
 

It should be fixed in the upcoming module update.

Hello,
The goal of this message thread is to provide ESET with specific feedback on changes and new features you would like to see in future versions of ESET Internet Security or ESET Smart Security Premium. Please use the following format when providing feedback:
Description: A very-specific one-line description of your feedback.
Detail: A more detailed explanation of your feedback. Please feel free to make this any length, but be sure to use terms everyone can understand. If your suggestion is an extension or update to an existing discussion, please include a link to it in your message.
 
Here is an example:
Description:  Arduino support
Detail:  The Arduino is a small ARM-based single-board computer popular with hobbyists.  I think ESET should make a version of ESET Internet Security for it.
You are welcome to discuss the merits of each and every suggestion, but keep your comments on topic, concise and thoughtful.  There are other parts of the forum to discuss issues.
NOTE:  When making your requests do not offer general suggestions such as "better detection, HIPS, firewall, cleaning, and so forth."  ESET's threat researchers constantly examine new threats and release updates to the virus signature database and to the modules in order to improve these functions.  Requests must be actionable:  If you have a specific feature or functionality you would like to see added (or improved) please post it here, but general requests to "make things better" or "improve detection" are not helpful because they do not give ESET detailed enough information.  Thank you for your understanding.
Regards,
 
Aryeh Goretsky

After update to new version it works. Thanks

The PUA detection is correct. It's optional. For more information what PUA are, please read https://support.eset.com/en/kb2629-what-is-a-potentially-unwanted-application-or-potentially-unwanted-content.
If you think that benefits of using a particular PUA outweigh possible risks, you can exclude the PUA from detection.

Hello,

Just to add to my colleague @Marcos suggestion, I would strongly recommend you back up any important information stored on the drive, as it sounds like it has begun to fail.  SSD failure modes can be very problematic in terms of data recovery, so it is a very good idea to make sure any type of information you have on the drive which is valuable to y ou is saved in one (or more) backups.
After you have gotten your important information backed up, check with the SSD manufacturer to see what diagnostic software they offer to check the drive, as that may provide you with additional information/insight into what is happening, as well as what options are available, such as replacing the drive under warranty, and so forth.

Regards,

Aryeh Goretsky

As I wrote, the license I found was for 1 computer, not for 3. Please contact the seller if you actually extended it to 3 computers.