Summary
With the deprecation of SHA-1 certificates, signed installations require SHA-2 signatures to be validated on newer Windows OS.Symptoms
With the deprecation of SHA-1 certificates, signed installations require SHA-2 signatures to be validated on newer Windows OS. On the other hand, Vista/Server 2008 and earlier OS will not validate SHA-2 signatures. Therefore, to support a signed installation that can be validated both on Vista/Server 2008 and newer OS, executables will need to be dual signed with both a SHA-1 hash and a SHA-256 hash using the SHA-256 certificate. Currently, InstallShield does not have the ability to dual sign during build.Cause
| An enhancement request for this feature has been submitted and is pending review from our Engineering team. The issue is being tracked under issue #IOJ-1749020. |
Workaround
Currently, the workaround involves performing dual signing with Microsoft's signtool.exe after build. This can be integrated into the InstallShield build process by including the signtool calls as a Postbuild Event.Additional Information
For information regarding installers and dual signing, please refer to the Microsoft article Windows Enforcement of Authenticode Code Signing and TimestampingFor information regarding Postbuild Events, please refer to our HelpNet article Postbuild Event Dialog Box
Was this helpful?
Related Articles
Windows agent fails to verify if signing certificates are revoked if connections to the public Internet need to go through… 1Number of Views Error may appear in beacon-services.log files: "Error occurred while saving the log file. Exception: {0} Stream does not s… 12Number of Views Frequently Asked Questions: How do I gather log files and information for the Snow Support team? 177Number of Views FlexNet inventory (ndi) files fail to upload when the user name contains a hash (#) character 4Number of Views How To: Send Support a Snowpack 957Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
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. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Revenera Assistant
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago