Task Scheduler - The User account does not have permission to run this task - Upgrade from 2012 R2 to 2019

Question

I upgraded a Windows Server 2012 R2 to Windows Server 2019. Everything works fine after the upgrade except the Task Scheduler. I have 300+ Task running perfectly fine on their schedule however if i try to right click on one of the scheduled task and click run, it throws an error message as "The User account does not have permission to run this task"

Task is created by an account which is part of Administrators group
Task is scheduled to run on an account which is part of Administrators group
C:\Windows\System32\Tasks folder has got full permission for Administrators group

Please let me know if anyone else have faced similar issue with Scheduled task after OS upgrade

Answer 1

This post may be a bit too late but it might help others later. I have the same issue not being able to run a task manually and this is what I did to get it to work.

You basically want to re-create the task. Before you try this, make sure you know the credentials when running the task using a different user account.

To re-create the task using Task Scheduler, export the task to an XML file, delete the task, then import the task XML file. Save the new task which would prompt you for credentials when running the task using a different user account. If you prefer not to delete the old task, you could assign a different task name.

Re-creating the task updates the registry with the permissions needed to run the task.

Answer 2

The user needs to be a member of the administrators group. Prior versions of Windows referenced permissions on C:\Windows\System32\Tasks. Somewhere along the way that changed and security is now in the registry.

Please see the script that I wrote to allow any user to "right click and run a task". Depending on your security requirements, you may need to modify that.

https://social.technet.microsoft.com/Forums/windows/en-US/6b9b7ac3-41cd-419e-ac25-c15c45766c8e/scheduled-task-that-any-user-can-run

Answer 3

Easiest fix is to right-click the job to export the task to XML, rename it in notepad, and then import by right-clicking the task scheduler library. DONE!

Answer 4

Please note that only right click and ADHOC run is throwing an error message and the TASK itself runs on the schedule

Answer 5

Hi,

Check Run with highest privileges:

Please don't forget to mark helpful reply as answer