Why does Setup launcher made by InstallShield 2015 clone itself to temp folder?
Hi @diamondkuo ,
Installshield is doing secure installation from Installshield 2015 onwards to prevent DLL preloading attacks. So, during the installation it will clone to a random directory and install from there. Usually, after the installation the random folders will be cleared.
Can you see the behavior with /clone_wait parameter.
Pretty sure that random folder is not going to be cleared. Given /clone_wait parameter help nothing.
Besides the project Basic MSI, the InstallScript MSI project had the same problem.
I saw the extracted .msi files in the temp folder had be cleared after installation, but not setup.exe.
I'm trying to use the another InstallScript project, it seems setup.exe can be cleared.
@banna_k is correct - the clone that you are seeing created is due to changes that we made within Installshield to address dll pre loading.
We have a full knowledge article discussing this in full here:
With regards to the setup not being cleared correctly in the Temp folder, this was identified as a bug due to the hotfixes provided in the above article.
This was fixed in Installshield versions 2018 SP1 and above.
I hope that helps.
@shuntMy InstallShield 2015 SP2 installed the hotfix downloaded from the link you mentioned, doesn't fix the problem of clearing the setup.exe in random subfolder in temp folder.
Is there other hotfix?
@diamondkuo - The fix was provided as part of the Installshield 2018 SP1 release. To resolve this issue you would need to upgrade to that version.
As Installshield 2015 is due to be EOL next month, this could be an opportune time to upgrade.