Fix: The Selected Task ‘Name’ No Longer Exists

Fix: The Selected Task ‘Name’ No Longer Exists

I try to automate as many tasks on my computer as possible to avoid remembering to perform regular maintenance on my computer. Everything from cleaning out temporary files and unneeded files to defragging my non-SSD drives are run at least once a week.

I schedule the tasks using the Windows Task Scheduler, which makes it easy for me to perform the tasks on a specific schedule. I recently ran into an issue where this following error message was display on the screen whenever I access the Task Scheduler:

The selected task 'name' no longer exists. To see the current tasks click Refresh.

The message appeared twice – once for each task that didn’t exist anymore. On top of that, the same messages appear multiple times – once when I opened the Task Scheduler, and a second time when I navigated to the folder that contained the missing tasks.

While the message didn’t stop me from using the Task Scheduler, it just became annoying to having to click the OK button four times each time I accessed the Task Scheduler. So I decided to fix the error to avoid the messages.

The selected task ‘Name’ no longer exists solution

For such a simple issue – at least I thought it was a simple issue – it did take some research to find a solution to the problem.

Most of the solutions I found were for a similar, but different, issue. I did, however, find the correct solution to my problem.

To resolve the issue, use the following steps:

  1. Click the Start logo and type “regedit” to search for the registry editor.
  2. Right-click the regedit name and select “Run as administrator” to open the registry editor as an administrator. You will either need to enter the administrator password, or confirm the opening of the registry editor as an administrator.
  3. In the registry editor, navigate to the “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree” key.
  4. Inside that key you will see additional subkeys for each of task. Find the ones that match the names of the missing tasks, and then delete the subkey with the same name.
  5. Reopen the task scheduler. If the error persists, restart Windows and then reopen the task scheduler

Since I had two missing tasks, I deleted the two subkeys that matched the names of the tasks in the error messages, and the next time I went into the task scheduler the error messages were no longer displayed.

14 Responses to “Fix: The Selected Task ‘Name’ No Longer Exists”

  1. Priscilla says:

    Hi, The other day I thought it was the setting as I set it to restart the task in 3 min. I removed this condition. Today the task I am having issues with does not run and running the task manually prompts the same error. I deleted both regedit and in folder task and created a new task but this did not work. I have tried exporting a working task and importing and configuring it to the non-working task. It still did not work and I am still having the same issue. Could it be my permission even though my login permission is already admin. Any other ideas would be much appreciated. Thanks in advance!

    • Priscilla says:

      I tried a different approach and it looks like it is only failing if I add run task every 30 min for some hours. If I remove this, the task seems to run on demand. I believe it might be a MSFT issue. Any thoughts or ideas is most appreciated. Thanks!

  2. brian says:

    Thanks, worked for me!

  3. Ashish says:

    is there any script is available to this task as in my organization more than 400 pc having this problem.

  4. Steve Brown says:

    My error message, which I no longer get, said that “{0}” was missing. That’s when I googled and found this article. I didn’t see anything called “{0}” in the tree, so I went back to Task Scheduler and read the complete error message. It said to run Refresh. You can right-click ‘Task Scheduler Library” or select ‘Refresh’ from the ‘Action’ menu. No more error message.

  5. James says:

    Thanks, was wondering where those tasks resided.

  6. CyberAngel says:

    Thank you, saved me a lot of searching for a solution.

  7. Curtis Gray says:

    Thanks for taking the time to put this here. AS MS gets more like Apple every day (charges more, delivers less, increases attitude, pretends it owns my hardware) it is helpful when people share their fixes as we certainly cannot count on MS to do so.

  8. Douglas D Smith says:

    We should not have to do this. With Linux Unix or Apple OS, this could not happen. Microsoft should pay $1 for each of these worthless waist of time errors. POS

    • Paul Salmon says:

      Issues happen on all operating systems. I have had issues with iOS on my mobile devices, and some of the most high-profile security issues over the past 5 years have affected open-source libraries that run on *nix machines. Saying that issues like this could not happen on anything but Windows means ignoring the facts of history.

  9. Kenneth Chirinos says:

    Good stuff worked as advertised for me

  10. bn880 says:

    Good tip, thanks

  11. Mike Denny says:

    Thanks! Worked great.

  12. Greg S says:

    Thank you, fix worked perfectly!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.