If a scheduled task refers to an executable file w/o a path, and a startup directory is specified, Autoruns assumes the EXE is placed within the startup directory (it doesn't) and thus falsely reports the task a file not found.
In my example, I launch javaw.exe w/o a path since it changes with each java version. The task itself is valid since java is within the system PATH.
All autoruns does is try to get the file path associated with the tasks and display it for you. If it doesn't find it then it shows the warning. That is expected and there are other cases where a scheduled task (or any process for that matter) won't have a file path. It is just alerting you to something that you might want to look into. If that case is fine then just ignore it.
2 people are following this question.
