As a shortcut that might work, you can try running DISM.exe /Online /Cleanup-image /Restorehealth, and run SFC scan afterward to see if it gets fixed on its own, as it did in my case:
Troubleshoot Tree Cache
These are cache files related to the tasks automated via the scheduler. This will have you open the registry editor by typing regedit in the Windows Run.
Next, navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree.
Subsequently, right-click Tree to rename it.
The purpose here is to make this cache ineffective and see the problem status. If the renaming has no effect on the Task Scheduler, then you can safely move to the next solution after reverting this registry folder to its original name (Tree).
But, if it did solve the problem, then one should try renaming the individual files (one at a time) within this folder to pinpoint the corruption.
And since there are always a huge number of entries under the Tree cache, the best is to start with self-made schedules, followed by the schedules set by any recent installs, and lastly, wrestle with the system ones.
Once found, right-click-delete the bad entry, and reboot the system.
Conditions are rules, in addition to triggers, that determine when a particular task should run. You can surf through the conditions of all the tasks in the Task Scheduler dashboard.
However, the options will be grayed out, and one needs to click an entry and right-click to enter properties.
The first thing one can alter is to uncheck the last one: Start only if the following network connection is available. This will help make the specific task run unhindered, irrespective of the connection.
Similarly, you can modify the conditions based on the task at hand.
And again, start with the tasks you made, then the ones created by the recent installs, and leave the system ones for the last.
These are the user accounts meant to run a specific task. And every task has one or more user account(s) linked one can check in the General tab.
Here, the Change User or Group signifies the account for which a specific task runs. This is hardly an issue for a personal computer with a single-user account.
However, you should check for the user account you’re trying to run a task for if you have multiple users. For this, you can click Change user or Group, enter the exact username, and click Check Names.
The easiest way to find out the username for the active account is via the command prompt.
Next, enter that correctly and click Check Names to add it.
Alternatively, click Advanced, and click Find Now on the subsequent screen to get a list of all the users to pick from.
You can also have multiple usernames, which you can enter one at a time.
After adding all the accounts for the subject task, click OK, and see if you’re still stuck with any Task Scheduler hiccups.
This is suitable if a specific task isn’t running.
Navigate to the Triggers section of the Task Scheduler and check every trigger.
For instance, verify if the Enabled at the bottom is checked. In addition, confirm the schedule and, most importantly, check all the triggers for conflicts if there are more than one.
This is another blanket solution that helps sysadmins to come out of many annoying situations.
The steps to perform a clean boot are fairly common, irrespective of the Windows versions that you might have.
First, open Windows Run, type msconfig, and hit enter.
Here, the idea is to disable all non-Microsoft services.
Next, open Task Manager by typing taskmgr in the Windows Run and clicking on Startup at the top menu.
Now screenshot this screen to know which programs are enabled (you’ll need this later) and remove them from the startup by selecting each one and clicking disable.
This step ensures no additional service will initiate on its own when you boot. So this completes the requirement for a clean boot.
Finally, restart your PC and see if the problem persists. If it’s solved, either you can uninstall/reinstall all the extra programs to see if it didn’t resurface.
Alternatively, enable each program and service individually and reboot to catch the bad actor. This process might be long, depending on the number of programs on your system, but that’s the only way to if you want to keep the rest of them.
We hope the Windows Task Scheduler is performing optimally.
But still, some users reported nothing worked for them and ended up reinstalling Windows. And there are various ways, as linked, but the first thing you should do is data backup before proceeding with either resetting, recovery install, or a clean install.