Marcos

Support for Thunderbird was discontinued years ago. However, email received via IMAP(S) or POP3(S) in Thunderbird is scanned by ESET. It's just that you can't scan already received messsages on demand or that received messages are not scanned by ESET antispam. Otherwise malware should be normally detected in received email.

V6 is in limited support and as such is not developed any more:
https://support-eol.eset.com/en/policy_business/product_tables.html
V7 with added features will be available in the future.

V6 is in limited support and as such is not developed any more:
https://support-eol.eset.com/en/policy_business/product_tables.html
V7 with added features will be available in the future.

There are currently no plans to release EEA v6 compatible with macOS Sonoma. However, you can contact your local ESET distributor or reseller and they'll try to come up with a solution for you.

Unfortunately without knowing the detection name and the object where the detection was triggered we can't help you and give some suggestions. I can only assume those are HIPS-based behavioral on in-memory detections which can be disabled only in the advanced setup and not via the tray icon menu.

Support for Thunderbird was discontinued years ago. However, email received via IMAP(S) or POP3(S) in Thunderbird is scanned by ESET. It's just that you can't scan already received messsages on demand or that received messages are not scanned by ESET antispam. Otherwise malware should be normally detected in received email.

On the second machine you had Secure all browsers (SAB) disabled and set up some protected websites in the past. Later you enabled SAB.

We don't check for installed updates but perform a true ACS test instead. This information is from the developer who implemented the test routine that creates the said registry value.

Please use the latest version of Process Explorer from the Microsoft website.

The latest version does not contain a vulnerable driver.

Please provide the content of the C:\Program Files\WindowsMalwareProtection folder. Move the folder to c:\esetvir for instance and reboot the machine.
You can then select the 2 scheduled tasks and delete them.

If I remember correctly, SS filtering used to be disabled by default in older versions of Windows server products. Therefore you must enable SSL filtering via a policy:

Note that SSL/TLS filtering may cause issues with some SSL/TLS enabled server applications so it's possible that you will have to exclude them.

It is actually Microsoft that sunset support for cross-signed root certificates: https://knowledge.digicert.com/alerts/Kernel-Mode.html.

Nobody can tell for sure. What I can tell is that ESET didn't detect any malware upon opening the website.

Even the site with the com TLD is pornographic. As for whether it's malicious or not, I can only tell that ESET didn't detect any malware upon opening it.

ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 16.2.15 have been released and are available for download.
Changelog:
Version 16.2.15
FIXED: Fixes in backend communication
FIXED: App icons displayed incorrectly when selected rules created with MS store apps
FIXED: Email address not submitted with samples
Known issues:
N/A
Upgrade to Latest Version
Upgrade my ESET Windows home product to the latest version
If your ESET security product has not updated automatically yet, you can enforce product update by manually checking for update in the Update panel or wait until it updates automatically.
Support Resources
ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support.
Online Help (user guides) Visit www.eset.com/contact to email ESET technical support

For almost every home user it is important that the antivirus works as much automatically as possible. Those who have been using interactive mode often complained that after updating Windows Store applications rules stopped to work. The solution are rules created by the app name and signer by default. Using application path would return the issues that users were struggling with. While we listen to you, our customers, we are also aware that we cannot please everyone and there will always be someone disappointed.

For almost every home user it is important that the antivirus works as much automatically as possible. Those who have been using interactive mode often complained that after updating Windows Store applications rules stopped to work. The solution are rules created by the app name and signer by default. Using application path would return the issues that users were struggling with. While we listen to you, our customers, we are also aware that we cannot please everyone and there will always be someone disappointed.

V17 will be released later this year.

Yes, Vulnerability Assesment and Patch Management is a new feature. According to https://help.eset.com/protect_cloud/en-US/?vulnerabilities.html, it requires:
•ESET PROTECT Elite or ESET PROTECT Complete license
You can enable ESET Vulnerability & Patch Management only on Windows computers running:
•ESET Management Agent version 10.1+
•ESET Endpoint Security for Windows version 10.1+
 
 

As far as I know, it's a known issue. Please raise a support ticket so that you are informed about the latest development in this matter.

We confirm it's a false positive by Microsoft.

Definitely FP.  SecureAge is not one of the most popular and reputable AV vendors I'd say.

A response is not guaranteed when you contact samples[at]eset.com. It is up to the malware analysts to give priorities to particular tasks. Tickets with very low quality samples that include clean, non-functional files, greyware, files not subject to detection, such as source files may never be replied to as out analysts primarily deal with malware and samples that pose actual risk to users. We encourage everyone to submit highly suspicious files and appreciate it. Samples that are actual malware are usually detected within minutes or hours at maximum.
Having said that, we'll draw this topic to a close.

It was a false positive which has been already fixed. If still detected, run update manually please.