Reply to thread

Message

<blockquote data-quote="ForgottenSeer 72227" data-source="post: 821916">Hmm interesting, thanks for the feedback. I&#039;ll have to try it out again and see if I can figure it out. It definitely seems strange as I&#039;ve used this rule before without any issues, but that was on the previous version of W10.Thanks [USER=77647]@davisd[/USER]!I didn&#039;t get that error when I finished creating the rule. The only other security program that I had installed on my system was OSA, but I uninstalled it before installing Eset. I also had Configure defender set to max, but I set it to default and restarted the computer before installing Eset, so either of those shouldn&#039;t have caused any issues. For another test, I reinstalled Eset and just put that one rule in to HIPS and same thing, it was going off like crazy.&nbsp; I did look at the logs and I didn&#039;t see anything strange other than Chrome, or the new Edge browser being blocked, as those were the 2 programs I tried to open after that rule was created. I did follow the step by step exactly and just copy and pasted the file paths from the instructions. The only thing that changed for me from the last time I tried Eset was I am now using W10 1903, hence why I feel like it may be the issue, but maybe there&#039;s something else at play.It&#039;s a head scratcher for sure, but I&#039;ll try it again to see if I can figure it out. If not, I can just put it in smart mode and use OSA along side it without any custom rules. You are right though, it&#039;s things like this that always bring me back to WD as it can be very annoying to deal with something like this, especially if you are following a step by step instruction that was created by the company themselves.</blockquote>

[QUOTE="ForgottenSeer 72227, post: 821916"] Hmm interesting, thanks for the feedback. I'll have to try it out again and see if I can figure it out. It definitely seems strange as I've used this rule before without any issues, but that was on the previous version of W10. Thanks [USER=77647]@davisd[/USER]! I didn't get that error when I finished creating the rule. The only other security program that I had installed on my system was OSA, but I uninstalled it before installing Eset. I also had Configure defender set to max, but I set it to default and restarted the computer before installing Eset, so either of those shouldn't have caused any issues. For another test, I reinstalled Eset and just put that one rule in to HIPS and same thing, it was going off like crazy. I did look at the logs and I didn't see anything strange other than Chrome, or the new Edge browser being blocked, as those were the 2 programs I tried to open after that rule was created. I did follow the step by step exactly and just copy and pasted the file paths from the instructions. The only thing that changed for me from the last time I tried Eset was I am now using W10 1903, hence why I feel like it may be the issue, but maybe there's something else at play. It's a head scratcher for sure, but I'll try it again to see if I can figure it out. If not, I can just put it in smart mode and use OSA along side it without any custom rules. You are right though, it's things like this that always bring me back to WD as it can be very annoying to deal with something like this, especially if you are following a step by step instruction that was created by the company themselves. [/QUOTE]

Verification