SlashRose

If you can hardly use your system during this time, then something is wrong with Eset and anyone who disagrees does not really seem to know Eset! But is only my personal opinion.

Itman I'll see it tomorrow. Marcos there You contradict each other, but what Mr. Peter Randziak says is that it runs with low priority and you tell Marcos now that it always runs with normal priority, get some agreement, how now? In low priority as Mr Peter Randziak says, or as you say with normal priority? Is once again Fantastic

I won't do that this time because I already know the answer!

Marcos it is a contradiction when you say that it can take up to 20 minutes and here Writes that it is an error in the changed code of Eset, is that answered?

Oh Mr. Randziak, in another post, where I just replied to them, where it is also about this error, they wrote that this is normal and can take 20 minutes, very contradictory statements from them!

Mr. Randziak, you don't really want to tell me that this update behavior of Eset is normal? No, it's not, because as you should have seen, working on Windows is almost impossible during this time, I'm always surprised by the answers when reporting errors. If you show me an AV that behaves similarly, there is none! And the system has never been under load, even with others where this error occurs, because we have no apple boxes as a PC!

I had done this a while ago, after you had written this, after that there was some time rest and now the whole thing starts again.

I have now noticed that the Eset update gets stuck whenever Windows checks for updates at the same time, so I think there is a conflict between Eset and the Windows Update!

itman that is with me in the middle of Windows operation and not only at system startup.

Today again the same problem that Eset gets stuck during the update, so slowly you should really iron out this time and not take it from one build to the next!

I had the problem 4 days ago that the Eset update got stuck again, so again one of some bugs that Eset takes into the new build despite the message!!!!

Eset has never recognized a VPN connection with me, no matter what VPN software. Because Defender , I've never used it.

Then you had a different problem like me, because with me Hing Eset gets stuck every time I wanted to release the NetBios for the VPN and that needs a VPN now and that was a clear Eset error, because I don't have in build 14.2.23.0. But even this build does not recognize VPN as a new network!

I also had a few times under the previous build.

Actually, this should not take longer than 1-2 minutes, usually takes less than 1 minute for me!

Can only fully confirm what Itman describes as in the other posting and as I wrote there, it is at irregular intervals, where only a restart remedy!

For me it occurs at irregular intervals every now and then, with exactly the same side effects as for you Itman. Everything only in the new build.

I also post a post about it, but this was misunderstood by Marcos and he was only of the opinion that it was due to OpenVPN, which is complete nonsense. Yes Eset has a VPN problem with enabling the NetBios request, and this is an Eset problem! And the VPN connection has never been recognized by Eset as it should be as a new network. I only have this problem as well as other problems since the new build 14.2.19.0, z.b. that the download of the virus signatures now and then abort the download, but not abort in the actual sense, the virus signature remains in the middle of the download and it can neither be aborted nor anything else, it then only helps to restart the PC

No, the eMule was only submitted once, everything is only submitted once, only if the same eMule has been running on the PC for 6 years, then Eset already knows it. And if I then scan the files with Eset (also offline) and then also scan the submitted files online via https://www.virustotal.com/gui/, the submitted files are also classified as clean and that is again all files that are submitted that I have had on the PC for years, so Eset already knows them. Itman doesn't bother me, I just wonder why, since like I said Eset already knows her. @Marcos, what kind of suspicious network communication?

No, because this eMule was rewritten for me personally in 2016 and has some more functions than the normal official eMule.

You're right Itman.

Itman you misunderstood something, not you posted 6 years, but I have been using Muli for 6 years and of course Eset then already knows eMule, or do you see it differently, because your opinion interests me most, because you know what you are talking about. Probably because of the translation you misunderstood!

Itman, can it really be that Eset only find a file that has been on pc for 6 years? I would find that very strange, but can this really be Itman?

Why did I know that it was the same game again, if you didn't have Itman here, then the forum would look very old, because the boy at least has something on the box! Because you don't really get help.

But not if the eMuli just like Eset that I have been running since the v2, knows this mule, that's still absurt! Because Eset already knows this eMule