Ok, I found out that there was an error in the build script - the signing process was being executed twice. The insignia does not handle the extraction of already signed engine well and the behavior is the result of it.
After removing the certificate from the extracted engine.exe, the values in the burn section of this engine.exe are left as they were. After signing the engine and reattaching it back to the bundle everything seems fine. But when installing, the bootstrapper expects that those values were zero before signing, so it zeroes them out and breaks the signature of the engine.exe. That's it. PePri -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-signing-the-engine-in-the-bootstrapper-tp7595376p7595418.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
