When using Comodo digital signatures for signing, Comodo states there needs to be at least a 15 second delay between signing so their severs don't get hammered. They appear to be getting more and more fussy about that 15 second delay. I've had to adjust my scripts to accommodate these delays so I don't have failures. Is there a way to add a delay before signing of a user specified amount or hard code 15 seconds before signing? When I build with IS, especially via command line via scripts, I've been getting more and more errors, especially with dual signatures, because it's doing back to back requests. ... View more

Is it just me, or did the IS2016 IDE go into severe regression with the keyboard shortcuts to the clipboard working in the IDE. I filed a case - 01261269 Go to Installscript editor and select text and go CTRL-C and the paste the text elsewhere in the file. No joy. You can select text, right-click and select copy. Then right-click and select Paste. Seems like a pretty serious regression, even though there is a workaround. ... View more

January 1, 2016 is the Code Signing Armageddon. As we still have to support Windows Vista and Server 2008, we need the ability to dual sign our installer and apps. Doing the apps is easy. Doing the Single file Setup EXE is fine. But I need to be able to dual sign the MSI before it is wrapped in the Setup.EXE. Here is background on this from MS, who recommends dual signing and an article explaining as well. http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx http://zabkat.com/blog/code-signing-sha1-armageddon.htm ... View more

I have way too many XP and Vista customers that are complaining regarding our SHA256 signed installers as creating security warnings or not being allowed to download. I'm even having some XP customers complain that they are getting a Error 24592 error that a cab has an invalid digital signature and wont install. How can I continue to use IS2015 and go back to using a SHA1 digital certificate (which I now have to re-buy, since I converted my cert to SHA256). Looking around, seems like many software companies supporting XP, 2003 Server, Vista have had to downgrade to SHA1 too. ... View more

Maybe I'm missing something. Basic MSI Project with MSI 4.5 required. Setup.EXE size, with no Windows Installer 4.5 redistributables enabled is 98 Megs. So users will have to make sure they have Windows Installer 4.5 install, which for 7+ is no issue. I added XP SP3, 2003 SP2 32 and Windows Server 2003 and XP 64 bit, Vista 32 and 64 bit redistributables. Size now is 127 Megs. Ok. Bigger, but I added stuff. My thinking - Let the installer download those from the web, slimming down the size. So I went into each redist properties and changed the Build location to "Download From the Web". Size is now still around 120 Megs. That seems pretty weird. Why is this payload so heavy when I said to download from the web? Shouldn't it be more around 100-105 at most? ... View more

I'm using BasicMSI project and using a Setup.EXE to a compressed single EXE. I require Windows Installer 4.5. When installing on a computer (Server 2003 R2) that had Windows Installer 3.1 and didn't have 4.5, the Setup.EXE Extracts... Then dies. No clue why. When I did a VOICEWARMUP on the customer's computer, the log explained the situation, I upgraded the customer's Windows Installer to 4.5 and all was well. Is there a reason why the Setup.EXE can't see that and give a simple warning that this installer requires Windows Installer 4.5? I'm not including 4.5 installer to keep the payload smaller. ... View more

I've been getting a rash of these errors occurred in the field during installation. The resolution so far has been to delete the content from within: C:\Users\xxx\AppData\Roaming\Microsoft\Crypto\RSA Any idea what's going on? Customers haven't had this issue with IS2012 Spring based installs. This is Basic MSI projects. ... View more

Basic MSI project. Client has Windows 7 Home. Getting Object already Exists error. Any ideas what happened? Lance MSI (s) (74:20) [14:53:05:558]: Determining source type MSI (s) (74:20) [14:53:05:558]: Source type from package 'BLS2015INSTALL.msi': 0 MSI (s) (74:20) [14:53:05:559]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{E8B12E79-DB5F-4DDB-A27F-9B38C5667528} MSI (s) (74:20) [14:53:05:559]: SECREPAIR: SourceHash database file already exists. Deleting it. MSI (s) (74:20) [14:53:06:029]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (74:20) [14:53:06:180]: SECREPAIR: New Hash Database creation complete. MSI (s) (74:20) [14:53:06:193]: SECREPAIR: CryptAcquireContext: Could not create the default key container MSI (s) (74:20) [14:53:06:193]: SECREPAIR: Crypt Provider not initialized. Error:-2146893809 MSI (s) (74:20) [14:53:06:193]: SECUREREPAIR: Failed to CreateContentHash of the file: BLS2015INSTALL.msi: for computing its hash. Error: -2146893809 MSI (s) (74:20) [14:53:06:193]: SECREPAIR: Failed to create hash for the install source files MSI (s) (74:20) [14:53:06:193]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (74:20) [14:53:06:193]: SECUREREPAIR: SecureRepair Failed. Error code: 8009000fF85434B8 Object already exists. MSI (s) (74:20) [14:53:09:076]: Action ended 14:53:09: ResolveSource. Return value 3. Action ended 14:53:09: INSTALL. Return value 3. ... View more

Seem to be having a brain relocation moment. Basic MSI project. SetupCompleteSuccess dialog. I have the checkbox "Show the Readme File" (LaunchReadMeText) and the behavior and visibility is appropriate when installing. However on uninstall, the checkbox option still shows visible. The Show Condition for the checkbox is: (NOT Installed) and ((NOT REMOVE~="All") OR (NOT MaintenanceMode="Remove")) And (NOT ISENABLEDWUSFINISHDIALOG) Any suggestions? ... View more