Nine days ago, I replied to your question about how to return and reactivate the license.
I'm going to rewrite the question again.
"As you explained, I tried to return the license but a screen appears that says "Offline Activation" (At the end of this email I attach the image).
I have tried several ways but I can't.
Please, can you give me detailed instructions on how to proceed?"
I just renewed my InstallShield Professional 2025 license.
The problem I have is that my provider has not sent me the new "Activation Code" and if I look at my licenses, the old code appears.
If I open installshield, it tells me that it will expire soon.
Where can I find the new "activation code"?
Using InstallShield 2025 R1, we can see that Server 2025 is now included as an OS type.in the check box screen.
However, it looks like the SYSINFO.WINNT values haven't been added to in order to support identification of Server 2025 as a valid OS?
Are there plans to add Server 2025 into SYSINFO.WINNT or is there a separate way to identify the OS?
We have tried using 2025R2 but that contains a catastrophic bug with the licensing dialog when stepping through an install created with R2 (this has been raised and confirmed as a valid bug).
Hi, I need to re-activate an InstallShield 2015 license. I have sent an email to 'offlineactivations@installshield.com' with the request string created from the InstallShield license repair tool, but I did not get any answer. Now it's 5 days ago.
I have lost the activation due to a migration of the VM from ESXi to Hyper-V.
With best regards
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.
Nine days ago, I replied to your question about how to return and reactivate the license.
I'm going to rewrite the question again.
"As you explained, I tried to return the license but a screen appears that says "Offline Activation" (At the end of this email I attach the image).
I have tried several ways but I can't.
Please, can you give me detailed instructions on how to proceed?"
Using InstallShield 2025 R1, we can see that Server 2025 is now included as an OS type.in the check box screen.
However, it looks like the SYSINFO.WINNT values haven't been added to in order to support identification of Server 2025 as a valid OS?
Are there plans to add Server 2025 into SYSINFO.WINNT or is there a separate way to identify the OS?
We have tried using 2025R2 but that contains a catastrophic bug with the licensing dialog when stepping through an install created with R2 (this has been raised and confirmed as a valid bug).
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
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. | |
