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 M:\sw\test.exe
  • syntactically incorrect firewall path is D:3\sw\test.exe

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.

p1 p2

  • 1
    Any news about what can cause it ? I have had a similar issue. I am suspecting a malware trying to divert access authorisation somehow but i have no clue. I doesn't always happen but when it does i refuse access and the exe still works – RR404 Nov 5 '17 at 20:30
  • @RR404 good to hear I am not alone, but I can no longer reproduce the problem. I wouldn't worry about malware, this looks more like a bug. – Vlastimil Ovčáčík Nov 7 '17 at 12:44
  • Have you installed the windows 10 bash terminal ? I thought it might have been that causing issues with pathes – RR404 Nov 22 '17 at 20:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.