Albireo wrote:I get no error message when the EXE-file is created with "EnableUIAccess",
That should mean it was successful. You can verify by using a PE resource editor/viewer (such as Resource Hacker or PEBrowsePro) to check that the manifest resource (ID 24) contains the string
uiAccess="true".
Does it make any difference where the program "EnableUIAccess" is installed?
For EnableUIAccess.ahk itself, No. For the executable it creates, Yes. The script warns you if you are saving the file in a non-trusted location. It must be in Program Files or Windows\System32.
When I run the created exe-file, a blue UAC-window (not yellow) is opened, before the program is running.
This shows that the executable has a valid digital signature. But why are you running it as admin? That makes EnableUIAccess redundant.
Is it possible to use "EnableUIAccess" on every EXE-file I want to disable the UAC-window?
(not only converted AHK-files?)
No. It might fail if the EXE does not have an XML manifest resource, or if it does not contain the expected XML tags.
I have a program that I have to run as Administrator (reads and writes in the windows registry)
If I want to start and control that program with AHK. Must both the "Exe-program" and "AHK-file" be modified with "EnableUIAccess".
You are mistaking the purpose of EnableUIAccess. It does just as it's name implies; enables AutoHotkey to access the UI of administrative programs -
without running as admin (as stated in the forum topic). It does
not enable AutoHotkey to run as admin without a UAC prompt.
Is there any difference between running a "EnableUIAccess" created file, or to use the "Task Scheduler" to launch programs without an UAC prompts?
It does not give the script admin privileges. Since the script is not running as admin, programs launched by the script do not automatically get admin privileges either. It doesn't bypass the UAC prompt; there's just no prompt, because it's not running as admin.