How to avoid placing installer files in roaming profile

[sjstreeting]

We'd like to avoid putting any of the installer files in the user's roaming profile, as some users have complained that we're clogging up their log off / log in times with installers.

We already changed the installer settings so that "Updater > Downloads updates in this folder" is set to "[CommonAppDataFolder][Manufacturer]\[ProductName]\updates\". This works and the self-executing EXE is downloading into C:\ProgramData instead of the roaming profile. However after the upgrade is complete we find an MSI file in "[AppDataFolder]\Roaming\[Manufacturer]\[ProductName] [Version]\install". I assume this is being created by the EXE installer when it runs.

I've searched but can't find any setting to control this. How can we prevent the roaming profile being used like this?

[Bogdan]

Hi,

Yes, this is the folder where the setup EXE extracts the files it used to run the installation.
You can easily change this extraction folder from Media page, under "Extraction folder" control. We recommend a unique parameter
to be used in the extraction path, like [ProductVersion], so each new package has a different path, this way you can avoid certain unwanted upgrade scenarios
that could break the installation of the new version.

Regards,
Bogdan

[sjstreeting]

Ah, excellent thanks, I missed that. I'm just going to change [AppDataFolder] to [CommonAppDataFolder] in this path, so it keeps all the unique bits that are already there.