Hi All,

I released an update to an application 2½ months ago. Relating to
Windows 7 and UAC, the EXE behaves correctly and as expected when
installed and executed on Windows 7. It runs with no UAC permission request.

I need to release an update now. I used the exact same SB7 script that
was used to compile the previous release to compile the new release. The
only change I made to the script was to increment the version number.

SB code signs the EXE and embeds an "AsInvoker" manifest exactly the
same as it did in the previous install(s).

When I install this update on a Windows 7 OS the icon placed on the
desktop, as well as the icons for the exe and uninstall placed in the
"Start Menu" now have the Windows 7 security shield super imposed over
the icon. When I start the app the typical UAC warning/permission screen
is displayed.

Also something I noticed that probably is a clue. When I uninstall the
previous version it runs as expected with no UAC warning but the new
version uninstall requests UAC permission.

I have verified the exe is code signed, but other than that, I haven't a
clue what to check next once the application is installed. I have
screwed something up and will appreciate *any* ideas/suggestions what to
look for to fix this. This release I am needing to deploy has a major
bug fix in it and I need to get it released as quickly as I can.

Any ideas/suggestions are most welcome.

--
*Regards*,

Lee
www.cya2day.com
CYA - Don't Leave Home Without One