When I run an executable located on Storage Spaces disk that requires incoming network connections, the Windows firewall incorrectly determines the full executable path.
- the actual path is
- syntactically incorrect firewall path is
The rule does not match any running program and thus the
test.exe is never allowed to receive incoming connections.
The problem can be fixed by editing the rule manually, but I would like to know why this is happening and how to fix it without having to resort to manually editing the firewall rule each time.