.tmp file name in the vista secure desktop prompt

[pg.g...@gmail.com]

Hello,

I have a bootstrapper executable (setup.exe), which in turn, executes
an msi package stored in the executable. When I run this executable
under an admin account on Vista, I get the secure desktop prompt. This
prompt has a .tmp file name on it. I was hoping that the name would be
setup.exe and not a temp file name. Does anybody know why this happens?

Thanks.

[Rob Hamflett]

I've seen this before, too. My exe acted as you described when I ran it from a server, but as
desired when I ran it from the desktop. I guess the UAC prompt uses the real file name, and if
you're running something from a remote machine Windows makes a local temp copy. I'm not sure if my
theory is correct or if that explains what you're seeing. I can see how it's more secure, but
somewhat annoying to the developer and probably useless to the user.

Rob

[Phil Wilson]

If Windows Installer runs a custom action from the binary table of the MSI
file it will get a .tmp extension when extracted and run.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
<pg.g...@gmail.com> wrote in message
news:1164948439.1...@f1g2000cwa.googlegroups.com...

[pg.g...@gmail.com]

I am running the setup.exe from the local hard drive. There seem to be
no custom actions executed at that point. This is just launching of the
executable. I confirmed that by launching the setup.exe as a user.

The temporary file name begins with 1st three characters of the real
filename. When I click on the details, I see the full file path as
below. The temp file name keeps changing everytime I double-click the
executable.
set6E17.tmp
<publisher's name>
"C:\Temp\setup.exe"

I am not able to locate set6E17.tmp file in %TEMP%, %TMP%, and
%WINDIR%\Temp.

[Jeff Henkels]

The file may be in your user's temp directory -- i.e. c:\documents and
settings\user\local settings\temp.

<pg.g...@gmail.com> wrote in message
news:1165000120.8...@j72g2000cwa.googlegroups.com...

[pg.g...@gmail.com]

The setup.exe is copied to %WINDIR%\Temp\ and not local temp directory.

I found a way to get rid of it. When signing the setup.exe, if a
signing description is provided, then that description shows up on the
consent/elevation prompt.

signtool sign ....... /d "My Signing Description"

[mgama]

Out of curiosity, what self-extracting bootstrapper technology are you
using?
Installshield Package For The Web?
IExpress?
WinZip?
Stuff/Setup.exe from the Platform SDK?
Your own written one?
Other?

Thanks
Mike

<pg.g...@gmail.com> wrote in message
news:1165005961.3...@l12g2000cwl.googlegroups.com...

[rookie]

Its too late to answer now. But I just noticed this.

Setup.exe is our own written. Does it matter?

Thanks.