Why did windows change the elevation requirements of my AutoHotKey script, and how can I prevent such in the future?
- by monsto
I was working on an AutoHotKey (AHK) script to create prefab mouse movements for a very simple model viewer. I worked on it for a good hour. I zipped the script, posted it to a forum, and thought "oh hey, I should add bla bla bla to the script".
When I returned to the program, the AHK script would not work. I could see the mouse movements working in other programs (notepad, chrome, etc), but not where I had been working the previous hour.
After several hours of throwing darts at the troubleshooting wall, I discovered that the fix was to set the AHK.exe to Run as Administrator.
The question here are multiple
Why did Windows 7, in all it's wisdom, suddenly decide that elevation was necessary in the middle of usage?
Can these permission requirements somehow be reverted by, say, removing a key from the registry or something?
How can this kind of Windows behaviour be avoided in the future?
