PDA

View Full Version : UAC msg in one dir but not another



NewsArchive
09-21-2010, 01:49 AM
I must be missing something.

I have a real simple sb7 install. The install, uninstall, and app are
code-signed and the app is manifested as asInvoker.

If I install to the default folder of c:\cosmetsbh, I get the UAC message
when starting the app. If I change the default folder to c:\cosmetxxx,
rebuild and rerun the install and run the app, then I don't get the uac
message. Change the default dir back to cosmetsbh and now I get the uac
message when the app runs.

Any thoughts?

Skip

NewsArchive
09-21-2010, 01:52 AM
Skip,

> I must be missing something.
>
> I have a real simple sb7 install. The install, uninstall, and app are
> code-signed and the app is manifested as asInvoker.
>
> If I install to the default folder of c:\cosmetsbh, I get the UAC message
> when starting the app. If I change the default folder to c:\cosmetxxx,
> rebuild and rerun the install and run the app, then I don't get the uac
> message. Change the default dir back to cosmetsbh and now I get the uac
> message when the app runs.
>
> Any thoughts?

Perhaps there is still a Windows "program compatibility" setting (with "Run
this program as an administrator" enabled) on that machine from an old
version of your app located in c:\cosmetsbh? You can check this by
righ-clicking the app and selecting the Compatibility tab.

Friedrich

NewsArchive
09-21-2010, 01:54 AM
BTW, I have attached a screenshot.

The testmesb7.exe is a "asInvoker" manifested application located in
c:\cosmetsbh. If you mark the "Run this program as an administrator" then
this will always trigger the UAC-elevation prompt when it is started from
c:\cosmetsbh. The same app started from c:\cosmetxxx does not give the
UAC-prompt.

Even if you remove the file from c:\cosmetsbh and add it again, Windows
"remembers" the compatibility mode setting and will always start it
elevated.

Friedrich

NewsArchive
09-21-2010, 01:54 AM
Thanks Friedrich.

That was it. I thought that I had checked that last night, but it was
late.....

Skip

NewsArchive
09-21-2010, 01:55 AM
> That was it. I thought that I had checked that last night, but it was
> late.....

:-)

Friedrich