Likely i don't understand the problem, but i'd start with an "install directory" action in the "install" section followed by "launch executable" under "launch".

If it's an EXE that you want to install - for example the iPrint Client you have shown above - you should use the "Install Executable" action in your bundle. That uploads the EXE file to ZENworks and the server will deal with distributing it during the install.

If it is just an EXE that needs to run then use the "Install File(s)" action to copy it to the machine, and then use the "Launch Executable" action to run it.

Either option Mathias Braun or Matt Jones  will work in your case.

1. If it's an installer, and it's a single exe, use the Install executable as Mathias mentioned under Install Action.
   
   
2. If it's a standalone exe, you can also use the install executable under the Launch, so you can update it in zenworks content store if necessary, and zen agent will cache it.  Caveat to note, go into the options under Install or Launch for run once and disable.  If you don't disable the default, it will only run one time then user will think it's broken next time unless you have them always right click and repair.

Found out what was tripping me up as that was what I was doing.

A Windows update that ZPM thinks it needs, but keeps hanging up, Windows Updates don't think it is needed, and it is getting in the way until I manually removed my test station from it being applied.

If this isn't a problem on the other systems, several others should show as being updated tomorrow, and if so I can roll out to all while also trying to dig into this odd issue as I see evidence of it happening on other systems.  sigh