| Previous | Next |
| SCHED_E_ALREADY_RUNNING | SCHED_E_INVALID_TASK_HASH |
SCHED_E_USER_NOT_LOGGED_ON
SCHED_E_USER_NOT_LOGGED_ON means the task requires an interactive user session, but the selected user is not currently logged on. The error is expected for a task registered with an interactive-token logon type when no matching interactive token exists.
Distinguish the intended execution model
TASK_LOGON_INTERACTIVE_TOKENrequires the user to be logged on and runs only in an existing interactive session.- Password and S4U logon types are different models with their own credential and privilege requirements.
- Tasks that show UI or need a user desktop must use an appropriate interactive design; services should not assume a desktop session exists.
Fix the configuration, not the symptom
Use an interactive trigger or logon type only when the task truly depends on a logged-on user. For unattended work, redesign the task around a supported non-interactive principal and explicitly test access to the files, network resources, and privileges it needs.
Microsoft: Task Scheduler status codes · Microsoft: TASK_LOGON_TYPE · Microsoft: security contexts for tasks
Looking for a different code? Search another status or error code.