Task Scheduler error

Pokomolo 21 Reputation points
2021-02-19T13:53:31.463+00:00

Hello, When I wanted to create a new task in the task scheduler I realized that it was not working correctly. When I open it, an error message appears that says "The selected task" {0} "no longer exists. To see the current tasks, click on Refresh". When I click on Refresh, the same message reappears. In the "task status" or "active tasks" panes, it is written "Failed to read data". If I click on "create a basic task" a message appears that says "The task scheduler service is not available or the folder does not exist. Check that the service is running and that the folder exists " In the scheduler, besides the problems mentioned above, I get a message "Unrecoverable failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))" when I click on "Show all active tasks" In fact, nothing works, I get error messages wherever I click. Do you have a solution?

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,417 questions
0 comments No comments
{count} votes

Accepted answer
  1. Reza-Ameri 16,776 Reputation points
    2021-02-19T14:38:31.65+00:00

    Try open Command prompt as administrator and then type the following command:

    sfc /scannow and press enter and let it runs and see what is the result.

    Try open start and search for feedback and open the Feedback Hub app and report this issue.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Pokomolo 21 Reputation points
    2021-02-19T22:48:27.59+00:00

    Thanks Reza, I did the "sfc / scannow" but I don't know where to find the "Feedback Hub app".

    0 comments No comments

  2. Pokomolo 21 Reputation points
    2021-02-19T23:18:22.527+00:00

    I managed to find the scan report, it's CBS.log. After running sfc / scannow again it says: "Windows Resource Protection found damaged files, but failed to fix all of them. Details are included in the cbs.log.
    Changes after repairing system files will take effect after the next restart "
    The cbs.log file is really very long, Which part is relevant?

    0 comments No comments