There are three solutions to this problem:
- Completely Disable UAC – Not the best solution for security purposes, but it works.
- Compile your script to an executable.
- Hack the registry and add “Run as Administrator” to the context menu.
All you have to do is right-click on the script, choose “Compile Script”…

And now you can run the executable version as administrator:

This isn’t the perfect solution, however. I edit my script all the time, so having to recompile each time I make an edit… would get annoying.
Manual Registry Hack for AutoHotkey “Run as Administrator”
Open up regedit through the start menu search or run box, and then browse down to the following key:
HKEY_CLASSES_ROOT\AutoHotkeyScript\Shell

Right-click on “Shell” on the left-hand side and create a new key called “runas”, then create a key called “Command” below it. Then create or set the following two values on the right-hand side, adjusting the path if necessary.
Name | Value |
(Default) | “C:\Program Files\AutoHotkey\AutoHotkey.exe” “%1″ %* |
IsolatedCommand | “C:\Program Files\AutoHotkey\AutoHotkey.exe” “%1″ %* |
Now when you right-click on an AutoHotkey script, you’ll see the option to Run as Administrator:

Article stolen word-for-word from http://www.howtogeek.com/howto/windows-vista/add-run-as-administrator-for-autohotkey-scripts-in-windows-vista/
ReplyDelete