Vista/Win2k8 detect 32-bit installation programs based on a few criteria. One of it are keywords like "install," "setup," "update," etc. in the EXE name. See http://technet.microsoft.com/en-us/library/cc709628.aspx for more details.

You can add a manifest to your application with requestedExecutionLevel as shown in Add a manifest to control your application Vista UAC behavior. It'll prevent installation program detection.

Check also http://doughennig.blogspot.com/2007/12/code-signing-your-vfp-exes.html


>
>I am just trying to do some compatibility testing on a 2008 Server to ensure our products run as expected.
>
>I was surprised to find most things still actually work but have run into something which I could do with some input on. We have a number of exe's, all VFP6, and all but one of them runs ok, the one which doesnt is called install.exe and whenever we try to run it we get the dreaded 'An unidentified program wants access to your computer' message. Now I've done quite a bit of reading on the UAC and have a reasonable understanding of why its been introduced and that really all our exe's should be signed but what I cant explain is why all the other exe's run without issues. Furthermore if I rebuild the install.exe and call it something which doesnt contain Install, in my case 'Bob', it runs exactly as expected.
>
>It seems the OS is specifically restricting files named Install, has anyone seen anything like this before or have any knowledge of working around this without renaming the exe?
>
>Any help or input would be appreciated?
>
>Thanks
>
>Jon