failed to create firewall rule

[thomas.haslwanter 0]

I need to give a sensor on my WLAN access to my computer, and therefore have to open the firewall for that sensor. To do so, I

configure the firewall to run in "Filtering Mode: Interactive mode". This way I get asked what to do when a new connection appears.

The problem: after a few rules have been created, the "Interactive mode" spits the dummy, and does not allow me to create new rules (see the attached picture). When I log out and log in again, the "Interactive mode" works for the next few connections, before the same problem happens again.

Has anybody else experienced that problem? And is there anything I can do?

BTW, I am running "Eset Internet Security 13.0.24.0"

[Marcos 5,453]

What operating system do you have? Did you get an UAC prompt window after clicking Allow and confirmed by clicking Yes?

[thomas.haslwanter 0]

OS Name    Microsoft Windows 10 Pro (64-bit)
Version    10.0.18362 Build 18362

And yes, I do get an UAC-promt for every new connection. The first few typically work, and after about 5 prompts I get the Error Message - consistently.

 

[itman 1,801]

If you are using the Eset firewall Interactive mode to setup all your firewall rules initially, a better way to do this is to use Learning mode for a couple of system boot cycles. You can then delete any auto created rules you don't want. Then switch to Interactive mode.

This way, firewall rule creation should only occur on an exception basis; i.e. a few rules created when a new app is installed for example.

Quote

 

I need to give a sensor on my WLAN access to my computer, and therefore have to open the firewall for that sensor. To do so, I

configure the firewall to run in "Filtering Mode: Interactive mode". This way I get asked what to do when a new connection appears.

 

I assume the first thing occurring is Eset alerting about that new connection? You then have to specify what profile to use; Home/Office or Public. At that point, you can then switch the firewall to Learning mode and let Eset auto create all the rules for that connection. Note: you will have to change the Eset:

Known networks -> Protection type of new networks setting, from "Use Windows settings" to "Ask user"

if currently set as such.

What I am confused about is the Eset default firewall rules for be adequate for that new sensor created connection.

Edited February 13, 2020 by itman

[Marcos 5,453]

This is a known issue, it's already fixed in 13.1 which is currently available for Insider program members.

[YFNP 1]

I have recently been having the failed to create rule issue, so I tried a few things and eventually hit upon this.  It seems that part of eset is trying to run with less than full admin level powers.

1- go to directory eset is installed into, such as "C:\Program Files\ESET\ESET Security" for smart security.

2- locate the gui interface, such as for smart security, "egui.exe".

3- right click on it / properties / compatibility / set to run as administrator.  apply.  ok.

4- right click on it again, copy.

5- find empty spot on desktop.  right click.  paste shortcut.

6- run the shortcut, to make sure it is running.

7- task manager, however you get to it, Ctrl-alt-del or right click task bar or whatever.

8- locate the eset gui in task manager and 'end task' on it, to make sure the process is ended.  running the shortcut the first time makes sure it was running so that you can find it to end it.

9- run the shortcut again.  now when it runs, you should be able to get the popups to create rules.  and at least for me now, until eset updates again, I have to keep the gui running minimized in order to be able to get the popups to create rules.

It is what I did and what works for me.  posting here in case at a later point someone else gets the same issue and wants a possible fix to try.  sometimes finding a part of a program component and selecting it to run as administrator in properties gets around windows hiccups.

[Marcos 5,453]

If the above needs to be done then there's something wrong with the permissions of the currently logged users. If the user is actually an administrator and not a standard user, I'd suggest raising a support ticket to find out the root cause of the issue.

[Cinohee 0]

On 3/15/2020 at 9:11 PM, YFNP said:

I have recently been having the failed to create rule issue, so I tried a few things and eventually hit upon this.  It seems that part of eset is trying to run with less than full admin level powers.

1- go to directory eset is installed into, such as "C:\Program Files\ESET\ESET Security" for smart security.

2- locate the gui interface, such as for smart security, "egui.exe".

3- right click on it / properties / compatibility / set to run as administrator.  apply.  ok.

4- right click on it again, copy.

5- find empty spot on desktop.  right click.  paste shortcut.

6- run the shortcut, to make sure it is running.

7- task manager, however you get to it, Ctrl-alt-del or right click task bar or whatever.

8- locate the eset gui in task manager and 'end task' on it, to make sure the process is ended.  running the shortcut the first time makes sure it was running so that you can find it to end it.

9- run the shortcut again.  now when it runs, you should be able to get the popups to create rules.  and at least for me now, until eset updates again, I have to keep the gui running minimized in order to be able to get the popups to create rules.

It is what I did and what works for me.  posting here in case at a later point someone else gets the same issue and wants a possible fix to try.  sometimes finding a part of a program component and selecting it to run as administrator in properties gets around windows hiccups.

Perfect solution