Jump to content

SlashRose

ESET Insiders
  • Posts

    327
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by SlashRose

  1. There is never an answer from Eset after such a message, in any case I and all those I know who use Eset have never received an answer to it. Would also be very desirable for me if you would get an answer from Eset!
  2. And that's exactly our problem here Marcos, you never see reported problems, no matter how much you show them to them and that's why they are not useful here, as I already wrote to their superiors!
  3. Can understand you well itman, because I feel the same way on this point
  4. itman can't explain that to him, he's always right, he's not true, but he believes it, so let's let him believe in it.
  5. That's my problem with Marcos! You're absolutely right itman.
  6. Yes the v14 is bad because it has too many errors and an AV that has many errors is not trustworthy for me! This is only a small excerpt, since the Eset protocol has not logged everything that takes place in port scans and attacks for some builds. I have had between 30 and 40 attack attempts every day since the Corona craze, before Corona came I had maybe 10 attacks in half a year, that's what I mean! And that's why it's all the more important to have a reliable AV during this time.
  7. What's the point, there are postings here about where it is also written by your colleague that it is an Eset error and not just a visual error! @peyepi8, don't really trust Eset at the moment, is just a little tip
  8. I, like you itman and others, no longer see Eset as trustworthy and where since Corona the attacks have increased a few times. This is not a fine kind of Eset.
  9. I'm curious if you're right itman. For me, the network has always been public.
  10. This error has been around for quite a while, namely since the Windows 10 May Update. I find it really, very strange that the Eset developers/coders do not notice this and this error is taken over by Eset from build to build, as well as other bugs and all this moved me to stop constantly sending logs etc. and not to engage me so much anymore,
  11. After today Eset once again stuck to the update and even after 1 hour waiting nothing changed, I doubt the reliability of Eset now more than just! The last few months are just too many errors that Eset has had since several builds and therefore I doubt so slowly the reliability of this AV's
  12. I feel the same itman, especially because rarely anything comes out of it!
  13. Then take a look at nvpn.net, in my personal opinion and experience this is the best VPN provider because there is and, above all, really has a policy above, is the fastest provider and above all has port forwording!
  14. Yes itman I had read that from you in the other topic and had also emptied the update cache, it took a while and then the problem was there again, just like with other users.
  15. And what comes from Eset's side when you send the data, that the traffic is encrypted and you don't see anything, as in my post about it, only these are rarely encrypted links, not as everyone claims, only what does the internet traffic have to do with this faulty module? Nothing.
  16. 100% there is no problem of my system, there are one or more Eset problems and these are already running through several builds as confirmed by me and other users here!
  17. No, that's not the case, Eset gets stuck and then it's not really possible to work on the PC, that's what others have already told them, so what's the point? It doesn't stop even after an hour, so what do they want to tell me here? Is it so difficult for Eset to admit mistakes, because listen to the whole thing often and what always turned out, it was eset!
  18. Yes I have the latest build right after running and namely the 14.2.24.2 and the problem as well as other reports, is not fixed in the build, unfortunately.
  19. Rather from a third party provider, they are usually better.
  20. And the Eset scans immediately for signatures after the system starts, that was the first thing I turned off, but Win Update Does not always update itself immediately after the system start, but partly also sometime during the OS operation and should Eset update itself this month, Eset's signature update hangs and therefore I also stick to my opinion, that there is a conflict between Eset and the Windows Update, especially since Eset has been having problems since Windows 10 2004.
  21. It's not about how long the OS start takes while Eset is running, it's just as fast as usual, it's about the Eset although the computer takes just 1%CPU, Eset then updates the signatures and this then takes 20 minutes and especially you can't really do anything on the PC in these 20 minutes and that's not normal and I'll stick with that!
×
×
  • Create New...