Marcos

I was asked to remove the links until the build passes QA tests so I hope I'll be able to provide you with the installers within the next 1-2 weeks.

With ESET Endpoint Security installed, temporarily enable advanced firewall logging in the advanced setup -> tools -> diagnostics and reboot the machine. Then disable logging and collect logs with ELC. Upload the generated archive to a safe location and drop me a message with a download link to the generated archive.

Try disabling the extensions one by one. There's at least one which appears to be adware-related.

We cannot clean PUAs by default because of legal reasons.

Since ESET does not detect MBAM's files, no exclusions should be needed whatsoever.

Please configure Windows to generate complete memory dumps as per https://support.eset.com/kb380/ and reproduce the crash. Then compress the dump, collect logs with ELC and upload both the dump and logs to a safe location and drop me a message with download links.

Please upgrade to the latest version 11.1.42.1 which has it fixed.

It's the same issue as the one reported here: https://forum.eset.com/topic/15163-111420-scans/

That is just an ELC operation log. ELC generates a zip archive with all collected logs.

You must make the appropriate exclusions in MBAM. Why do you need to do that? Does MBAM detect any of ESET's files erroneously as threats?

This notice appears if Parental Control is enabled for your account and you attempt to open a website that falls under a category blocked by parents.

When opening an Internet banking website for which you haven't defined an action yet, you are asked if you want to open it in a secured browser: A secured browser has a green border and the following logo:

Please temporarily uninstall EAV and install ESET Internet Security (activate a 30-day trial version ). Then in the advanced setup -> tools -> diagnostics, enable advanced firewall logging and reboot the computer. Next disable logging and collect logs with ELC. Upload the generated archive to a safe location and provide me with a download link.

He didn't have a clue since with the LiveGrid feedback system is disabled, there should be no communication with TSM*.eset.com servers. Please check if you have some files in the C:\ProgramData\ESET\ESET Security\Charon folder besides cache.ndb.

Yes, settings are saved whenever you install a newer version over an older one or if you perform in-product update. We are going to release a legacy product update for users with older versions to upgrade them smoothly to v11 without the intermediary updates.

Yes. Exclusions without a path just based on the process name would be dangerous. We will be improving the value validator which will prevent invalid values from being entered in the process exclusion list.

Did you leave pre-release updates enabled before restarting the computer? Switching to pre-release updates and immediately back will install the same modules so the fix / change cannot take effect after a reboot. Personally I've used pre-release updates for a long time and wasn't able to reproduce this issue.

Please check process exclusions. The full path to executables must be entered, not just process names, otherwise HIPS won't be able to process the exclusions.

A fixed version is planned to be released in less than a month. This issue should manifest only when an extremely fast scan is performed. I was unable to reproduce it just by scanning a single executable.

Why do you think there's a correlation between the ScRegSetValueExW Event 7006 and the ESET Firewall Helper service given that you confirmed that disabling Self-defense makes it go away? With Self-defense enabled, try enabling logging of all blocked operations in the advanced HIPS setup. When the event 7006 occurs, disable logging, collect logs with ELC and provide me with the generated archive.

There should be no reason to exclude Malwarebytes. Please explain what issue you are trying to solve by adding exclusions since each exclusion creates a potential security hole. Exclusions by paths or detection names can be set in the advanced setup -> Detection engine -> Edit (in the Exclusions section).

Run ELC and collect logs as per the instructions at https://support.eset.com/kb3466/.

Perhaps you could try connecting through a different network / ISP and see if it makes a difference.

TSM*.eset.com servers have nothing to do with updates, neither with standard updates nor with streamed (pico) updates which are downloaded from update servers as well and not from ThreatSense servers. I will talk to the developer who is in charge of LiveGrid for information about the mechanism of communication with servers and will update you then. With Endpoint 6.6 that doesn't use the latest technologies, I have 10 connections with TS servers in TIME_WAIT state after an attempt to update.

I've upgraded from 8.0.319 to v11.1.42. It takes 2 intermediary updates to v9.x, e.g. due to the change of certificates that occurred a longer time ago but you will finally update to the latest version. Or you can uninstall v8 and install v11.1.42 directly.