Digitally sign the original MSI, include the public cert in the MsiPatchCertificate table, and then sign the MSP with the same certificate.
<PatchCertificates> <DigitalCertificate Id="MyCompany" SourceFile="MyCompany.cer"/> </PatchCertificates> And in the wixproj, <Target Name="SignCabs" DependsOnTargets="UsesSignTool"> <Exec Command=""$(SignToolPath)" sign /t http://timestamp.digicert.com /a "%(SignCabs.FullPath)"" /> </Target> <Target Name="SignMsi" DependsOnTargets="UsesSignTool"> <Exec Command=""$(SignToolPath)" sign /d "My App Setup" /t http://timestamp.digicert.com /a "%(SignMsi.FullPath)"" /> </Target> I use custom logic to detect the location of SignTool, but that should get you started. Note, group policy can still disable LUA patching. -----Original Message----- From: chintala srinivas [mailto:chentala.srini...@gmail.com] Sent: Tuesday, June 25, 2013 11:53 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Require admin rights to msp Hi, I have a patch(.msp) file which will works fine only if it runs from administrative command prompt on UAC on machine. Can anyone please let me know how to give admin privileges to .msp. Regards, Srinivas. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users