Marcos

V10.1 also had these notifications. Older versions didn't notify the user even if LiveGrid didn't work.

Do you have automatic activation of gamer mode for applications running in fullscreen mode enabled or disabled?

Please collect logs with ELC and provide me with the generated zip archive so that I can review your config and rules.

Is ekrn.exe among running processes in the task manager? Is there also egui.exe? If not, are you able to launch egui.exe from the Start menu?

It would not be possible to temporarily suspend processes as it takes minutes to get results from replicators. With submission of files disabled, it can happen that a malware will be detected only in memory after execution by AMS but since no actual files will be submitted to ESET, we won't be able to add regular detection applicable by all scanners. Normally that should not happen as someone else would encounter and submit the new malware but in case of a targeted attack we would not get the malware.

Older versions didn't check if LiveGrid works or not. During install, you can choose whether you want to submit suspicious files and statistics to ESET. It's not possible to disable LiveGrid during install. It's one of the main protection features that enables ESET to quickly respond to new malware and provide users with maximum protection. Disabling LiveGrid completely (ie. checking hashes against LiveGrid servers) will substantially deteriorate protection and cleaning capabilities.

What about adding 127.0.0.1 in the "Excluded IP addresses" list ?

That is a correct behavior. Disabling LiveGrid completely (ie. even simple asking ESET's server about hashes) has substantial adverse effect on detection and cleaning and therefore it's signalized by a red protection status.

Pausing protection is only possible locally by a user with administrator rights or from ERA by sending a special Run command task. If settings are protected with a password, the user must enter a correct password.

Does disabling any of the following make a difference? - Automatic start of real-time protection followed by a reboot. - Disabling HIPS followed by a reboot. - Disabling protocol filtering in the advanced setup.

If generating a Procmon log is not an option, please try to configure Windows to generate complete memory dumps and trigger a crash to generate one as per the instructions at https://support.eset.com/kb380/. It will help us determine if ESET is somehow involved in the issue or not.

Are you able to open https://edf.eset.com/edf in a browser using the same proxy settings as set in the ESET setup? Ie. if you don't use a proxy, it must not be set in the ESET setup either. If that works, I'd suggest contacting your local customer care that will provide you with a tool for diagnosing activation issues.

I've got information that LiveGrid servers should be up and running now alright.

Our engineers are working on fixing LiveGrid servers which may take a while. We apologize for the inconvenience.

It looks like a problem of the cafe management software. If disabling all protection modules or renaming ESET drivers in safe mode, one at a time, doesn't make any difference, it's highly unlikely that the application crash has nothing to do with ESET.

To avoid having multiple topics about this issue, we'll draw this one to a close. Please continue with the discussion at https://forum.eset.com/topic/13562-the-eset-live-grid-servers-cannot-be-reached/.

To avoid having multiple topics about this issue, we'll draw this one to a close. Please continue with the discussion at https://forum.eset.com/topic/13562-the-eset-live-grid-servers-cannot-be-reached/.

To avoid having multiple topics about this issue, we'll draw this one to a close. Please continue with the discussion at https://forum.eset.com/topic/13562-the-eset-live-grid-servers-cannot-be-reached/.

To avoid having multiple topics about this issue, we'll draw this one to a close. Please continue with the discussion at https://forum.eset.com/topic/13562-the-eset-live-grid-servers-cannot-be-reached/.

You could not experience this message earlier as the notification about communication issues with LiveGrid servers was first added in v10.1. I've reached out to developers to confirm or deny that there have been some issues with LiveGrid servers earlier today.

If you have a path to ecls.exe entered in the virus scanner setup in IDM, make sure it points to a correct ESET install folder.

As long as the activation code is still valid, you should be able to use it to activate v11. Your license entitles you to download and activate any version of the product you purchased.

Please refer to https://support.eset.com/kb141/.

V10 should report the same problem if connection to LiveGrid servers is not possible. Older versions didn't report anything even if communication with LiveGrid servers was blocked by a firewall for instance.

Bad result? I don't see any bad results there but there's definitely an issue with the methodology. As for the urls, it appears to be there were no malicious ones that were not blocked by ESET but those not blocked was mainly fresh phishing from today which was not blocked at that time by any AV. As for the on-demand scan "test", I "like" tests where one puts all mess (benign files, apps with Chinese gui, PUAs, etc.) into a folder, then scans the files and presents undetected files as misses AVs that detect such files have FPs and should be penalized for that but in these "tests" they get good points for detecting FPs. A credible tester should know what he or she has in the test set, should be able to distinguish malware from PUAs, greyware and other benign applications and remove such from the test set. Including non-malicious files usually substantially skews the final results. Also note that on-demand scans do not reflect the real-world scenario. In real world, malware is usually downloaded by malicious scripts on compromised websites or spread by spammed email. Running just an on-demand scan cannot test other protection layers that might have prevented the malware from being downloaded and executed.