Skip to content
Documentation

AutoSteps can't find executable

Symptom: AutoSteps can’t find the scripting language program after AutoSteps has been installed.

Cause: the PATH system environment variable hasn’t been updated

Section titled “Cause: the PATH system environment variable hasn’t been updated”

AutoSteps starts the program that runs your scripts, for example AutoHotkey, by its file name. Windows then looks for the program in the folders listed in the PATH environment variable. When you install such a program, make sure that the program’s installation folder has been added to the PATH variable under System variables in the Windows environment variables.

AutoSteps reads the PATH variable only when it starts. After you have saved the updated PATH variable, restart the computer. Alternatively, exit AutoSteps from its notification area icon, sign out of Windows and sign in again, and then start AutoSteps again.