Task Scheduler is one of the most useful built-in tools in Windows. It allows you to automate tasks such as launching applications, running scripts, creating backups, deleting temporary files, and performing system maintenance without manual intervention. However, many Windows 10 and Windows 11 users encounter an error where a scheduled task completes with the Last Run Result: (0x1) instead of running successfully.
The 0x1 error usually means the scheduled task started but failed to complete properly. Unlike other Task Scheduler errors that clearly describe the problem, 0x1 is quite generic, making it difficult to identify the exact cause. It can happen because of an incorrect file path, missing permissions, an invalid working directory, incorrect command-line arguments, corrupted system files, or environmental differences between manual execution and scheduled execution.
The good news is that the problem is usually easy to fix once you identify what’s causing it. In this guide, we’ll explain what the Task Scheduler 0x1 error means, why it happens, and the most effective methods to fix it in Windows 10 and Windows 11.
What Does Task Scheduler Error 0x1 Mean?
Error 0x1 is a generic return code indicating that the scheduled task did not complete successfully. In many situations, the application or script itself returned the exit code 1, which Task Scheduler displays as 0x1.
Common symptoms include:
- Scheduled task never completes successfully.
- Last Run Result always shows 0x1.
- The task works perfectly when run manually.
- Batch files fail only when scheduled.
- PowerShell scripts stop unexpectedly.
- Programs launch briefly and then close.
- Backup or maintenance tasks fail automatically.
Since multiple issues can generate this code, troubleshooting usually involves checking the task configuration carefully.
Why Does the 0x1 Error Occur?
Several reasons can trigger this error:
- Incorrect executable path
- Missing quotation marks in file paths
- Wrong Start in (Working Directory)
- Missing administrator privileges
- Incorrect user account settings
- Batch or PowerShell script errors
- Network drives unavailable
- Environment variable problems
- Antivirus blocking the process
- Corrupted system files
- Incorrect command-line parameters
- Task Scheduler service issues
Let’s go through the solutions one by one.
Method 1: Verify the Program or Script Path
The most common reason behind the 0x1 error is an incorrect file path.
Open Task Scheduler and locate the scheduled task.
Right-click the task and select Properties.
Open the Actions tab.
Select the action and click Edit.
Verify that the Program/script field points to the correct executable.
For example:
C:\Windows\System32\notepad.exeInstead of:
notepad.exeUsing the complete path helps Windows locate the application correctly.
Also verify that the file actually exists.
After saving the changes, run the task manually from Task Scheduler.
Method 2: Add Quotation Marks Around File Paths
If the program path contains spaces, Windows may interpret it incorrectly.
Incorrect example:
C:\Program Files\App Folder\App.exeCorrect example:
"C:\Program Files\App Folder\App.exe"The same rule applies to batch files, PowerShell scripts, Python scripts, and executable files.
Quotation marks prevent Windows from treating spaces as separate commands.
Method 3: Configure the “Start in” Folder
Many applications expect a working directory.
If the Start in (optional) field is empty, the application may fail even though the executable launches correctly.
Open:
Task Properties > Actions > Edit
Locate:
Start in (optional)
Enter only the folder path.
Example:
C:\ScriptsDo not include the script name.
Correct:
C:\ScriptsIncorrect:
C:\Scripts\backup.batThis small configuration fixes many 0x1 errors.
Method 4: Run the Task with Highest Privileges
Some programs require administrator permissions.
Without elevation, Windows may return error 0x1.
Open Task Properties.
Select the General tab.
Enable:
- Run whether user is logged on or not
- Run with highest privileges
Click Apply.
Enter your account password if prompted.
Now test the task again.
Method 5: Check the User Account Running the Task
Sometimes the task is configured to run under the wrong user account.
Open:
Task Properties → General
Verify:
- User account
- Account password
- User permissions
If the account password has recently changed, update it in Task Scheduler.
A task using outdated credentials often produces error 0x1.
Method 6: Use Full Paths for All Files
Avoid relying on Windows search paths.
Instead of:
pythonUse:
C:\Python313\python.exeInstead of:
backup.batUse:
C:\Scripts\backup.batSimilarly, specify complete paths for:
- Scripts
- Input files
- Output folders
- DLL locations
- Configuration files
Using absolute paths reduces the chances of Task Scheduler failing because it cannot locate a resource.
Method 7: Verify Command-Line Arguments
Incorrect arguments frequently generate exit code 1.
Suppose you’re running:
"C:\Program Files\App\App.exe"with arguments.
Verify every parameter carefully.
Example:
--backup --silentRemove unnecessary spaces.
Check spelling.
Ensure every file path exists.
If you’re unsure, test the exact command in Command Prompt before using Task Scheduler.
Method 8: Test the Script Manually
If you’re scheduling a batch file or PowerShell script, execute it manually first.
Open Command Prompt as Administrator.
Navigate to the script folder.
Run:
backup.bator
powershell.exe -ExecutionPolicy Bypass -File "C:\Scripts\Backup.ps1"If the script itself produces errors, Task Scheduler will simply display 0x1.
Fix the script before troubleshooting Task Scheduler.
Method 9: Check PowerShell Execution Policy
PowerShell scripts often fail because script execution is disabled.
Open Windows Terminal as Administrator.
Run:
Get-ExecutionPolicyIf it returns:
Restrictedallow local scripts:
Set-ExecutionPolicy RemoteSignedOr schedule PowerShell using:
powershell.exe -ExecutionPolicy Bypass -File "C:\Scripts\Script.ps1"This bypasses execution restrictions for that task.
Method 10: Repair Corrupted Windows System Files
Corrupted system files can also interfere with Task Scheduler.
Open Command Prompt as Administrator.
Run:
sfc /scannowWait until verification reaches 100%.
After completion, run:
DISM /Online /Cleanup-Image /RestoreHealthRestart the computer.
These tools repair damaged Windows components that may affect scheduled tasks.
Additional Tips to Prevent the 0x1 Error
Following a few best practices can help avoid Task Scheduler errors in the future.
Always use complete file paths rather than relying on Windows to locate executables automatically. If your task launches a program located in Program Files, enclose the path in quotation marks to handle spaces correctly.
Whenever possible, test commands in Command Prompt or PowerShell before scheduling them. If a command fails manually, it will almost certainly fail in Task Scheduler as well.
Avoid saving scripts on removable drives or temporary network locations. If the scheduled task starts before the drive becomes available, Windows may return the 0x1 error.
If your task depends on mapped network drives, remember that Task Scheduler may not recognize drive letters such as Z: or X: when running in the background. Instead, use the full UNC path, for example:
\\Server\SharedFolder\File.txtThis ensures the resource is available regardless of how the task is executed.
Common Mistakes That Cause Error 0x1
Many users accidentally create incorrect task configurations. Some of the most common mistakes include:
- Using relative instead of absolute paths.
- Forgetting quotation marks around file paths with spaces.
- Leaving the Start in directory blank.
- Running tasks without administrator privileges.
- Scheduling scripts that contain syntax errors.
- Using expired user account passwords.
- Referencing disconnected network drives.
- Deleting files required by the scheduled task.
- Blocking the executable with antivirus software.
- Providing incorrect command-line arguments.
Reviewing these items carefully often reveals the root cause.
How to Confirm the Task Is Working Correctly
After applying the fixes, verify that the task runs successfully.
Open Task Scheduler and locate your task.
Right-click the task and select Run. Wait a few moments, then refresh the list.
Check the Last Run Result column. If the task completed successfully, the result should display 0x0, which indicates successful execution.
You can also review the History tab for detailed information about when the task started, whether it launched the intended program, and if any additional errors were recorded. If the History tab is disabled, enable it from the Action menu by selecting Enable All Tasks History.
For more detailed troubleshooting, open Event Viewer and navigate to Applications and Services Logs > Microsoft > Windows > TaskScheduler > Operational. This log records events related to scheduled tasks and may provide additional clues if the problem persists.
Frequently Asked Questions
Why does Task Scheduler show 0x1 even though the program works manually?
Manual execution uses your current user environment, working directory, and permissions. A scheduled task may run under a different account, with a different working directory or without administrative rights, causing it to fail.
Does 0x1 always indicate a Task Scheduler problem?
No. In many cases, the scheduled application or script itself returns an exit code of 1, and Task Scheduler simply reports that code. The issue may lie within the script, application, or its configuration rather than Task Scheduler.
Should I use “Run whether user is logged on or not”?
Yes, if the task needs to run in the background without requiring an active user session. Combine this option with Run with highest privileges if administrative access is needed.
Can antivirus software cause the 0x1 error?
Yes. Some antivirus or endpoint security programs may block scripts, batch files, PowerShell commands, or applications launched by Task Scheduler. Temporarily disabling the security software for testing or adding the task to the antivirus exclusion list can help determine if it’s the cause.
Conclusion
Task Scheduler error 0x1 is one of the most common scheduled task issues in Windows 10 and Windows 11, but it is usually straightforward to resolve. In most cases, the error is caused by an incorrect executable path, missing quotation marks, an empty working directory, insufficient permissions, invalid script parameters, or problems within the script itself.
Start by verifying the program path, ensuring all file locations are correct, adding quotation marks where necessary, and specifying the appropriate Start in directory. If the task requires elevated privileges, configure it to run with the highest privileges and confirm that the correct user account and password are being used. Testing scripts manually and repairing Windows system files with SFC and DISM can also help eliminate underlying issues.
By carefully reviewing the task configuration and following the methods outlined in this guide, you can eliminate the 0x1 error and ensure your scheduled tasks run reliably and automatically on both Windows 10 and Windows 11.
