Table of Contents
Do you want to know how to Fix ‘Task Scheduler Service Is Not Available’ issue? Task Scheduler has always been an important tool for Windows users who want to plan out when to run programs and other tasks. But I just found out that Task Manager on my Windows computer isn’t working right. For example, if I open it, I see a message about the Task Scheduler service being available. Several bugs and errors are out to get Windows users. Task Scheduler is not available is the latest in a long list of Windows 11 or Windows 10 errors. When this error comes up, neither OK nor closing the window will work.
The error comes back, and the Task Scheduler stops working. If you get stuck in this kind of situation, Task Manager is the best way to get out of it. Still, it will show up again after a while. This bug affects a lot of Windows users. If you are one of them, you no longer have anything to worry about. This error could be caused by a number of things, such as a broken registry or a broken Task Scheduler tree cache. We will try different things to Fix ‘Task Scheduler Service Is Not Available’ issue. Just do them one at a time until the problem is fixed.
What is the Task Scheduler service?
The Task Scheduler service is a Windows service that lets you set tasks to run at certain times or intervals. This can be useful for automating tasks like backing up files, running updates, or sending emails. By default, the Windows Task Scheduler service is turned on. Go to Start > Run and type taskschd.msc to open it.
There are two parts to the Task Scheduler window: the Task Scheduler Library and the Task Scheduler Summary. All of the tasks that have been made are shown in the Task Scheduler Library pane. The tasks that are running right now are shown in the Task Scheduler Summary pane.
Causes of the “Task Scheduler Service Is Not Available” error?
- Disabled Task Scheduler Service: If the Task Scheduler service is disabled on your computer, it won’t be available to manage scheduled tasks.
- Corrupted System Files: System files related to Task Scheduler may become corrupted, preventing the service from running correctly.
- Malware or Virus Infection: Malware or viruses can disrupt system services, including Task Scheduler, leading to errors.
- Software Conflicts: Third-party software or applications can sometimes conflict with Task Scheduler, causing it to become unavailable.
- Permissions Issues: Insufficient or incorrect permissions on Task Scheduler files or registry entries can result in this error.
- Windows Updates: Some Windows updates can introduce compatibility issues or bugs that affect Task Scheduler’s functionality.
- Registry Errors: Incorrect or damaged entries in the Windows registry can impact Task Scheduler.
How to Fix ‘Task Scheduler Service Is Not Available’ issue
Edit the TimeBrokerSvc Registry Key

- Start Registry Editor.
- Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services where you find services. TimeBrokerSvc is a service.
- Double-click the Start DWORD in the TimeBrokerSvc key.
- Verify if the value of the Start DWORD is set to 3.
- To save and close the DWORD window, click OK.
- Close the Registry Editor window.
- Press “Start,” then “Power,” and finally “Restart” from the options.
Rename the Tree Registry Key
- Get the Registry Editor going.
- Go to the important spot below:
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ScheduleTaskCache\Tree\Software\Microsoft\Windows NT\CurrentVersion\ScheduleTaskCache\Tree
- Right-click on the key called “Tree” in the registry and choose “Rename.”
- Type “Tree.old” as the key’s new name.
- Open the Task Scheduler and run the affected tasks to see if the problem still happens.
- If the error stops happening after you rename the Tree key, it means that a corrupted task is to blame. In this case, you’ll need to find the key for that task and delete it. Make sure to back up the registry before moving on.
- Change the name of the Tree.old key to Tree.
- If you double-click the Tree key, it will grow.
- Click the right mouse button on the first task subkey and choose Rename.
- Add .old to the end of the name of the key.
- Go back to Task Scheduler and run a task that was affected to see if the error message comes back.
- If the error still happens, change the key you just renamed back to its original name by removing the .old suffix.
- Do the same steps for the other subkeys for tasks in the Tree key.
- Right-click on the last key you renamed that was broken and choose Delete > Yes to get rid of it.
Edit the Schedule Registry Key
- Open the Windows Search bar: Press the Windows key + S.
- Open the Registry Editor: Type regedit in the search box and press Enter.
- Clear the path in the address bar of the Registry Editor.
- Type in these key locations: Schedule is located at Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services*Schedule*.
- Choose the Schedule key from the list on the left.
- Double-click on the Start DWORD in the Schedule key.
- If the Start DWORD is set to a number other than 2, type 2 in the Value box.
- Press OK to set the new value for the Start DWORD.
- Put an end to the app Registry Editor.
- To use the changes, you need to restart Windows.
Reset Windows
- Open the menu for settings.
- Choose the System.
- Select Recover.
- Find the option to Reset this PC and click on it.
- This will start the process of resetting your PC.
Change the Network Condition
- Press the Windows key and the R key together to open the Run dialog.
- Type taskschd.msc in the text box and click OK.
- In the left sidebar, click on Task Scheduler Library.
- Right-click on the task where the error is happening.
- Choose Properties from the menu that pops up.
- Select the Conditions tab in the task’s properties window.
- If the Start only if there is a network connection box is checked, uncheck it to turn off the setting.
- To save the changes, click OK.
- Get rid of Task Scheduler.
- Reboot your computer.
- Click the search box or button on the taskbar that says “Search Windows.”
- Find out what PowerShell is.
- Click the right mouse button on the PowerShell result in the search tool.
- Choose “Run as administrator” to open PowerShell as an administrator.
- Make a copy of this command:
- gci -path “c:windowssystem32tasks*” -recurse | select-string “/Id>” | select-object “filename,line”
- To paste the command into PowerShell, press Ctrl+V.
- To run the command, press Enter.
- You will see a list of filenames for tasks that need a certain kind of network.
- In Task Scheduler, double-click each of these tasks.
- Follow the steps above to stop their network conditions from working.
- Repeat the steps for each task that has a different network situation.
Conclusion
Task Scheduler is a tool in Windows that lets users set up and run tasks automatically. But some users can’t run tasks because they get an error message that says “Task Scheduler service is not available.” Users say this error message appears when they try to run tasks by hand. Task Scheduler can usually still be used by users who need to fix this error. But that tool isn’t very useful if its tasks don’t run. Here’s how to fix the “Task Scheduler service is not available” error on Windows 10 and 11. If you want to know more information about this issue so you can visit Microsoft Official Website.
Questions and Answers
System inactivity: By default, Windows won’t run scheduled tasks when the system isn’t doing anything, like when it’s sleeping or hibernating. Check the power settings and set up the tasks so that they run even when the computer is not being used. The Task Scheduler service is not running or has been turned off.
Method 2: Go to Apps and Features/Programs and Features to get rid of Advanced Task Scheduler. Find and click on Advanced Task Scheduler in the list. The next step is to click “uninstall” to start the process of getting rid of the program.
Switch or change the user account. You might be having trouble because your profile is wrong or because the administrator hasn’t given you access. If you own this computer but still can’t get to the task manager, we can try switching the user account and see if that helps.