Issues with folder and file visibility

[Former Member]

I am having trouble creating the rules I need because some executables are missing from Windows folders when I browse for them, even though they show up in the normal Windows Explorer window. Also, for some reason I don't understand, manually typing in a path yourself does not work when creating rules. This is odd behavior. My account is an administrator and should have access to the folders. I have also tried running Endpoint Security as an administrator, but this does not work and actual causes problems (the settings UI will not load from taskbar icon when Run as administrator is ticked in the properties). My only guess is perhaps that something is amiss with the account permissions, but I am hesitant to mess with those settings. Any assistance would be appreciated.

[Former Member]

Which rules are we talking about here?

Are these all locally based folders? If they are mapped they wouldn't show up.

[Former Member]

They are local files. Some folders and executables in the system32 folder that I'm trying to enable, because they aren't included in the core rules for operating system files for some reason. 

[Former Member]

One example is I'm trying to add a rule for taskhostw.exe in the system32 folder. It shows up in the Windows Explorer but not the list of executables in the firewall settings.

[Former Member]

Thank you for clarifying this. I've been researching this but can't see why this is happening. Do you have a Service Request open for this? I'd love to get an answer from Dev for you - if you have a case, I can link the research task for you.

[Former Member · Accepted solution]

It ended up being an issue with Windows user permissions rather than an issue with Endpoint Security. It is resolved now. Thanks.