An Exe name, such as update.exe, blocked by UAC in a scheduled task

Question

I have a problem with UAC windows, scheduled tasks, and an executable file called "dbupdate.exe". I have full control over the source code, manifest, etc., but not over user systems (in short: normal software engineer ;-). Language is Delphi, but should not be important, I think.

I have a problem using the application in the task scheduler on Windows Vista and Windows 7. The program is called dbUpdate.exe. He built an xp / vista manifest that configures the launch of the "asInvoker" program.

Now, in Vista and Windows 7, I can run the program without any problems, but I have to log in. If I have not logged in, the program does not run (I use the Windows task scheduler, but I know that the problem exists with other scheduling programs). But: if I rename the program to "dbBlaBla.exe", it will be executed. Explains to me that detecting a UAC installer suggests that my program is an installer (this is not the case, but I know that it looks at file names such as update, configuration, etc.).

I searched the Internet, I could not find many useful things. Therefore I ask here

Do I need to create a special manifest for its execution in a scheduled task? Or is there a way to disable UAC for scheduled tasks or just for my executables? Or do I really need to choose a different name (then it will work, as mentioned earlier) and runs the risk that customers and my colleagues are not very happy with this? $

Thanks for any help, greetings

Answer 1

On Windows 7, a program called "update.exe" seems to require privileges. Apparently this is the name, and this is just one of these odd things from Microsoft. Renaming it to "anythingUpdate.exe" will cause a magic violation; "UpdateAnything.exe" also!

So, I renamed mine to up7.exe, and now Microsoft is calm and undeniable. The same thing happens in Vista.

So "updatedb.exe" will not work; "upd_task.exe" will be ...

Answer 2

From http://social.msdn.microsoft.com/Forums/en-US/windowscompatibility/thread/1b316a7f-852e-4a71-89d3-090e45990f98

User account control: application installation detection and elevation request must be enabled to detect the installer to detect installation programs. This option is enabled by default and can be configured with the Security Policy Manager snap-in (secpol.msc) or with Group Policy (gpedit.msc).