| Previous | Next |
| SCHED_S_SOME_TRIGGERS_FAILED | SCHED_S_TASK_QUEUED |
SCHED_S_BATCH_LOGON_PROBLEM
SCHED_S_BATCH_LOGON_PROBLEM means the task was registered but may fail when it starts because its principal lacks the Log on as a batch job right. It is an early warning about the task’s execution identity, not evidence that the task action or trigger is invalid.
When it matters
Microsoft documents that tasks registered with TASK_LOGON_PASSWORD or TASK_LOGON_S4U launch only when the specified user has the batch-logon privilege. Domain or local policy can grant or deny that right after a task is created, so a task that worked previously can later fail without changes to its XML.
What to check
- The task principal, logon type, domain or local account name, and current effective user-right assignment.
- Group Policy results, including any explicit deny assignment that overrides an allow assignment.
- Whether the selected logon type matches the task’s resource needs: S4U does not provide network or encrypted-file access.
Microsoft: Task Scheduler status codes · Microsoft: security contexts for tasks · Microsoft: TASK_LOGON_TYPE
Looking for a different code? Search another status or error code.