I am using Windows XP with a VS 2003 Setup project to create MySetup.msi that is digitally signed (authenticode) during compilation of MySetup.msi (checked authenticode in Properties dlg box for the Setup project and provide paths to the *.pvk, *.spc files, and the time stamp URL). I mentioned digitally signed because I don't remeber the following problem occurring before I started digitally signing the msi file. When I run MySetup.msi on a Vista Business OS, I get a UAC dialog box that ask if I want to run c46a8.msi. Publisher and version information in the UAC dialog box are correct. Why would c46a8.msi be displayed rather than MySetup.msi? Is there a way to fix this? Thanks for any comments or information. -- Gary Larimer
Is there any chance you're running it from off a remote server? When I was playing with UAC and signing I ran my signed exe from off a server, and the path the dialog reported was obviously a local copy that Windows had made in my temp folder. Rob Gary Larimer wrote: > I am using Windows XP with a VS 2003 Setup project to create MySetup.msi that > is digitally signed (authenticode) during compilation of MySetup.msi (checked > authenticode in Properties dlg box for the Setup project and provide paths to > the *.pvk, *.spc files, and the time stamp URL). > > I mentioned digitally signed because I don't remeber the following problem > occurring before I started digitally signing the msi file. > > When I run MySetup.msi on a Vista Business OS, I get a UAC dialog box that > ask if I want to run c46a8.msi. Publisher and version information in the UAC > dialog box are correct. > > Why would c46a8.msi be displayed rather than MySetup.msi? Is there a way to > fix this? > > Thanks for any comments or information.
Thanks Rob. I was running the *.msi file from a CD-ROM on a local machine. I am going to try signing the *.msi file after it has been created by the VS Setup project. I will have more control over the signcode.exe parameters. Not sure if that is the problem, but worth a try. If signcode.exe does not work, might try signtool.exe. -- Gary Larimer "Rob Hamflett" wrote: > Is there any chance you're running it from off a remote server? When I was playing with UAC and > signing I ran my signed exe from off a server, and the path the dialog reported was obviously a > local copy that Windows had made in my temp folder. > > Rob > > Gary Larimer wrote: > > I am using Windows XP with a VS 2003 Setup project to create MySetup.msi that > > is digitally signed (authenticode) during compilation of MySetup.msi (checked > > authenticode in Properties dlg box for the Setup project and provide paths to > > the *.pvk, *.spc files, and the time stamp URL). > > > > I mentioned digitally signed because I don't remeber the following problem > > occurring before I started digitally signing the msi file. > > > > When I run MySetup.msi on a Vista Business OS, I get a UAC dialog box that > > ask if I want to run c46a8.msi. Publisher and version information in the UAC > > dialog box are correct. > > > > Why would c46a8.msi be displayed rather than MySetup.msi? Is there a way to > > fix this? > > > > Thanks for any comments or information. >
Found problem -- needed to add a friendly name to the digital signature. If no friendly name then Windows appears to use auto generated character for the file name, hence c46a8.msi instead of MySetup.msi. Instead of digitally signing the msi file in the VS Setup project, I used the signcode.exe wizard to digitally sign AFTER MySetup.msi was created. This allowed inputing the friendly name. Double clicking signcode.exe causes the signcode.exe wizard to appear. -- Gary Larimer "Gary Larimer" wrote: > I am using Windows XP with a VS 2003 Setup project to create MySetup.msi that > is digitally signed (authenticode) during compilation of MySetup.msi (checked > authenticode in Properties dlg box for the Setup project and provide paths to > the *.pvk, *.spc files, and the time stamp URL). > > I mentioned digitally signed because I don't remeber the following problem > occurring before I started digitally signing the msi file. > > When I run MySetup.msi on a Vista Business OS, I get a UAC dialog box that > ask if I want to run c46a8.msi. Publisher and version information in the UAC > dialog box are correct. > > Why would c46a8.msi be displayed rather than MySetup.msi? Is there a way to > fix this? > > Thanks for any comments or information. > -- > Gary Larimer
"Gary Larimer" wrote in message news:53593F9F-E4A9-4E16-90A5-AABEEB0ED3C8@microsoft.com... > Thanks Rob. I was running the *.msi file from a CD-ROM on a local > machine. I am going to try signing the *.msi file after it has been > created by the VS Setup project. I will have more control over the > signcode.exe parameters. Not sure if that is the problem, but worth a > try. If signcode.exe does not work, might try signtool.exe. This text is controlled by the description field during the signing of your MSI file. It has nothing to do with location of MSI or even the name of the file itself (although you can make the description the name of the file if you want). If you are using signtool.exe then signing parameter options related to UAC are: /d <desc.> Provide a description of the signed content /du <URL> Provide a URL with more information about the signed content. The <desc> is used in the prompt that users see. Sincerely, Adrian Accinelli
Thanks Adrian. You were right. Found problem, and corrected with signcode.exe wizard. See my next post. -- Gary Larimer "Adrian Accinelli" wrote: > "Gary Larimer" wrote in message > news:53593F9F-E4A9-4E16-90A5-AABEEB0ED3C8@microsoft.com... > > Thanks Rob. I was running the *.msi file from a CD-ROM on a local > > machine. I am going to try signing the *.msi file after it has been > > created by the VS Setup project. I will have more control over the > > signcode.exe parameters. Not sure if that is the problem, but worth a > > try. If signcode.exe does not work, might try signtool.exe. > > This text is controlled by the description field during the signing of your > MSI file. It has nothing to do with location of MSI or even the name of the > file itself (although you can make the description the name of the file if > you want). > > If you are using signtool.exe then signing parameter options related to UAC > are: > /d <desc.> Provide a description of the signed content > /du <URL> Provide a URL with more information about the signed content. > > The <desc> is used in the prompt that users see. > > Sincerely, > Adrian Accinelli > > >
