Flexera Community

Jun 30, 2022

DigiCert is ending support for file-based code signing certificates later this year: "Starting on November 15, 2022, at 00:00 UTC, industry standards will require private keys for OV code signing certificates to be stored on hardware certified as FIP...

Sep 29, 2021

We just replaced our old Thawte 2048-bit code signing certificate with a new DigiCert 3072-bit one.InstallScript EXE builds are happy to use the new cert, but MSI builds fail unless I turn off including the Software ID tag:Started signing regid.2000-...

Jan 22, 2020

We have a CDROM format (loose files) setup distributed with a signed self-extracting EXE wrapper. We do things this way because we need to add a unique license key file to the setup for each customer.The self-extractor EXE extracts the files to a s...

Jan 15, 2020

I upgraded a Basic MSI project from IS2016 to 2019 R2.I have a custom VBScript action to read 2 values from an id.txt file that is added to the MSI separately for each customer. The custom action is set to Immediate Execution -and- under Sequence > ...

Oct 17, 2019

DigiCert is shutting down the Symantec timestamp service that InstallShield uses by default as of October 31.If you look at your EXE or MSI in Windows File Explorer > Properties > Digital Signatures, then click on the signature, then click Details, y...

Aug 29, 2022

Are you using the login for your product that lets you download and get licenses? If yes, at the top of the page you should see a "Get Support" menu item, and if you click that you should see "Open New Case" and "Case Portal". That is how you open ...

Oct 07, 2021

Thanks for the response. I worked with a helpful person in support who sent me a working self-signed certificate to compare with ours. It turns out that the code in 2019 R3 that signs the SWIDTAG had a problem with our cert which was a P7B to PFX c...

Jan 22, 2020

It is an upgraded IS 2016 MSI project that is still creating MSI files not MSIX

Jan 16, 2020

Correction: the new version of the custom action still gives the ISDEV -9018 warning, but now the action does run.Apparently upgrading from 2016 to 2019 broke the old custom action, my guess is because it originally had some InstallShield default co...

Jan 16, 2020

Thanks for the response.I upgraded to 2019 R3, re-created the custom action from scratch with the wizard, and am still getting the ISDV -9018 warning.What where your settings for: In-Script Execution and Install Exec Sequence?Did you store the scrip...

Flexera Community

User Statistics

User Activity

Amazon CloudHSM for code signing?

2019R3 - MSI - error -1027 signing SWIDTAG (signing OK with tag disabled)

Feature transfer (Access is Denied) - Windows Defender

IS2019 R2 - VBScript action = warning -9018 and doesn't run (worked in IS2016)

PSA - If code signing, you must update Timestamp server by Oct-31-2019

Re: Is that the right place to contact flexera's support after paying revenera $1000's for maintenance?

Re: 2019R3 - MSI - error -1027 signing SWIDTAG (signing OK with tag disabled)

Re: IS2019 R2 - VBScript action = warning -9018 and doesn't run (worked in IS2016)

Re: IS2019 R2 - VBScript action = warning -9018 and doesn't run (worked in IS2016)

Re: IS2019 R2 - VBScript action = warning -9018 and doesn't run (worked in IS2016)