Thank you for responding
@mikeyww. There must be something else happening on my end, because it still doesn't work. I copied the AHK startup Registry entry directly into a Windows Command window. It launches the script perfectly, so I know the pathnames are correct. But for whatever reason, it does not launch the AHK when I reboot my system. I don't know
This morning I created a workaround for launching the AHK files. The registry is fine with launching EXE files. I update certain AHK files frequently, so recompiling each AHK into a Registry friendly EXE after each script update would be a pain. So, I created a new script to launch AHK files at start. I compiled this script launcher, created a Registry entry for it, and now I won't have to recompile the script launcher unless I need to change which AHK scripts I want starting with the system at boot. It isn't perfect, but it is better than compiling each AHK after and update.
To anyone else who might have a need for it:
Code: Select all
DetectHiddenWindows, On
;Allows you to hide the CMD window. If you won't be hiding your CMD window, then no need to add this line.
SetWorkingDir, C:\Program Files\AutoHotkey\
Run, %ComSpec% /c ""C:\Program Files\AutoHotkey\AutoHotkey.exe" "C:\path_to\script.ahk"",,Hide,
ExitApp
