Our product relies on modifying VERSION resource information on the setup.exe to personalize the installation for our customers. Everything worked fine until we purchased IS 2018. The setup.exe built in IS 2018 becomes unusable (size changes from 8Mb to 1.2Mb). On top of it after installing IS 2018 our IS 2010 deactivated itself so we no longer can build installation packages for production. Please help! ... View more

Recently I started getting errors about signing the .msi package when building installation. Before anyone suggests invalid certificate or credentials - we use the same certificate and credentials for all other installations projects and they all build correctly. The only project that fails is "mothership" installation that contains few sub-installations and a launcher (which are all successfully build with the same signing certificate). If I disable the packaging of the installation into a single setup.exe file, the .msi appears to be correctly signed. The installation build succeeds if I disable signing of the .msi package and only sign setup.exe Here is how the end of the build log looks like: ---------------------------------------------- Media table successfully built Started signing certificate.msi ... Successfully signed: certificate.msi Performing Upgrading and Patching Validation Started signing MyProduct.msi ... Successfully signed: MyProduct.msi ISDEV : error -6258: An error occurred extracting digital signature information from file "C:\...\DiskImages\DISK1\MyProduct.msi". Make sure the digital signature information provided in the IDE is correct. ISDEV : error -6003: An error occurred streaming 'C:\...\DiskImages\DISK1\MyProduct.isc' into setup.exe ---------------------------------------------- My only idea is that I added .NET 4.0 prerequisite to few sub-installations, which resulted in bigger installation package footprint and this somehow resulted in this error. Any suggestions will be highly appreciated. ... View more