Feature request: Masks for applications paths

[agronatur]

Some applications update on daily basis and like to change paths changing the folder name with their versions like: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\120.0.2210.133\msedgewebview2.exe C:\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_1.226.1187.0_x64__zpdnekdrzrea0\Spotify.exe

so if we could do something like this: C:\Program Files (x86)\Microsoft\EdgeWebView\Application*\msedgewebview2.exe C:\Program Files\WindowsApps\SpotifyAB.SpotifyMusic_*\Spotify.exe

The * would allow anything.

[camheelio]

I agree, using wildcards in the path would allow real "process-enablement". Currently even selecting a process creates a file rule limited to the exact and complete file path. And since more and more applications have it's version in the path (e.g. UltiMaker Cura, MSEdge, etc), it would allow to enable them without the need of modifying the rule after each update. Also it would cover UWP-Apps, that are not correctly placed in the group, like winget, which in theory should reside in the "DesktopAppInstaller"-UWP-Package but cannot be enabled by enabling this package. For this a simple

*\winget.exe

as file path could solve anything

[Rumpa112]

Yeah, a much-needed future. As it stands now every time an app that has a stupid version string in the path needs its firewall rule updated...