Task Scheduler 0x1 Error on Windows 10/11

The 0x1 error in Windows Task Scheduler usually means that a scheduled task started but the program or command did not complete as expected. The task may show a status such as The task has completed with exit code 0x1, even though the same program works correctly when launched manually.

This problem is often caused by an incorrect program path, missing Start in information, permission issues, incorrect arguments, or differences between running a program manually and running it through Task Scheduler.

The following methods can help you troubleshoot and fix the Task Scheduler 0x1 error in Windows 10 and Windows 11.

Method 1: Check the Action and Program Path

The first thing to check is the action configured for the scheduled task.

1. Press Windows + R.
2. Type:

taskschd.msc

3. Press Enter.
4. Find the task producing the 0x1 error.
5. Right-click it and select Properties.
6. Open the Actions tab.
7. Select the configured action.
8. Click Edit.

Check the Program/script field carefully.

For example, if you are running a script or application, use the complete path to the executable instead of relying on Windows to find it automatically.

Instead of:

python

you may need to use the complete executable path, such as:

C:\Path\To\Python.exe

The exact path depends on the application installed on your computer.

Also check the Add arguments field and make sure the arguments are correct.

After making changes, click OK, save the task, and select Run to test it.

Method 2: Add the Correct Start In Folder

A missing working directory is one of the common reasons a task works manually but fails through Task Scheduler.

This is especially important for scripts that use relative file paths.

For example, a script may expect a file in the same folder as the script. When you run it manually, the application may automatically use that folder as its working directory. Task Scheduler may start the program from another location.

To specify the working directory:

1. Open Task Scheduler.
2. Right-click the affected task.
3. Select Properties.
4. Open Actions.
5. Select the action.
6. Click Edit.
7. Locate Start in (optional).
8. Enter the folder containing the program or script.
9. Click OK.
10. Run the task again.

For example, if your script is stored in:

C:\Scripts\Backup

you can enter:

C:\Scripts\Backup

in the Start in field.

Do not include quotation marks around the folder unless they are actually required by the configuration.

Method 3: Check File Paths and Permissions

Task Scheduler may run a task under a different user context or with different permissions than when you launch the same program manually.

Check whether the account running the task can access:

• The program.
• The script.
• Input files.
• Output folders.
• Network locations.
• Required configuration files.
• Temporary folders.

Avoid using mapped network drives such as:

Z:\Backup

when possible.

A scheduled task may not have access to the same mapped drives available in your interactive Windows session.

Instead, use the full network path if appropriate, such as:

\\Server\Share\Backup

You should also make sure the account running the task has the necessary permissions for the destination folder.

Method 4: Run the Task With the Correct User Account

The task may be configured to run under an account that cannot access the required files or applications.

To check the account:

1. Open Task Scheduler.
2. Right-click the task.
3. Select Properties.
4. Open the General tab.
5. Check Security options.
6. Review the user account under which the task is configured to run.

If the task requires access to protected files or system resources, consider enabling:

Run with highest privileges

You can find this option on the General tab.

After changing the setting:

1. Click Apply.
2. Click OK.
3. Right-click the task.
4. Select Run.
5. Check whether the task completes successfully.

Only enable elevated privileges when they are actually needed.

Method 5: Check Task Scheduler Conditions

Task Scheduler can prevent a task from running correctly because of its configured conditions.

Open the task’s Properties window and select the Conditions tab.

Review settings related to:

• Idle state.
• AC power.
• Battery power.
• Network availability.
• Other system conditions.

For example, a task configured to run only when the computer is idle may not behave as expected when manually tested.

You can temporarily relax unnecessary conditions while troubleshooting.

Also open the Settings tab and review options related to task execution, such as whether the task can be run on demand and what should happen if the task fails.

After changing a setting, save the task and test it again.

Method 6: Test the Command Outside Task Scheduler

Testing the command manually can help determine whether the problem is caused by Task Scheduler or the command itself.

First, open Command Prompt.

Press Windows + R, enter:

cmd

and press Enter.

Then manually run the same program or command configured in Task Scheduler.

If the command also fails from Command Prompt, the problem is probably with the program, script, arguments, or file paths rather than Task Scheduler.

For scripts, you can also create a simple batch file to make the command easier to test.

For example:

@echo off
cd /d C:\Scripts\Backup
your-program.exe your-arguments
pause

The cd /d command changes the working directory before starting the application.

If this works correctly from Command Prompt but fails from Task Scheduler, review the task’s Actions, General, and Conditions settings carefully.

Method 7: Check Task History and Event Logs

Task Scheduler can provide useful information about what happened when the task was executed.

To check task history:

1. Open Task Scheduler.
2. Select the affected task.
3. Open the History tab.
4. Review recent events.
5. Look for warnings or errors around the time the task ran.

You can also check Windows Event Viewer.

Press Windows + R, type:

eventvwr.msc

and press Enter.

Review relevant Windows logs for errors occurring at the same time as the scheduled task.

The additional information can help identify whether the problem is related to permissions, application startup, missing files, or another configuration issue.

Method 8: Recreate the Scheduled Task

If the task has been modified many times and you cannot identify the incorrect setting, recreating it can sometimes be easier than troubleshooting every option.

Before deleting the existing task, record its important settings, including:

• Program or script.
• Arguments.
• Start-in folder.
• Trigger.
• User account.
• Conditions.
• Required privileges.

Then create a new task with the same basic configuration.

To create one:

1. Open Task Scheduler.
2. Select Create Task or Create Basic Task.
3. Configure the trigger.
4. Configure the action.
5. Set the appropriate user account.
6. Review the conditions and settings.
7. Save the task.
8. Right-click it and select Run.

If the newly created task works, the original task likely contained an incorrect or conflicting configuration.

Conclusion

The Task Scheduler 0x1 error is commonly related to how a program or script is launched rather than the Task Scheduler service itself. Incorrect paths, missing working directories, permissions, user accounts, arguments, and task conditions can all cause a task to fail even when the same program works manually.

Start by checking the Actions tab and making sure the program path, arguments, and Start in folder are correct. Then verify the account and permissions used by the task. If the problem continues, test the command manually and examine Task Scheduler history or Event Viewer for additional information.

If the configuration is difficult to identify, recreating the task with a clean configuration can be an effective final troubleshooting step.

FAQs

1. What does Task Scheduler error 0x1 mean?

Error 0x1 generally indicates that the scheduled command or application returned an error or did not complete successfully. The exact cause depends on the program being launched.

2. Why does my scheduled task work manually but fail with 0x1?

A task can run differently under Task Scheduler because it may use a different working directory, user account, permissions, environment variables, or access to mapped drives. Checking the Start in field and program path is a good starting point.

3. How do I fix Task Scheduler 0x1?

Check the program path, arguments, Start in folder, user permissions, task conditions, and privilege settings. Then manually test the command and review Task Scheduler history for additional errors.

4. Should I enable Run with highest privileges?

Only enable Run with highest privileges when the program or script actually requires administrator permissions. It is not necessary for every scheduled task.

Quick Summary

• Check the program path and arguments in the task’s Actions tab.
• Add the correct Start in folder when the program uses relative paths.
• Verify the user account, permissions, and required privileges.
• Test the command manually and use Task Scheduler history or Event Viewer to identify remaining problems.