[the eset live grid servers cannot be reached]

I didn't have the message again since Sunday October 29th while connected to the internet.

When I use VPN and lose internet access I do get the message but then it's correct because there's no internet connection.

My 'home-internet' to my desktop is via ethernet-cables, so no wifi.

[the eset live grid servers cannot be reached]

Thank you for the fast and accurate responses.

On other forums you may have to wait for a long time before getting an answer if any.

[the eset live grid servers cannot be reached]

Just now, Marcos said:

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

Let me rephrase: "Is the exact reason for the warnings appearing since version 11.0.144.0 known?"

Are the warnings caused by the new version 11.0.144.0?

[the eset live grid servers cannot be reached]

19 hours ago, Marcos said:

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

I haven't seen the warning that the LiveGrid-servers are unreachable or unaccessible since the message above.

Can you tell if the warnings are only related to the new version 11.0.144.0 or could it have happened in previous versions too?

[the eset live grid servers cannot be reached]

7 minutes ago, itman said:

The question is if this option is disabled does it adversely effect LiveGrid's rep scanning of an unknown process using Eset's cloud scanners?

I think it will when you're using a process that's not widely used and poses a yet unknown threat. But if you use 'mainstream software' I don't think it will have a substantial adverse effect.

[the eset live grid servers cannot be reached]

9 minutes ago, razorfancy said:

You dont need to disable LiveGrid for not having the Live Grid not accessible message you can disable that message by going to: Advanced Configuration -> User Interface -> Application Status (Edit) -> General -> Eset Live Grid not accessible (Turn it Off)

Yes, I already found that out this morning. It's especially nice when I'm using VPN and the internet is unreachable.

[the eset live grid servers cannot be reached]

10 minutes ago, Marcos said:

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.

That explains my confusion. I just checked the install-process via YouTube and reread the option which says: 'Enable ESET LiveGrid feedback system (recommended)'. I now understand that this question only has to do with the feedback and not with shutting down 'LiveGrid' altogether. So I must have had 'LiveGrid' active in previous versions.

I understand that the 'LiveGrid' provides better protection and will leave it on.

[the eset live grid servers cannot be reached]

33 minutes ago, Marcos said:

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.

I seem to remember that I had disabled 'LiveGrid' in the previous version and didn't get this red warning.

I also seem to remember to not have checked 'Enable LiveGrid' when installing the update to version 11.0.144.0.

Note that  I use the word 'seem' because I'm not 100% sure and can't check it anymore.

Is showing a red message when 'LiveGrid' is disabled new in version 11.0.144.0?

[the eset live grid servers cannot be reached]

I have had the same problem since the update to version 11.0.144.0.

After reading that the problem is fixed I have just reenabled 'LiveGrid'. I will report if the problem reappears.

By the way when you disable 'LiveGrid' you get a nasty red message. This message can be suppressed via advanced settings - user interface - application statuses.