We have this same issue, but its for some of the other custom actions launched by AdvancedInstaller. Is there a way to control where all dynamic powershell files are generated?
When scripting out custom actions, Advanced installer will automatically create powershell scripts used to launch actions in the temp directory (c:\windows\temp) with filenames like: pss1214.ps1 We would like to be able to specify _where_ these files are created so we can whitelist them with our AV ...
