0X00041302

SCHED_S_TASK_DISABLED 0X00041302 Fix Guide

This error shows up when a scheduled task is turned off. It won't run until you re-enable it. Here's how to fix that for good.

You're trying to run a scheduled task, maybe a backup or a script that cleans temp files, and you get the error SCHED_S_TASK_DISABLED (0X00041302). This usually happens when you open Task Scheduler, right-click a task, choose Run, and nothing happens. Or you check the task's history and see that message.

The real trigger is simple: someone or something turned the task off. Could be you by accident, a group policy from IT, or even a security tool that thought the task was suspicious. Windows won't run disabled tasks, period. The error code just confirms it's disabled.

Root Cause

A task gets disabled when its Enabled checkbox in Task Scheduler is unchecked. That's it. No hidden driver issues, no corrupted files. The scheduler reads that flag and says "nope, skipping this one." Sometimes group policy can force tasks off, especially on company computers. But 90% of the time, it's a manual change.

Fix: Enable the Task

Here's the step-by-step. Follow these exactly, and you'll be back in business in 2 minutes.

  1. Open Task Scheduler.
    Press Windows key + R, type taskschd.msc, and press Enter. You should see the Task Scheduler window open with three panels.
  2. Find your task.
    In the left panel, click the folder where your task lives. Common spots: Task Scheduler Library or a subfolder like Microsoft > Windows. Look in the middle panel for the task name that gave you the error.
  3. Right-click the task.
    Choose Properties from the menu. A Properties window opens with several tabs.
  4. Check the General tab.
    At the bottom of that tab, you'll see a checkbox labeled Enabled. If it's unchecked, that's your problem. Click the checkbox so it shows a checkmark. After you click it, you should see the box fill with a blue check.
  5. Save the change.
    Click OK to close Properties. You'll go back to the main Task Scheduler window.
  6. Test it.
    Right-click the task again and select Run. If the task starts immediately, you're good. The Status column should change to Running and then back to Ready once it finishes.

If the Task Won't Stay Enabled

Sometimes you enable it, click OK, and when you open Properties again, it's disabled. That means something is forcing it off. Here's what to check:

  • Group Policy: On a work or school PC, your IT might have set a policy to disable certain tasks. Open Command Prompt as admin (right-click Start, choose Terminal Admin) and run gpresult /h C:\report.html. Open that HTML file and search for your task name. If you see a policy setting it to disabled, you need to talk to your IT team.
  • Antivirus: Some security tools like McAfee or Bitdefender can disable tasks they think are risky. Check your antivirus's quarantine or task management settings. Add an exception for the task if needed.
  • Third-party software: Tools like CCleaner or advanced system optimizers sometimes disable tasks they think are useless. Go through their settings and make sure your task isn't in a blocked list.

If none of that works, delete the task and recreate it. Right-click it, choose Delete, then create a new one with the same settings. That usually fixes any weird corruption in the task's data.

What to Check If It Still Fails

You enabled it, it looks good, but the error still shows? Rare but happens. Try these:

  • Reboot your computer. A fresh start clears up weird state issues.
  • Check if the task's trigger is set correctly. In Properties, go to the Triggers tab. A disabled trigger won't fire even if the task itself is enabled.
  • Look at the task's History tab. Double-click any entry that says Task Disabled. It might give you more detail, like which policy or user disabled it.

That's it. You should now have the task running again. If not, your case is one of the rare ones where you might need to create a fresh task from scratch.

Related Errors in Windows Errors
0X80097005 MSSIPOTF_E_BAD_OFFSET_TABLE (0X80097005) Fix: Corrupt Font or Signature 0XC00A0016 STATUS_CTX_WINSTATION_NAME_COLLISION 0XC00A0016 Fix 0XC01E0313 STATUS_GRAPHICS_PATH_ALREADY_IN_TOPOLOGY (0xC01E0313) Fix 0XC00D1B75 Fix NS_E_INVALIDPACKETSIZE 0XC00D1B75 in Windows Media

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.