I used Autohotkey to compile an Autohotkey script and placed the compiled program in the Windows startup folder. When I start Windows, however, the program no longer runs (it used to). I also tried placing the program somewhere else and putting a shortcut to it in the startup folder.

How can I figure out what's happening and fix it?

  • Does it still run if you start it manually? Have you tried recompiling it into a new EXE? – Ƭᴇcʜιᴇ007 Jun 4 '13 at 19:20
  • @techie007, It still runs when I run it manually, I haven't tried recompiling. sfc says it found corrupt files but was unable to fix some of them. – mowwwalker Jun 4 '13 at 19:32
  • Have you done a disk check recently? – Ƭᴇcʜιᴇ007 Jun 4 '13 at 19:33
  • @techie007, I did run sfc, but it said it found corrupt files it couldn't repair. – mowwwalker Jun 4 '13 at 22:17
  • Does your program require admin rights (-> UAC)? Does your program require network drives that are not mapped any more? Are there other programs in the startup folder and are they run successfully? – Werner Henze Jul 2 '13 at 12:04

You Must be aware that some program needs Administrative privilege to start. Keeping program simply in startup folder doesn't provide the program permission to execute it.

  1. You either need to remove the Option to run program as administrator.

    • To do this, right click and go to property of the program and in Advance button of shortcut, uncheck the Run As Administrator.
    • But this may leads to app not work properly for the task it need administrator privilege.
  2. Another option is to create a scheduled task.

    • Open scheduled task and select the program in new task and execute it on every startup.
    • Since Configuring Scheduled task needs admin privilege already, so your program will be already granted admin permission.

So it will work!

  • 2
    This answer is really mixed-up and sometimes you say the opposite of what you mean (example uncheck=>check). You should correct it and supply full instructions. As it stands, it's not very useful. – harrymc Jun 29 '13 at 15:48
  • It was this. Thank you! – mowwwalker Jun 30 '13 at 6:41
  • Sorry for that but i was in really hurry situation but since i knew that answer, i should tell ans and they'll get; and they did. Next time i'll be careful :) – Dheeraj Thedijje Jul 1 '13 at 8:59
  • How may be disabling of Run as Administrator harmful to anything? The opposite action (enabling it) may be harmful for sure. Disabling it may only cause an app to stop working or behave differently. In fact, you're just decreasing rights an app have, so I cannot imagine how it may be harmful for security... – Dawid Ferenczy Sep 21 '17 at 12:03
  • Yes, my mistake, i have corrected it. :-) thank you – Dheeraj Thedijje Sep 22 '17 at 8:11

You could try referencing it directly in the registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Run

Run ProcessMonitor and capture a bootlog. Open it and look in the processTree if the exe was ever started and if yes, how long did it run. You can go to the Events and look for details in the Result column.

Watch this video from Mark at TechEd 2013:


I've looked up this issue on lots of websites in the last three days. none of them resolved the issue. Once I lowered the user account control settings, The shortcut then started up properly running as administrator.

Your Answer


By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.