We need to add an installer to the Block Executable policy, but wildcards are not allowed in the executable name, so we would have to monitor and update the policy every time a new version is released... or is there another way?

Example:

AppInstaller-1.0.exe

AppInstaller-1.1.exe

It would be ideal to be able to block 'AppInstaller-*.exe' so that both of these versions, and any future releases (AppInstaller-1.2.exe) are automatically taken care of.