The selected task “{0}” no longer exists
Before making any changes to your system, it is recommended to create a system restore point or backup your Registry files. Having done this, proceed.
1] Repair Task Scheduler by deleting corrupted tasks
This is quite important since one corrupted file can cause a big problem. To delete a corrupted task or any task from Task Scheduler, you need to take the help of the Registry Editor, when you are unable to use Task Scheduler interface. For that press Win + R, type regedit and hit the Enter button. Following that, navigate to the following path- Here you can find all the tasks which are currently set in the Task Scheduler. As you do not know which one is corrupted, you should try deleting the latest one in Task Scheduler last. Before deleting, you should note down the ID. To get the ID, select the task that you want to delete, double-click on the Id string on your right-hand side, and copy it in Notepad.
After that, right-click on the task name, and delete it.
Next, delete that same GUID (the Id you have copied earlier) from these following folders- You may not find the same in all folders but if you see it, delete it. Now navigate to this location: Delete the same task you deleted from Registry Editor. Restart your computer and check if you can use Task Scheduler properly or not.
2] Synchronize tasks manually in Task Scheduler
If there is any problem in the synchronization between Explorer and Registry Editor, you might get this error message while opening Task Scheduler on Windows 10/8/7. You can try synchronizing them manually. In other words, you need to check whether all created tasks have also created a registry key. For that, navigate to this folder in the File Explorer: And open this path in the Registry Editor: Now, check whether all tasks in Windows Explorer are also included in Registry Editor or not. You need to check two locations in the Registry Editor, and they are as follows: If you find any extra task in either location, you can delete that task and then check whether Task Scheduler is opening properly or not. These are two primary solutions to this issue, and we hope one of them helps you.
