Kucing Hitam 1 Posted October 20 Share Posted October 20 I would like to create a rules to block ccleaner connection but when I go to Firewall Rules - Add Rule - Local - Application, I cannot add the application because it does not appear on ESET Windows. This problem occur after update to version 15.0.16.0. The same problem also occur with hips rule editor. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 3,881 Posted October 20 Administrators Share Posted October 20 I see the problem, however, I can't reproduce it neither with the release nor pre-release update channel selected. Entering a full path to the file should work around the issue. Please provide logs collected with ESET Log Collector so that I can check the version of modules that you have. Quote Link to comment Share on other sites More sharing options...
Most Valued Members peteyt 219 Posted October 20 Most Valued Members Share Posted October 20 38 minutes ago, Kucing Hitam said: I would like to create a rules to block ccleaner connection but when I go to Firewall Rules - Add Rule - Local - Application, I cannot add the application because it does not appear on ESET Windows. This problem occur after update to version 15.0.16.0. The same problem also occur with hips rule editor. Is this just for ccleaner or does this occur if trying to add another .exe Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 3,881 Posted October 20 Administrators Share Posted October 20 6 minutes ago, peteyt said: Is this just for ccleaner or does this occur if trying to add another .exe The file type is wrong so it affects the listing of any folder. A weird thing is that I can't reproduce it neither with release nor pre-release module updates. Quote Link to comment Share on other sites More sharing options...
Mr_Frog 2 Posted October 20 Share Posted October 20 (<b>.exe) Looks like there is bug in filter. Quote Link to comment Share on other sites More sharing options...
ESET Insiders yeoldfart 41 Posted October 20 ESET Insiders Share Posted October 20 maybe a stupid idea: can you try to work around this by blocking cc in Windows firewall ? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 3,881 Posted October 20 Administrators Share Posted October 20 As I wrote, it's easy to work around it by entering or copying & pasting the complete path to an executable. Does somebody else have an incorrect type filter with "<b>" in the rule editor? I can't seem to reproduce it. Quote Link to comment Share on other sites More sharing options...
Solution Kucing Hitam 1 Posted October 20 Author Solution Share Posted October 20 The problem is now solved. After I switched to the pre-release update, it is back to normal. Thank you everyone. Aryeh Goretsky 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.