Freigeben über

Error message 'The selected task "{0}" no longer exists. To see the current tasks, click Refresh’

  • Artikel

A lot of customers complained the following:
When they open up the Task Scheduler, they get a message that says:
The selected task "{0}" no longer exists. To see the current tasks, click Refresh.

 The mechamism task scheduler uses: it has a copy of tasks in registry and a copy of them in task files on disk. If somehow the tasked stored in registry and on disk are not in sync, users will encounter such issues as reported.

Tasks are stored in C:WindowsSystem32Tasks

In Registry, related branches are located in:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Tasks tree is stored in:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTreeMicrosoft

So the general troubleshooting steps are starting from checking these locations to see if anything is broken or inconsistent.

Reference:

 https://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/69afe198-3f97-406a-8d91-6a17504fb5b5

https://social.technet.microsoft.com/Forums/en-IE/w7itproinstall/thread/273368d4-ed12-4107-9d52-34759f2b53aa

https://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/1f677dd3-bdb7-4650-9164-d8e2c66b7708

https://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/d584f7e4-4e4c-45e8-8bce-39414914d674

https://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/a9e485d3-06ba-4038-a9b8-1b58e73ea4dd

https://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/360fde7c-ec4e-41f2-ae74-8949218e7a06

https://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/8e779ed1-7200-482e-a3a4-1e0ba8bf17cc

https://social.technet.microsoft.com/Forums/en/w7itproperf/thread/94bb210a-b291-41ad-a745-d4a9d8cc77dc

https://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/344f6815-0878-43ab-8997-33790b889541

https://social.technet.microsoft.com/Forums/pl-PL/w7itproperf/thread/43712af2-5731-4177-9d45-31d9b5b3240d

Comments

  • Anonymous
    February 17, 2012
    The comment has been removed

  • Anonymous
    May 03, 2012
    The comment has been removed

  • Anonymous
    May 05, 2012
    If It can be fixed by a series of steps then surly MS could generate a EXE or BAT file which would fix a complicated error. The semi-automatic fixing of errors is one thing which possibly would create a user friendly os.

  • Anonymous
    June 18, 2012

  1. Open Registry Editor
  2. Open the following Key a. [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionTracingSCMRegular]
  3. Add/Change the following value a. Name = TracingDisabled b. Type = REG_DWORD c. Value Data = 0
  4. Reboot the Server
  5. Open Task Scheduler and verify that you can see the tasks

  • Anonymous
    August 16, 2012
    Thanks to  Abhishek for his suggestion - Seems to be a system logging system. I was unable to find which task in the Windows folder was causing the problem as they ALL gave an error. Followed Abhishek idea and was then able to find Defrag was the problem. I deleted the file from my HD and the problem was cleared. Then un-did the Abhishek fix.

  • Anonymous
    December 27, 2013
    Pingback from The [The selected task ???{0}??? no longer exists???] issue | UC3

  • Anonymous
    January 22, 2014
    The comment has been removed

  • Anonymous
    March 25, 2014
    Good morning AskPerf! Over the past couple of years, our customers have opened Support Cases and created

  • Anonymous
    September 30, 2014
    Same issue here, scheduler worked but after awhile the message starts to grate on my nerves...
    Problem was corrected by simply resetting the schedule for the defrag then disabling it in the scheduler, apparently I deleted it...

  • Anonymous
    November 06, 2014
    Thanks abhishek

  • Anonymous
    December 08, 2014
    I had this issue today, came across this thread and looked at the solutions. I managed to solve my error with just a restart of the Task Scheduler service. It might be worth that a go before messing with the registry / rebooting server.

  • Anonymous
    August 10, 2015
    The comment has been removed

  • Anonymous
    October 28, 2015
    The comment has been removed

  • Anonymous
    November 17, 2015
    I'm getting this error after installing the first Windows 10 update