SlashRose

Nein.

The VPN has been off for 5 days.

Again, this is natural all the time, it only occurs since the new build.

And also on this screenshot you can see the Live Grid does not work!

Again, you can see that it doesn't really work.

The file as seen in the screenshot is recognized, but why time LiveGrid this image from the previous post???? Marcos I had as from the log yes to be seen, the extended logging activated! @Itman, No Itman, I get as above written, neither in the Gui a warning displayed, nor in the event log, Itman you can see from the screenshot but that something is going wrong in Live Grid, but what is the question now?

Here the Screenshot! And do you notice Marcos, no matter what, it always comes that everything is ok, for what then the constant creation of the logs?

Itman the ports are all released, since the firewall will probably be a bit spinning, even that is nothing new! Itman there must be something wrong, because if Live Grid is not reachable, it is actually reported in Esets Gui, but none of it is reported.

Here Marcos. https://1drv.ms/u/s!Av0lEm2Gh_QfvXY22i0n1HF5hwcT?e=aYpZxi

Here please Marcos, have not changed anything on the settings, neither on Windows nor on Eset! eis_logs.zip

In the above version, the Live Grid does not work at all, with every new build, new surprises and once again the question, what is going on with you? From build to build bug, at some point it's enough!!!

For some time now, Eset has been doing this with some updates, even if the path hasn't changed!

Sorry Marcos, but with me it already looked the same in the v14 as with NewbyUser, it had also posted, as you know!

Who is talking about a mistake that is above? Nobody, I wrote that this already happened in the v14!

Also this error we already had in the v14, that is what I already wrote in my error message post of the v15, there are always errors taken over into the new build / version!

Had this also a few days ago, but for me it was due to the OpenVPN software, this had to be released again in the Eset Firewall, although there the rule has existed for a long time, so probably not all firewall settings are really taken over by the v15.

Also this error we had already reported here in the v14 Marcos!

Here you can see for yourself!!! This has been going on for 40 minutes now and just like in the v14, working on the PC is hardly possible! Since the whole thing has been running for over 1 year now in such a way that errors are taken over and over again in the next version, you can and must simply ask yourself certain questions and one of them is, what are their programmers doing there? And then you just get a bit upset, because after all, you also pay for certain services and expectations also quality, which is no longer given. Will the v15 now be the same as the v14, a version you can't trust?

What is that, you take over from build to build, from version to version constantly the same errors. It also hangs in this version the update of the virus signatures, then the VPN is not recognized, furthermore not all attacks in the network log are logged, that are all errors that were already in the v14, what has been going on with their programmers for some time, that can everything no longer be, for what do you actually pay money for it? It has now taken him 151 minutes to get through the update of the virus signature, again, what about their programming???

That would also interest me now.

The problem is as I already wrote that Eset shows me the attacks via the taskbar, but not as it should and is also set, in the log under network only every few days it logs!

Was translated incorrectly, meant under Log because network protection!

Probably because it shows me in the task list Marcos.

Have just never got the latest version and have immediately noticed that the old error of the network attack protocol also in this version does not show all the attacks that it should display, since it has always been set by me to display everything in this direction. A bug that has already been taken over from build to build and now also in the new version and I bet that there will also be some bugs that have been around since the last build, I will report the days. I hang the screenshot, have daily, as I also wrote in the post v14, between 20 and 30 attack attempts and look at what of them only seems to see in the log!

Marcos I use Eset, then NOD since the v2, so for many years and I never swear to you a response after submitting contaminated websites that were not blocked by Eset!