Has any progress been made with this? We recently had a report that one of our InstallShield setup programs won't work with Smart App Control because the MSI isn't digitally signed. I presume that MSI is the TMP file mentioned here because we don't bundle an MSI file in it.

Is the solution to create an MSI file that is digitally signed and skip the more advanced InstallShield interface?

I'm hitting the same issue as Prateek, which is not the signed MSI issue that DataAnalyzer mentioned. Preface: My installer (Basic MSI) is pretty straightforward but makes heavy use of InstallScript. All of my install files, including the msi, mst, and exe files are all digitally signed.

Here is what I've observed:

• Launch my setup.exe which explodes my .msi and other files into a temporary directory
• During runtime of my installer, InstallShield will create temporary files, e.g. MSIE9FC.tmp, when it needs to execute InstallScript
• I analyzed these .tmp files (I quickly copied them out before the automatically disappeared) and they're just DLLs, but they are NOT renamed DLLs. It's like InstallShield creates them on the fly by stitching together other files.
• These .tmp files (e.g. MSIE9FC.tmp) are unsigned which makes sense since they are created on-the-fly.
• Windows SAC will **sometimes** block loading these .tmp files causing this popup:
• 
• I do not know why SAC sometimes blocks this, but sometimes allows it.

I'm not too sure how to proceed. Are Prateek and I the only ones hitting this problem?