SlashRose

For me, the solution with the VPN provider was to release the Eset used ports, but for this you need reasonable VPN provider with portforwording.

That's my talk all the time, especially since the bug has been around for a few builds!

Even if the Live Grid Gui does not work, connections are blocked, only the reputation is then not displayed there!

Just like last time, as if by magic Live Grid goes again, I knew why I didn't uninstall it!

The Browser was Open.

This comes down to the same thing, because Ram consumption remains Ram consumption, whether under processes, or under details, but see for yourself.

With me no problems with that.

Yes, I have a VPN, but it is rarely used and since it has portforwording, the ports are also unlocked there and the Live Grid Gui does not work via this either. Since I am once again convinced that a new installation because bug does not fix, because this is not the first version where there were live grid problems and I bet on the next build it will work again. My observation is that Eset has been having problems all the time since Windows 10 was released!

Eset is connected to the Live Grid Server, so I don't really understand the whole thing, maybe a mistake of the Gui? The Live Grid notification is also on.

No I do not receive a notification about Live Grid connection problems, I take the DNS servers of my providers.

I just tested, could all pings

I'm at a loss Itman, have two connections, once at Telekom and once at Vodafone and with both providers It doesn't work, really don't know what else I can do there, I think that Eset might have to become active!

Yes, is the Same!

And once again the LiveGrid does not work, the ports are and were always free, what can I do to make Live Grid work again

That's exactly what I had already reported to the v14 and asked myself, for me it was about eMule, only so really answered was not answered to me!

The Insider Builds run with me only on a test PC, not on my main PC's, I'm not crazy and install Insider Builds on a main computer. @itman, because I can try to clear update cache, but I think something else is going wrong.

If they only talk Marcos about the v15 they are right with the handful, but also a handful is too much with an AV, but I meant from the v14, so I wrote for months.

Marcos that no one says that it is not correct.

Itman is absolutely right, the packer that is also used for KMS and other cracks is also used by many malware writers and therefore Eset displays.

@itman, The LiveGrid problem has not occurred anymore, but at irregular intervals the update of the virus signatures hangs, but I see the big picture what have been so many bugs in Eset in recent months and therefore I ask myself, how far can I trust an AV which has had and has had various errors for months? @Marcos, please do not forget that here is only a very small part of the Eset users, I read on various pages that users have the same problems, also here in the Eset forum.

Meal, also in the above version there is the update problem of the virus signatures, the screenshot is now running for about 30 minutes, then the LiveGrid problem which occurred a few days ago and was also reported here, what is still coming and that with an AV? Not good, can you trust such an AV where problems have existed for months? Also the log problems reported months ago already exist over several builds! Can you still trust such an AV? I'm not so sure if you can still do this, can they answer from Eset me the answer, if you can trust an AV that has been having problems for months? UNd yes, I have already reinstalled Eset twice, then it runs for 1-2 days and then the same errors happen again.

Is exactly the same system and nothing has been changed about it. Why should the problem have been because LiveGrid is supposed to have blocked something, I don't think so.

Has to report something pleasing, since today the Live Grid goes again as if by magic, but my feeling apparently has not been deceived that it is due to Eset.

I will think about it, because so far I am not convinced that the installation is damaged, because since others also have this error, I think more in the direction that the module has problems with some PC's.

And now?