Fix 0x80041314: SCHED_E_UNSUPPORTED_ACCOUNT_OPTION in Task Scheduler

What the 0x80041314 error actually means

You're trying to edit or run a scheduled task, and Windows throws 0x80041314 (SCHED_E_UNSUPPORTED_ACCOUNT_OPTION). This happens when the task's stored account or password flag is corrupted or set to an option Windows doesn't support anymore. Common triggers: you migrated the task from an older Windows version, or you copied a task XML from another machine. The good news is you don't need to rebuild your entire task list.

Fix 1: Quick password reset (30 seconds)

This fixes 80% of cases. The task's stored password is stale or was never saved.

1. Open Task Scheduler (taskschd.msc).
2. Find the task throwing the error. Right-click it, choose Properties.
3. Go to the General tab.
4. Under Security options, click Change User or Group. Enter the same account (or a different one). Click OK.
5. Check Run whether user is logged on or not. Type the password twice. Click OK.
6. Try to run the task manually now.

If the Properties window won't open (it often hangs or crashes with this error), skip to Fix 2 or 3.

Fix 2: Delete and recreate the task (5 minutes)

When you can't even open the task properties, your best bet is to blow it away and recreate it. The error is stored in the task's internal registry-style data, and the GUI can't handle it.

1. Export the task's current settings (if you can) by right-clicking and selecting Export. Save the XML file. If that fails, you'll have to recreate from memory.
2. Delete the task. Select it and press Delete, or right-click and choose Delete.
3. Import the XML: In Task Scheduler, click Import Task... on the right pane, select your exported XML.
4. Before hitting OK, check the General tab. Re-enter the password for Run whether user is logged on or not. This resets the corrupt flag.
5. Click OK. Test the task.

If you don't have the XML, create the task fresh. Use the same triggers and actions. Annoying, but it works.

Fix 3: Nuke the task's corrupt registry data (15+ minutes, advanced)

This is the nuclear option. Sometimes the task data is so corrupt that even the XML export/import carries the bad flag. You need to delete the task's registry key manually.

Backup everything first. Seriously.

1. Open Regedit (regedit.exe).
2. Navigate to:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks
3. Each task is stored as a GUID. To find yours, look at the Path value in each GUID folder. It shows the task name (e.g., \MyTask).
4. Once you find the offending task, export that entire GUID key as a .reg file for backup.
5. Right-click the GUID folder and delete it. Yes, delete.
6. Close Regedit.
7. Open Task Scheduler. Press F5 to refresh. The task will be gone.
8. Now recreate the task from scratch (or import a clean XML if you have one).

Why does this work? The corrupt account option is stored in the TaskCache hive. Deleting the key removes all cached data, including the bad flag. The GUI then forces a clean write when you recreate the task.

What NOT to do

• Don't bother running SFC or DISM. They won't touch Task Scheduler's account cache.
• Don't waste time with schtasks /change with the /RU and /RP flags. It often fails with the same error because it's the GUI under the hood.
• Don't reinstall Windows. This is a data corruption in one task, not a system-wide problem.

Why this error happens (the short version)

The Task Scheduler stores each task's account info in a binary blob inside the registry. If that blob gets half-written (power failure during task creation, bad XML import, or a botched password change), Windows can't parse the account option and throws this error. Fix 1 rewrites the blob cleanly. Fix 2 forces a fresh blob. Fix 3 deletes the blob entirely.

Pro tip: If you're managing tasks remotely or via Group Policy, always set Run whether user is logged on or not explicitly. Never leave it on the default Run only when user is logged on if you plan to change the account later. That's a common trigger for 0x80041314.