What is TASK-SCHEDULER-ERR?
Scheduled task fails with error 0x1 ranks as a medium-severity Windows operating system issue in our database. A Windows Task Scheduler task runs but exits with return code 0x1 (general error) or 0x41301 (task is running). Another common trigger is 'Run only when user is logged on' vs 'Run whether user is logged on or not' mismatch. The steps below are ordered to resolve this efficiently.
Common Causes
- 'Run only when user is logged on' vs 'Run whether user is logged on or not' mismatch
- Incorrect working directory set in task properties
- Missing permissions for the task action
Step-by-Step Fix Guide
-
1
Check task history in Task Scheduler for detailed error
This step, "Check task history in Task Scheduler for detailed error", specifically rules out incorrect working directory set in task properties.
-
2
Set 'Start in' path to the folder containing the executable
"Set 'Start in' path to the folder containing the executable" covers a less common but documented cause of TASK-SCHEDULER-ERR.
-
3
Run as SYSTEM or a user with sufficient privileges
If earlier steps didn't help, "Run as SYSTEM or a user with sufficient privileges" directly addresses 'Run only when user is logged on' vs 'Run whether user is logged on or not' mismatch.
Commands & Diagnostics
schtasks /query /fo LIST /v
eventvwr.msc
Frequently Asked Questions
In most cases, 'Run only when user is logged on' vs 'Run whether user is logged on or not' mismatch is behind TASK-SCHEDULER-ERR. Incorrect working directory set in task properties and missing permissions for the task action can trigger it too.
Try "Check task history in Task Scheduler for detailed error" first — it resolves most TASK-SCHEDULER-ERR cases on its own. Only work through the rest of the guide above if it comes back.
As a medium-severity issue, TASK-SCHEDULER-ERR is more of a stability annoyance than a hardware risk — the steps above should clear it up.
In most cases, yes — the guide above resolves TASK-SCHEDULER-ERR without a clean install. Treat a reinstall as the last resort, not the first move.
Sometimes. Microsoft regularly releases patches that fix known BSOD triggers including TASK-SCHEDULER-ERR. Make sure Windows is fully up to date via Settings → Windows Update before attempting more advanced fixes.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database