Marcos

If the problem persists after uninstalling ESET, you will rule it out. Otherwise we would continue with investigation of the issue.

If the scan progress hangs like in your screen shot, then it's a known issue of v11.1.42 which has been fixed in the mean time. It will be addressed in the next service build of v11.1 which should be released some time soon.

To my best knowledge, we haven't received any reports of the system being hung after a module update. I'd suggest configuring Windows to generate complete memory dumps and enabling manual triggering of a crash so that you can generate a dump should the system get hung again. A complete memory dump should reveal the actual cause of the problem.

Are you getting an error even if you enter your current license key manually in the activation form in Endpoint? If so, what error is it?

Do you use default ESET's settings without any custom HIPS and firewall rules? Does temporarily disabling protocol filtering in the advanced setup make a difference? If not, what about temporarily uninstalling ESET?

As for what is being logged, you can check the mail server protection logs and review the records. Regarding ELC logs, you can decide what exactly will be submitted. If you think that some non-ESET logs are not suitable for providing them to us, it should be basically ok if you don't select them to be collected.

Please provide a Procmon boot log (read https://support.eset.com/kb6308/ - steps 1-4 and then follow the instructions Gather boot log files). Also collect logs with ELC. When done, upload both archives to a safe location and drop me a message with download links. Before you start, temporarily disable Protected service in the HIPS setup and reboot the machine.

Please provide a Procmon boot log (read https://support.eset.com/kb6308/ - steps 1-4 and then follow the instructions Gather boot log files). Also collect logs with ELC. When done, upload both archives to a safe location and drop me a message with download links. Before you start, temporarily disable Protected service in the HIPS setup and reboot the machine.

For me the Zvelo form is working alright. Have you tried setting Google DNS servers 8.8.8.8 / 4.4.4.4 on a computer to see if it makes a difference? Should the problem persist, install ESET Endpoint Security 6.6 on one of the machines, enable advanced firewall and Web control logging, reproduce the issue, disable logging, collect log with ELC and provide the generated archive to customer care for analysis.

We have identified a new code added to HIPS in v11.1 as the cause of "extra" protection of the ekrn-related registry key that services.exe attempted to modify . We'll add an internal exception so that the event is not generated.

To prevent duplicate topics on the same subject, we'll draw this one to a close. Please continue with the discussion here: https://forum.eset.com/topic/15213-new-error-after-upgrade-event-7006-service-control-manager/

Is it a port scan attack that is detected? You can create exceptions for remote IP addresses from which legitimate communication is blocked or even bind the exception to a specific firewall profile (e.g. the one that is active when connected to your company's LAN).

This is not a standard behavior and nobody else has reported an issue like this. Theoretically this could happen if edevmon.sys is removed from the disk but remains registered in the registry, e.g. when the computer is suddenly turned off or restarted before the installation / driver unregistration is completed.

Currently 11.0.159 is the latest version. We plan to release a newer version 11.1.X soon and your ESET will update automatically then.

Currently v11.0.159 is the latest available. In about two weeks we'll be releasing a new v11.1. As for support of Spring Creators Update, v11.0 and even v10 should be fully compatible.

Please contact your local distributor to find out.

Is this a clean install or upgrade, ie. you are installing over an older version? Please provide: - an install log created as per https://support.eset.com/kb406/ - A Procmon log with advanced output enabled as per https://support.eset.com/kb6308/ - ELC logs Upload both archives to a safe location and drop me a message with download links. You can also try running the ESET Uninstall tool in safe mode before re-trying a clean install.

Honestly, I can conceive how this should work. Imagine that some computers may be offline, on some scans may take very long, etc. so the question is how long would be long enough for ERA to wait before a report is sent even if scans were not completed. Also I'm not sure how possible threats from particular scans could be correlated to particular reports from technical point of view.

I'd suggest temporarily enabling diagnostic mail server logging and receive an unrecognized spam. Then disable logging, collect logs with ELC and supply them to Customer care along with the unrecognized spam saved as an eml or msg file. I assume that in this instance Hub transport role is installed since antispam is not available in Mailbox role at all.

Files are always quarantined when cleaning threats regardless of the scanner.

It should be added via an Internet protection module. Changes in modules are available in Customer advisories: https://support.eset.com/advisories/?segment=home.

Do you want Parental Control to be able to use data connections at all? If that's what you mean, I'm not sure if it's a good idea since then Parental Control would lose connection with ESET's servers and you would be able to control it only directly on the phone.

It is not related to the Cryptographic support module, we didn't say that. Pwe said that support for http2 will be added via a module update when it's ready.

So far all cases that users reported have been magically resolved themselves before we were able to connect remotely and debug the issue.

Developers have already replied you: Please note that supporting HTTP/2 means implementing full client and server functionality as specified by standards. This isn't directly related to certificates, and changing the TLS handshake to advertise HTTP/2 support is one of the easiest things to implement. This is not something that can be accomplished in a week or even in 2-3 months. I'd say it takes almost a year to do the implementation and subsequent testing properly. I assume you even didn't expect Microsoft to code Windows 10 in less a year from scratch; it definitely took them years.