SCHED_E_USER_NOT_LOGGED_ON (0X80041320) Fix

When This Error Shows Up

You set up a scheduled task in Windows Task Scheduler — maybe a backup script or a cleanup job. Then it fails. You check the history and see SCHED_E_USER_NOT_LOGGED_ON (0X80041320). This always happens when the task tries to run but nobody's logged into the machine. Classic scenario: you set a task to run at 2 AM and you're asleep. Windows says "sorry, can't do that."

Why It Happens

The culprit here is almost always the task's security options. By default, Task Scheduler creates tasks that only run when the user account is logged on. That's fine for interactive stuff like launching a program when you log in. But for background tasks that need to run at night or when you're away? It breaks.

Windows does this to protect your account — if the task runs without you logged in, it needs to store your password. Microsoft made it opt-in because some sysadmins got sloppy with security. But for most internal tasks, it's safe.

How to Fix It (5-Minute Fix)

1. Open Task Scheduler
   Press Win + R, type taskschd.msc, hit Enter.
2. Find your failing task
   Look in the left pane under Task Scheduler Library. Click it once.
3. Open task properties
   Right-click the task, choose Properties.
4. Go to the General tab
   Look at the bottom section: Security options.
5. Change the radio button
   Select "Run whether user is logged on or not". This is the fix.
6. Enter your password
   Windows will ask for your account password. Type it twice. This stores the credential securely.
7. Check the checkbox below
   Make sure "Do not store password..." is unchecked. That option is for services, not regular tasks.
8. Click OK
   That's it. Test the task by right-clicking it and choosing Run.

Still Failing? Check These

• Password changed recently?
  If you changed your Windows password, the stored credential in the task is stale. Go back and re-enter the new password.
• Account locked or disabled?
  Open lusrmgr.msc and check if your user account is active. If the account is disabled, no task runs.
• Task runs as SYSTEM?
  If you're running a task that doesn't need your user profile, switch to "Run with highest privileges" and use NT AUTHORITY\SYSTEM instead of your account. But be careful — SYSTEM has full access.
• Power settings killing it?
  If the machine goes to sleep, the task won't run. Go to Conditions tab and uncheck "Stop if the computer goes to battery power" and "Start the task only if the computer is on AC power" if you want it to run on battery.

Pro tip from experience: I've seen this error on Windows 10 and 11, Server 2016 through 2022. The fix is identical on all of them. Don't bother with the "Change User or Group" button — that only changes the account, not the logon requirement.

What NOT to Do

• Don't delete and recreate the task. Waste of time.
• Don't disable User Account Control (UAC). That's a security risk.
• Don't set the task to run with highest privileges without understanding what that means.

This error is one of the most common Task Scheduler gotchas. Once you know the fix, you'll spot it in 10 seconds. Change that radio button, enter your password, and move on.