As described in another topic we are wanting to allow non-admin users to patch a previously admin installed exe. Everything is working beautifully except the patch still asks for an admin password and presents a dialog saying an unknown publisher is trying to install something (even though the patch is signed with the same certificate as the one included in the patchCertificate table in the msi).
The problem appears to boil down to the following error -- extracted from the log: MSI (s) (A4:88) [10:32:42:349]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active MSI (s) (A4:88) [10:32:42:349]: Validating digital signature of file 'C:\Windows\Installer\69f22a66.msp' MSI (s) (A4:88) [10:32:42:367]: Certificate of signed file 'C:\Windows\Installer\69f22a66.msp' differs in size with the certificate authored in the package Has anyone experienced this problem? How can this arise -- we only have one certificate file? Is there a way we can check the certificate in the msi and the certificate applied to the msp are the same and valid? Any help will be greatly appreciated. Thanks, Richard -- View this message in context: http://www.nabble.com/non-admin-patching-certificate-size-problem-tp15324883p15324883.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
