SlashRose
-
Posts
327 -
Joined
-
Last visited
-
Days Won
1
Posts posted by SlashRose
-
-
In build 13.2.16.0, the home network is functioning normally again!
-
Yes, very bad, but unfortunately the problem also exists in the new build 13.2.16.0 and is an Eset display error.
-
16 hours ago, itman said:
Verwendet er dieselbe Router-Verbindung wie Sie. Das heißt, verwenden Sie beide eine Wi-FI-Verbindung zu Ihren PCs?
Auch zu adressieren @SlashRose kommen, sind beide PCs mit der neuesten Eset-Version; d.h. 12.2.15?
Hello itman,
I use the Fritzbox 6490 with the latest firmware and the last Eset Build 12.2.15, it is reported in many security forums by users, so it is not only users here in the forum who have this problem, it is also in other German forums Reported this bug! -
On 7/21/2020 at 6:15 PM, r1man said:
@SlashRose Anyway, both will get resolved, is that right?
I can not tell you, because it is actually not an Eset problem, but a Windows problem, which can only be fixed by Microsoft.
-
The router is not hacked, that is another Eset problem in build 13.2.15.0 under Windows Build 2004, I also have problems with the network scan, I also reported in my Eset Many Bugs Report. So don't worry, your router is not hacked !!!
-
2 hours ago, flutterby said:
Wow - that's pretty eye-opening. Thanks for the follow up and post itman.
Yes itman is a very good one in my eyes, one with a lot of knowledge about Eset, if you have problems with Eset the best way in my eyes to ask itman!
-
6 minutes ago, r1man said:
Not in this thread. In other one with the title So many bugs....
It's about another problem, not about WMI crashes!
-
@r1manThis has been a Windows problem for a long time and runs through various Windows 10 builds.
-
I don't think that a new build will come out so quickly, they will have enough to do with ironing out the zich, zich, zich mistakes, although I would think that the best solution, because the current build is really only for the trash can!
-
itman for me the firewall has always been running in interactive mode, for me there is no change of mode, never, so it can have nothing to do with it, as I said, it is exactly the same firewall error that we had about 2 years ago had!
-
It was the first time that I had the problem with Outlook 2016
-
@itman, I believe that the error arises from the fact that Eset no longer automatically updates the signatures when booting, but that the signatures must be updated directly after booting Manuel, which is also a bug of this version.
-
This is another bug that I have already reported on https://forum.eset.com/topic/24777-many-bugs-in-eset-internet-security-132150/, as I wrote this version has errors without end, you have to have a look at the German Security Forums, there are a lot of these errors!
-
@itman that is exactly the problem with the firewall rules of yesteryear, they are created and accepted in interactive mode, but every now and then, despite approval, there is a query for the same application, but only every now and then.
-
It is exactly the same with me and with others.
-
5 hours ago, Marcos said:
Please stop trolling and turning every question or user's issue against ESET. This topic is about the firewall which blocks inbound communication in case a rule doesn't exist for the communication and you again speak about it being a bug. Please stop doing that, trolling and ranting will not be tolerated. On the other hand, constructive feedback is always welcome.
What does that have to do with trolls Marcos when I write to you that the error has already been reported in my post and I point out to you ??? Or is the translation so bad that you do not understand what is written? I ask for an answer because I won't let them call me a troll !!!!
And if you have really read my Many Eset Bugs Post, this is exactly the problem I have described, what other people have confirmed in my topic and also on other forums this error is confirmed !!!
Edit: I emphasize it again Marcos, I would like to get an answer from you because I do not allow myself to be called a troll by you just because you do not seem to understand the translation !!!
-
Can that only confirm Marcos, I also wrote this error in the Post Many Eset Bugs, you know what, because the build 13.2.15.0 belongs in the bin and not that what you did there is a nonsense for every Eset customer who pays , so many mistakes and they never end, as in build 13.2.15.0 I haven't seen Eset in about 20 years, you shot yourself completely out of it, that advertising for you on my part, got rid of it, I will Don't recommend anyone anymore !!!
-
Of course, MBAM has a real-time scanner, the services continue to run even after the real-time scanner has been switched off, so I can only recommend either uninstalling MBAM or Eset, but under no circumstances would I leave both installed, so errors are inevitable!
-
I just played today's MS Patches, nothing was blocked by Eset!
-
12 hours ago, funzee said:
I was unable to download any apps from win store and check updates for windows.
disabling protocol foltering fixed 0x80245006 for me.
I just had a look for updates in the MS Store, for me the MS Store updates work quite normally.
-
12 hours ago, itman said:
Actually, there hasn't been a Win 10 Cumulative update since ver. 13.2.15 rolled out. That happens tomorrow and then we will know if versions prior to Win 10 2004 are also borked.
So far, just checking for Win Updates works fine on win 10 1909 and Eset 13.2.15 versions.
We are going to surprise it tonight at 7 p.m., I will report afterwards, if I go to Update Search now, I am not getting an error message. I will report this evening after the patches come, I'm curious!
-
14 hours ago, mallard65 said:
It's clear from these figures, and other provided by itman, that the current public release is an utter load of rubbish!
How on earth a company of ESET's reputation released this mess into the public arena is disgraceful and worthy of a detailed report.
Don't see why I should stay with ESET, when my confidence in the company has been reduced to nil.
I am 100% there with you, I am now disappointed that you make the effort to test the software, report the errors found to the German support and all reported errors in the final, or so-called final, in my eyes nothing more than a very bad beta version is to find again + to find the errors of the previous build again, if this continues with Eset, I will also consider whether I should pay for it and that although I am an absolute Eset I'm a fan and have been using it since NOD v2, I am really very disappointed!
-
itman you are 100% right, as always great of you!
-
For me the Windows Update runs error-free, which doesn't mean anything.
Program Files\ESET\ESET NOD32 Antivirus\eamsi.dll
in ESET Internet Security & ESET Smart Security Premium
Posted
itman I have to give you a big compliment again, you are really indispensable for the board here, you really hang in here and are really a big help!