InstallShield

Hi Jonathan,

Thank you for contacting Support.

A case has been registered for your query and the case number for your reference is 05027716.

The issue cannot be addressed here as this involves confidential information such as the product details.

Please respond back to the case with requested details and we will be assisting you further.

Regards,

Sunil.

Hi Lars,

A case has been registered for your query and the case number for your reference is 05029098.

Please respond back to the case email and we will share you required steps to register an SAB license.

Regards,

Sunil.

Hi Lars,

A case has been registered for your query and the case number for your reference is 05029098.

Please respond back to the case email and we will share you required steps to install an SAB license.

Regards,

Sunil.

Hi khuntley,

I'm assuming that you are talking about a code signing certificate for a desktop application. I'm sure most vendors can work, but I've used Sectigo with InstallShield. One thing I will mention is that the use of a PFX file seems to be a thing of the past for security reasons though maybe it is still possible with other vendors. The process has become a lot more complicated and I said that with the idea that I used to use a PFX file myself. It now involves having to have a USB plugged into the machine where InstallShield resides. If said machine is a VM, logging in with applications such as RDP (Windows Remote Desktop Connection) may not work as the certificate doesn't show up under that circumstance, at least not with the Sectigo vendor and again, maybe that isn't the case with other vendors. For example, with a VMWare VM and a Sectigo certificate, you have to login with things like vSphere in a browser for the certificate to be "seen" by InstallShield and this is a Windows thing, not an InstallShield thing. Again, just another security feature of sorts and my guess being that RDP is just too open to being used by "bad people". One of the more annoying things about the new way of doing things, i.e. not a PFX file, is that there is a "smart card" popup asking for the certificate password to be entered during a "manual" InstallShield build that doesn't seem to go away unless you remain logged into the machine. Now, can that be disabled or does it occur if your build process is in a pipeline type situation, I'm not sure, but in my current situation it's only a manual InstallShield build so far. With a pipeline I would hope that this popup would not show up and hence stop the process from continuing until some kind of manual intervention. So, for now, besides some so-called caveats, I can tell you that I've successfully used a Sectigo code signing certificate with InstallShield Premium 2025 R2. I hope this helps.

We have "lost" the following computers: DKD26614W, DKL31134W and C-AZ-0020.

So I would like to remove licenses for those computer in order to generate new license for other computers.

Kind regards

Lars Hesselberg

Hi Xing,

Let us know if you are still facing this issue, so that we could raise a support request for the license checkout issue.

Regards,

Sunil.

Hi James,

Following are the options to create a single MSI image:

Option 1: Create a new Basic MSI Project (Recommended)

This is the most common and supported way.

Steps

1. Open InstallShield 2025
2. Click New Project
3. Select Basic MSI Project
4. Click Next
5. Enter:

• Product Name
• Company Name
• Version

Click Finish

When you Build this project, InstallShield generates one .msi file only.

Output location:

ProjectName\Express\SingleImage\DiskImages\DISK1\

Option 2: Convert an existing project to Single-MSI output

If you already have a Basic MSI project

Nothing special is required.

Just:

1. Go to Build
2. Select Release
3. Build the project

A single MSI will be created automatically.

Regards,

Sunil.