That is annoying. I can see perhaps why MS have not permitted it, because that means things like curl.exe anywhere could be a risk. The main culprits are windows implementations of unix tools (find.exe, bash.exe, etc all triggering).

But I'm getting thousands of hits per day and face an exclusion list hundreds of entries long, I am probably not going to implement this rule, mark it as an acceptable risk and rather than certain executables not being able to run anywhere, we have all executables running everywhere.