Thanks everyone for the advice ! SuppressSignatureVerification=yes worked for this user.
Another tidbit is that he was running the EXE as admin, and interestingly the UAC prompt showed "unknown" for the publisher name. When I try the same thing I see a prompt with our company name. I'm tempted to just start setting SuppressSignatureVerification=yes on our future bootstrappers, just so installation succeeds despite weird security configuration issues. Curious to know if this sounds like a bad idea. -Rob On 1/28/2014 3:27 PM, Phill Hogland wrote: > There are other similar reports on the internet which are not related to > Wix, > so the root problem is probably more along the lines that Christopher > suggested. When you recompiled did you consider using > MsiPackage/@SuppressSignatureVerification? This can happen if the machine can't contact the Microsoft servers to download the root certificate. At least on Vista, if the machine is never connected to the Internet our Burn packages won't install because the Verisign certificate isn't on the machine. I don't know if the same issue exists on Windows 7 and newer though. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/0x80096005-timestamp-signature-and-or-certificate-could-not-be-verified-tp7592055p7592253.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
