Marcos

Please post status.html here.

Had the download speed been slower for a longer time or just yesterday?

You can use a filter to display only unhandled (active) threats.

If one needs to parse the email, adding html content would make it more difficult. I think the email must be brief and contain only the necessary information.

Unhandled threats are displayed in red while handled threats in orange.

Yes, please drop me a private message with a download link.

Do you have any issue with protection modules because of the error? Does temporarily disabling Self-defense and rebooting the machine makes the issue go away? If not, does temporarily uninstalling ESET make a difference?

We don't have any special version for tablets with Windows, only with Android.

Please read https://support.eset.com/kb3466/ for instructions.

I'd suggest to check Scheduler and keep only Regular update task enabled and see if that helps.

Is it enough to pause web protection (1) or only disabling protocol filtering (2) makes the issue go away ? 1. Web protection paused 2. Protocol filtering disabled

Please start off by collecting logs with ELC and providing me with the generated archive for perusal.

I'm unable to reproduce the block. Please provide a screen shot of the alert that you are getting.

Why do you suspect ESET to be the culprit? Does pausing real-time protection or temporarily uninstalling ESET make a difference?

Please make sure that protocol filtering is enabled on the client. Do you have ESET Endpoint Security or ESET Endpoint Antivirus installed?

HIPS is a crucial protection feature similar to real-time protection. By disabling HIPS, you also disable: - Self-defense - Advanced Memory Scanner - Exploit Blocker - Ransomware Shield - reporting operations to ESET Enterprise Inspector for evaluation of signs of APT malware https://www.eset.com/int/about/technology/ Although it's possible to disable the notifications in the Application statuses setup, I strongly recommend keeping HIPS enabled if you want to have the system protected against new borne threats.

Please follow the instructions at https://support.eset.com/kb141/ to report the website to ESET next time.

Does the issue persist with the Configuration module 1659.1?

If the uninstall completes alright, it's highly unlikely that any further BSOD or issues could be caused by ESET. Anyways, we are willing to check dumps to 100% confirm that it's unrelated.

You have the following options: 1, Uninstall / reinstall ESET. 2, Wait until a new version of the Configuration Engine module is released. Until then, ESET will continue protecting you despite the issue with gui. 3, Ask customer care for an unlock code. This option is not recommended since you will likely receive the new module sooner than a response from customer care.

The quickest and 100% working solution is to remove ESET in safe mode using the Uninstall tool and then installing it from scratch. Even if gui doesn't seem to react, the product continues to protect you from malware and update of the Configuration Engine module should fix it automatically when released.

The new Configuration Engine is included in v11.1.4x installers which is why there's no issue with a fresh install, only with upgrade. Only users with release updates were affected because an older version of the Configuration engine was available on release update servers. Those who updated from pre-release update servers were not affected because the new CE module had been there for weeks before update to v11.1.4x.

Please leave updates on pre-release until the new Configuration Engine is fully released for all users which will take a few days.

Please contact your local distributor who might have their own forum available. The official ESET's forum supports posting only in English and Slovak/Czech which are languages that most of users and moderators speak.

Update had been tested for several weeks before it was released. The problem was in an older Configuration Engine module on release update servers. On pre-release and test update servers, a new Configuration Engine module has been available for several weeks which is why the issue didn't manifest for those who were testing it. We apologize for the inconvenience.