How To Fix Task Scheduler (0x1) Error in Windows

The task scheduler error 0x1 is the most common error I see with windows scheduled tasks.  I have seen it on many users computers as well as my computers and servers.  I have fixed this error many times and the fix is always the same or very similar.

What causes the error?

The Task Scheduler (0x1) Error is caused because of a system path issue, your task does not run successfully because it can not find a file to run.

Sometimes the task will run and complete successfully but the task will not have actually done what you needed to do, I will go through the fixes below.

How To Fix Task Scheduler (0x1) Error in Windows

To fix the error 0x1 you need to enter a path in the “Start in (optional)” field in the edit action part of the scheduled task.

To do this follow these steps

1. Open task scheduler by clicking start and typing in “Task Scheduler” and click on the app
2. Click task scheduler library
3. Right click on the required task and select properties
4. Click the actions tab
5. Click edit
6. In the Start in (Optional) field type in the required path
7. If you are not sure what the correct path should be copy the path minus the process from the Program/Script field
8. In the example below I put c:\Program Files\Microsoft Security Client\
   
9. Click OK to close the edit action screen
10. Click OK to close the scheduled task
11. Re-run the scheduled task again
12. If you see the last run result is 0x0 then this means the task ran successfully

The below video also shows you the above process

How To Fix Task Scheduler (0x1) Error When Running Batch Files

To fix the error 0x1 when running batch files in a task scheduler you need to enter a path in the “Start in (optional)” field in the edit action part of the scheduled task.

You get the error 0x1 when a task scheduler is running a batch file because it can not find a file.  In the example below I am running the following scheduled task

• Task Name : Test Batch File
• Program/script : C:\Data\Robocopy.cmd
• Start in (Optional) : blank

Robocopy.cmd contents (FYI Robocopy.exe is located in C:\Data folder)

Robocopy.exe “C:\Data\Files” “D:\Backup\%DATE%\”

When a scheduled task runs if the “Start in (Optional)” field has not been filled out it will use the default path of C:\Windows\System32.  The issue with this is that it will not find the robocopy.exe file to start the file copy.

So there are a few fixes here

1. Open task scheduler by clicking start and typing in “Task Scheduler” and click on the app
2. Click task scheduler library
3. Right click on the required task and select properties
4. Click the actions tab
5. Click edit
6. In the Start in (Optional) field type in the required path (In the above example it will be C:\Data\

You could also copy the robocopy.exe file to C:\Windows\System32\ folder or update the Robocopy.cmd with the full path to the .exe as per below

C:\Data\Robocopy.exe “C:\Data\Files” “D:\Backup\%DATE%\”

How To Fix Task Scheduler (0x1) Error When Running Powershell Scripts

To fix the error 0x1 when running powershell scripts in task scheduler you need to set the execution policy to bypass in the task scheduler arguments.

To do this follow these steps

1. Open task scheduler by clicking start and typing in “Task Scheduler” and click on the app
2. Click task scheduler library
3. Right click on the required task and select properties
4. Click the actions tab
5. Click edit
6. In the “Program/script” field type in powershell.exe
7. In the “Add arguments” field enter -ExecutionPolicy Bypass -File “C:\Data\Script.ps1”
8. In the Start in (Optional) field type in the path of where the powershell script is located  C:\Data