How to fix error Task Scheduler service is not available on Windows server 2019, 2022

Windows server users are targeted by a number of errors and issues. The latest in the long list of Windows server 2019, 2022 errors is Task Scheduler is not available. When this error appears, clicking on OK or closing it doesn’t work at all. The error shows up again, and makes the Task Scheduler freeze. If you get stuck in such situation, the best way to close it is through Task Manager. But it will still show again up after some time. Many Windows server 2019, 2022 users are affected by this error. If you are also one of them, there is nothing to worry about anymore. The reason behind this error could be anything from the corrupt registry to corrupted Task Scheduler tree cache. We will try to fix this issue using different methods. Simply perform them one by one, until the issue is fixed.

Editing Registry Values

1 – Search Registry editor in Windows search box. Click on on Registry editor to open it.

2 – Now, browse to the path given below in Registry editor.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBrokerSvc

3 – Now, in the right side double click on Start.

4 – Change the value to 3 and click OK.

Now you need to restart your computer. After the restart, the error will be fixed.

Fix the Registry

1 – Press Windows key + R on your keyboard to bring up the Run dialog

2 – In Run, type regedit and click OK

3 – The last step will open Registry Editor. Here, you have to follow the path mentioned below on the left side of Registry Editor.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule

4 – After selecting Schedule on the left side, look for Start key on the right side of the Registry Editor.

5 – Here, under Value data type 2 and click on OK.

6 – After the last step, close the Registry Editor. Now you just need to restart your computer.

Find and Delete the Corrupted Task Scheduler Tree Cache

1 – Press Windows key + R on your keyboard to bring up the Run dialog

2 – In Run, type regedit and click OK

3 – Here, you have to follow the path mentioned below on the left side of Registry Editor.

HKEY_LOCAL_MACHINE\SOFTWARE \Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree

4 – On the left side of the Registry Editor, right-click on Tree and click on Rename. Rename it to Tree.old.

Note: -If you can not edit Tree , Read this article to get full permission

5 – Now, open the Task Scheduler and check if this has solved the problem. If you are no more getting the error message, this means the Tree is corrupted. Now we have to find out which task is corrupted in it.

6 – First, you need to rename Tree.old back to Tree. To do that, right-click on Tree.old and select Rename. Now rename it to Tree.

7 – Expand Tree. Here you will see a number of scheduled tasks. Now, you have to rename the first task and add “.old” at the end of its name (very much like Step 4). For example, if the first task is StartAUEP, then right-click on it and select Rename. Now rename it to StartAUEP.old.

8 – After performing the last step, open Task Scheduler and check if you are still getting the error. If you are still getting the error, then remove the “.old” from the task you renamed in the last step.

9 – Now, perform the Step 7 with the next task and then repeat Step 8. Keep doing this with every task, until the error message stops showing in the Task Scheduler.

And when you don’t get the error on Task Scheduler, this means the last task you renamed is the corrupted one. Now, simply delete the corrupted task by right-clicking on it and selecting Delete.

This should fix the problem.

Conclusion

In ours case after performing the above steps, we did not see the error again.

Hopefully this article will be useful for you. Good luck !