Windows 11 Task Scheduler Unable to Launch the Specified Application

Question

When setting up a scheduled task to launch an application, the task execution fails and returns result code 0x1 (program not started). If a batch script (.bat) is used instead to start the program, the script can be triggered normally, but the target program still fails to launch (double-clicking the script directly can start the program successfully). It has been confirmed that the script uses an absolute path, and the "Run with highest privileges" option is checked in the Task Scheduler. Solutions are sought to adjust the task configuration or alternative methods for scheduled program startup.

holdenstorm · Answer

When configuring the task, set the&nbsp;Start in (optional)&nbsp;field under the&nbsp;Actions tab to the directory containing your executable or script.

osmankis · Answer

"Program not started" — suggests Task Scheduler can't find or run the executable. When double-clicking the script, it starts fine. But when scheduled, it fails.

josej · Answer

This issue is a classic example of how Windows 11 Task Scheduler behaves differently from an interactive user session, and the symptoms you describe (task result 0x1, batch file runs but the target application does not) are entirely consistent with a launch-context problem, not a faulty script or executable.

Why this happens

Task Scheduler does not start programs the same way Explorer does. When a task runs, it may lack:

A valid working directory
An interactive desktop session
The same environment variables you have when double-clicking a file
Proper elevation context, even when Run with highest privileges is checked

Error 0x1 simply means the program failed to start, offering no diagnostic detail.

The most common fix: set the working directory

Many applications fail silently if the Start in field is empty.

In the task:

Program/script
C:\Full\Path\YourApp.exe
Start in
C:\Full\Path

Even when using absolute paths, this step is critical and frequently overlooked.

GUI applications must run interactively

If the application displays a UI:

Set Run only when user is logged on
Keep Run with highest privileges enabled

GUI applications generally cannot run in non-interactive sessions, which is why they fail when launched by the scheduler but succeed when started manually.

Use a launcher instead of the EXE

A reliable workaround is to launch via cmd.exe or PowerShell, which provides a predictable execution context.

cmd.exe example:

Program:
C:\Windows\System32\cmd.exe
Arguments:
/c ""C:\Full\Path\YourApp.exe""
Start in:
C:\Full\Path

PowerShell alternative:

Start-Process "C:\Full\Path\YourApp.exe" -WorkingDirectory "C:\Full\Path"

If you are using a batch file

Make sure the batch file explicitly sets its directory:

Echo off cd /d "C:\Full\Path" start "" "C:\Full\Path\YourApp.exe" exit

Then schedule the BAT file, not the EXE.

Don’t ignore security controls

Also check:

Windows Security → Protection history
Controlled Folder Access
Whether the EXE is blocked (file Properties → Unblock)

Windows Defender and SmartScreen can block scheduled launches while allowing manual ones.

Final takeaway

Task Scheduler is excellent for background or headless tasks, but it is unreliable for launching interactive GUI applications unless the task is explicitly configured for a logged-in user with a proper working directory.

In short: