According to AI support, creating a pause during build process or re-packaging the final EXE assembly is not possible. The only option is to break it down to multiple MSI and external CAB files in order to be able to expose all the files and sign them individually.
I have an active Professional license and build driver packages that are all distributed as "Single EXE setup (resources inside)". I have recently re-branded one of my packages for a reseller and he wants to sign the MSI and CAB files included in the package with his own digital signature, without s...
Hi cosmin, Once you get the package installed, in that directory you will find a bunch of MSU file for versions 1.9 and 1.11 of the WDF ehich is exactly what you need to install on target PCs. For the earlier versions, you may notice some DLL files rather than MSU. To extract the MSU files from thos...
Hi Cosmin, They are available online as free packages for everybody to download. If you don't find some of the old ones because Microsoft might no longer maintain the webpages for those packages, you can then either download them through MSDN subscriber download page, if you have access to any, or c...
Hello Bogdan, I got the exact same results with the External Tools too !!! As I said earlier, AI doesn't seem to include the right certificate chain when signing the files. To explain it better, I have used the same SAMPLE project that was sent to me by AI team regarding a different issue, and signe...
Hello Bogdan, I'm using Advanced Installer 9.3 Professional and the only thing I can change on the "Digital Signature" page is the Signature files themselves; not the cross-certificate that AI uses to sign the files. I even used the "Use file from disk" option; but found no place to be able to ident...
Hello Bogdan, I wanted to share with you some new developments. It seems like that even though my problem got resolved, AI still doesn't sign the files properly. I did some analysis on the files that AI signs and found out that AI doesn't sign them with the proper Cross-Certificate; resulting in rej...
Hello cosmin, How about adding different versions of the Microsoft redistributable packages (.MSU) for the Windows Driver Frameworks versions 1.05 to 1.11 to the list of predefined prerequisites? Windows driver packages heavily rely on these libraries and with Windows 8 release they will become incr...
Hello Bogdan, Thanks so much for looking into this issue. The problem turned out to be rooted in the Certificate Chains that was used in the signature vs. what was recognized on that Operating System. After I updated the test PC (Windows Server 2008 R2 x64) with all the latest and greatest patches t...
Hello, I have built a "Single EXE Setup" package (Mixed 32/64) using Advanced Installer Professional 9.2 and enabled Digital Signature facility within AI to do the signing for me as it builds and packages the pieces up. Although Windows Server 2008 R2 x64 is selected as one of the supported Operatin...
Hi Daniel, Thanks much for your input as well as the sample project you posted. I have also noticed that when I'm using the "Mixed 32/64-bit matching the platform" option, the Registry changes I have made don't take place in regular branches of registry and instead go under Wow6432Node which doesn't...
