Hi @Revenera_Ian  Yes we've tried disabling AV and Security Apps.  As noted this is happening on end users machines, with random frequency.  So getting and collecting data is limited.  I had not known about the /debuglog argument so yes we will be trying that. However, as also noted the msi logging /V"/l*vx C:\Temp\SetupLog.txt" did not work.  ... View more

Thinking it's systemic to Flexera/ Installshield. I'm seeing the same thing. It broke today, sometime after 4PM EST. If you still have a support license I'd ask that you open a ticket - as I am - so that we can get some eyes on this. ... View more

Came here to say the same thing.    Across projects, across machines, on different networks, all of our compiles now fail with this error.  Started signing certificate.msi ... ISDEV : error -6259: Internal build error Started signing MyProj.msi ... ISDEV : error -6258: An error occurred extracting digital signature information from file "D:\Package\CD\Build\DiskImages\DISK1\MyProj.msi". Make sure the digital signature information provided in the IDE is correct. ISDEV : error -6003: An error occurred streaming 'D:\Package\CD\Build\DiskImages\DISK1\MyProj.isc' into setup.exe Setup.exe created Started signing setup.exe ... Automatic update notification disabled   ... View more

Cary R wrote: It's possible there's some other parts that take a good long time which are candidates for some optimization. What do your build logs indicate is taking a long period of time? Am I missing something? Even with verbose mode turned on (IsCmdBld -v), I don't get a step by step breakdown of duration. Thanks for the other tips, this is exactly what I was hoping for; but yes, I too picked up on the obvious - use a fast disk, keep it all local on the fast disk, don't build stuff you don't need to. ... View more

palanisamy wrote: Both of them have different product code, product name, Upgrade code and same component code. You're using the same component code? If so that's the problem. Installer A registers component guid A to reference changes to file A. Installer B reregisters component guid A to reference changes to file B. When you uninstall A the installer tries to roll back it's changes to it's file under component guid A - which is pointing to file B. ... View more

Is this an installscript or basic msi? Are you using a setup.exe? Have you checked the properties on the behavior tab for your setupinitialization dialog? ... View more

kind of the same solution I replied below 😄 Again turn off the shared setting for that component - and again if you have more than the folder hung off that component recomponentize. ... View more

Without looking at your .ism file I'm going to guess you have sharing enabled on your registry entry component. Load your ISM and in the Installation Designer, under Organization> Components find the component responsible for creating your entries and highlight it. In the components pane on the far right, under the General list you see "Shared" set it to "No". But - if you have more than registry entries hung off this one component you may have an issue, and should consider adding components just to handle the registry entries at that point. Each time you install your app, you tell the local MSI that this entry is used by n number of apps. When you uninstall that one time - you're just telling the MSI to decrement, so it thinks there's n-1 apps still installed that need that registry entry to exist. So if you install 3 times, try uninstalling 3 times and on that last uninstall the registry should clear. ... View more