Default folder during custom action execution

[aldenlong]

I had an installation failure on one computer, that was not repeatible on another. I have a custom action executable file that is executed before files are copied to the target computer. Part of what this executable needs to do is to create a temporary file, and that attempt resulted in a system error (2 file not found). My diagnosis determined that the file is created in the default folder, and on the machine where the installation failed that turned out to be Windows\System32, where file creation is not permitted (Windows 7 32-bit). I have a solution in mind (specifying a specific path rather than using the default), but I really thought the default folder would be the one where the setup executable resided and the log file is written. Would you please comment on this? (File name is SAVE_OLD.EXE).

[Daniel]

Hello,

I'm not sure why this happens. However, if your custom action creates temporary files, then it is recommended to use the temp folder location. So, you can change the related temporary file path (within your custom action) to temp folder and see if the behavior still persist.

All the best,
Daniel