Installsheild cannot contact the FlexNet license server at this time. This may be due to server or network issues. you can try to reestablish the connection or exit Installsheild
Windows 11 has a new security functionality known as SAC - https://support.microsoft.com/en-gb/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003
InstallShield does not complies with Win11 SAC.
InstallScript projects or Projects with PowerShell Custom Actions create an intermediate unsigned .tmp file during installation/uninstallation action, and tries to execute the same.
These .tmp files have random names on each execution. They cannot be whitelisted with Microsoft SAC.
Since these InstallShield created temporary files don't have a digital signature, these cannot be trusted by Microsoft SAC as the publisher of the file cannot be verified/trusted.
We are expecting an esteemed organization like InstallShield to prioritize looking into this issue and provide a resolution to its users in a fast paced manner.
Attached images for reference.
Hello,
I no longer have access to my laptop with my licensed Installshield, so I cannot revoke the license.
Is there anyway I can still revoke it? I do have my activation code and serial number.
Kind regards
What vendor is compatible with InstallShield that I can purchase a certificate and get the .pfx file that would slot into the build process.
Best Answer
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.
I use a sustom command-line signing tool that requires a password popup for each file i need signed.
When building my installer, InstallShieldWizard tries to sign every .tmp file that is created in the build process and triggers a password popup for each file.
Is there a way to turn off the signing of .tmp files or any other workaround?
In the Releases > SingleImage > Signing tab, I have tried to set Exclude patterns and files to *.tmp and Include to only my .exe file. But that did not work.
Additionally, I set Sign Files in Package to No to prevent signing any package files, including temporary ones but that did not work either.
So despite these settings, InstallShield still tries to sign .tmp files created during the build process.
The issue persists after clearing the build and %TEMP% folders, as new .tmp files are generated each build.
I am using InstallShield 2024 R2 (freshly installed, no older builds).
Is there a fix for broken hyperlinks in build error codes?
Example: Error code -6090 = https://community.flexera.com/t5/forums/searchpage/tab/message?filter=includeTkbs,location&q=%22-6090%22&include_tkbs=true&location=board:InstallShield-Knowledge&collapse_discussion=true
At work we handle moved API pages by adding redirects instead of just letting the links break.
Most advice for copying a dialog was to start in Dialogs>Dialogs>All Dialogs.
Right-click on the dialog that I want to copy then select the Edit option from the context menu.
Then use the Direct Editor > Dialog view to customize it (new ID and name).
In the install script I copied the existing AskOptions function ((found in the C:\Program Files (x86)\InstallShield\2022\Script\Isrt\src folder) and modified it to become my test AskOptionsCustom function.
When I run my project, the dialog displays no options, but does display the buttons.
Further it is not skinned (which is bizarre because AskOptions is a skinnable dialog).
Is there a fundamental problem attempting to use the Dialog's Edit option for my purpose?
If I had used the "Clone" option instead, would I have had better success with that? BTW, the Clone option appears to be completely undocumented.
Any help will be appreciated.
We lost some old Azure Devops Agent to build some legacy product using visual studio .isproj project type.
Visual Studio 2022 and InstallShield 2025R2 are install on new agent, but keep failing with error: "InstallShield.targets" was not found.
Any ideas what we are missing?
Thanks
Hi,
I am using InstallShield 2020 Premier R2.
I got the code signing certificate from DigiCert and use its KeyLocker to do the code signing.
In the past, I install everything on my WIndows 7 and InstallShield can sign .mst files properly.
Now I want to do the same thing on my new laptop with Windows 11 system. I have installed the certificate on the local computer. And Windows sigetool can sign .EXE and .DLL files properly.
In my InstallShield project, I select the same certificate as the one on WIndows 7 in the "Signing" tab.
Everything on Windows 11 seems to be same as those on Windows 7. But when I built my InstallShield project, I get the following error:
Started signing 1025.mst ...
SigningHelper: error 0x80092006 while attempting to sign file
ISDEV : error -1027: Failed signing 1025.mst
How to fix the problem?
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
