Hi, I am releasing different versions of my application fairly often and because the version number is the part of the actual exe filename all the different versions trigger the firewall dialog when the give version is executed the first time. This is quite annoying and confuses the operators. The filenames I use are like:- myAppV1.0.0.exe- myAppV1.0.1.exe- myAppV1.2.1.exeetc etc Is there a turn off the firewall to every application which has a filename like "myAppV*.exe"? Or maybe any other way to get rid of that popup? (Using the same filename for different versions, or completly turning of the firewall is not an option) thanks!

...and stop including the version number in the executable name. The application builder will track version numbers and even autoincrement them for you, while signatures allow Windows to keep track of different versions of the same application.Doing it the way you are is inherently unreliable, error-prone and insecure.Mike...

LabVIEW

Universal firewall settings for different application versions?

Solved!

Author

Just as a follow up:

Your suggestion is optimal, it would be a hassle to roll it out on all the stands we have around the globe, so unfortunately I have to drop it as well.

The workaround I have found is executing the following command from LabVIEW: "cmd /x /c netsh firewall add allowedprogram "%s" myAPP ENABLE", where %s is the full path to the exe file. This only works if the user have admin rights. (works for me ...I know... but these rules were not set by me).

As a result the user will see the firewall dialog the first time the exe executed, but the exe will start working immediately because the firewall exception is created.

Thanks for your efforts helping me out.