Task Scheduler error 0x80041322 in Windows Server

1. The Task Scheduler service is stopped or disabled

This is the most common reason you're seeing 0x80041322. Something — a security policy, a recent update, or even a power outage — stopped the Task Scheduler service and it didn't restart. You'll typically see this error when you try to run a scheduled task manually or during a system event, like after a reboot on a Windows Server 2016 or 2019.

Here's how to check and restart it.

1. Open the Services console. Press Windows Key + R, type services.msc, and press Enter.
2. Scroll down to Task Scheduler. Double-click it.
3. You should see the Startup type set to Automatic. If it's anything else — Disabled, Manual — that's your problem. Change it to Automatic.
4. If the Service status shows Stopped, click the Start button. Wait a few seconds. After you click Start, the status should change to Running.
5. Click Apply, then OK.

Now test your scheduled task. If it runs, you're done. If not, move to the next step.

2. The Task Scheduler service is corrupted — reset it with a command

Sometimes the service shows as running but it's in a weird state. Maybe a Windows Update botched something, or a previous crash left it half-broken. The real fix here is to reregister the Task Scheduler binaries. I've seen this fix work on hundreds of servers after a KB update went sideways.

You'll need an elevated Command Prompt. Right-click the Start button and select Windows PowerShell (Admin) or Command Prompt (Admin).

Run these commands in order. Wait for each one to finish before moving to the next.

sc config Schedule start= auto
sc start Schedule
schtasks /change /tn "\Microsoft\Windows\TaskScheduler\MaintenanceTasks" /enable

Here's what each does:

• sc config Schedule start= auto sets the service to start automatically. The space after start= is required — don't miss it.
• sc start Schedule starts the service right now.
• schtasks /change /tn ... /enable re-enables the built-in maintenance task that often gets disabled after a corruption.

After running those, try your scheduled task again. If it still fails, there's a registry issue.

3. Missing or corrupted registry key

This is the less common but trickier cause. The Task Scheduler stores its configuration in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule. If that key is missing or has wrong values, the service won't start properly — even if it shows as running.

You'll only need to go here if the first two steps didn't work. I'd estimate this happens in about 5% of cases, usually after a manual registry cleanup or a failed uninstall of third-party software.

Open Registry Editor by pressing Windows Key + R, typing regedit, and pressing Enter. Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule

Check that the following values exist and have the correct data:

• Start — should be 2 (Automatic start). If it's 4 (Disabled), double-click it and change it to 2.
• Type — should be 0x10 (Win32 own process). If it's missing or wrong, you'll need to recreate the key from a working server or restore from backup.
• ImagePath — should be %SystemRoot%\System32\svchost.exe -k netsvcs. If it's pointing to a different path, especially one that doesn't exist, fix it.

After any registry changes, restart the server. That's non-negotiable. The service caches registry values at boot, so a simple restart won't pick up the changes.

Once the server's back up, verify the service is running using services.msc, then test your task.

Quick-reference summary table

That's it. Start with the service status, then the command, then the registry. One of these will get your Task Scheduler back online. If none work, you're looking at deeper system corruption — possibly a corrupt system file that needs a DISM or SFC scan. But that's rare. Nine times out of ten, this error is just a stopped service.