Ability to use * in HIPS/FirewallRule Path

  • Yes
  • No
0 voters

For example UWP apps -
C:\Program Files\WindowsApps\Microsoft.WindowsNotepad_11.2402.22.0_x64__8wekyb3d8bbwe\Notepad\Notepad.exe

If I update it will change version, if I could use -
C:\Program Files\WindowsApps\Microsoft.WindowsNotepad_*_x64__8wekyb3d8bbwe\Notepad\Notepad.exe is would make it easy

I tried it with C:\Program Files\WindowsApps\Microsoft.WindowsStore_*_x64__8wekyb3d8bbwe\WinStore.App.exe it works but Icon doesn’t work
Example 1

Example 2

Doesn’t work for C:\Program Files (x86)\Microsoft\EdgeWebView\Application\*\msedgewebview2.exe

I always think that wildcards in firewall and HIPS rules is a risk. You can already use it in for example, protecting a entire drive in the Protected Files by adding ?:* will cause HIPS to protect all files on all volumes and drives. Perhaps more useful for some but if your running in Safe Mode your unlikely to see that many alerts and you can set updater app popups to Treat as Installer/Updater.

If you are already involved in the manual creation of firewall rules, I think you will know if and where it is safe to use wildcards. It will save a lot of work for writing rules for paths (and filenames) that keep changing, so I am in favour for being able to use wildcards, provided their effect is reliable and consistent. By the way, possibly the reason for the icon not being shown, is because it is read from the executable via Windows functionality which apparantly does not support a wildcard in the full path to the application.