Task Scheduler Fails - Requested Operation Requires Elevation (0x800702E4)

I use a product called SQLBackupAndFTP to do nightly backups of my SQL Server Express development environment.  SQLBackupAndFTP creates a job on the Windows Task Scheduler to make this happen.

It used to work perfectly, but ever since my system has been upgraded to Windows 10 Anniversary Edition, it has stopped working.  Now I get an error message on the Task Scheduler that says, "The requested operation requires elevation. (0x800702E4)"  This seemed odd, since the job is assigned to a user with appropriate privileges, and the "Run with highest privileges" option is set.

As I was researching what may have changed, I discovered the following web page from a separate product called Macrium Reflect.  Macrium describes a bug whereby tasks created using version 1.0 of the Task Scheduler API fail to elevate properly.

http://knowledgebase.macrium.com/display/KNOW/Windows+10+Aniversary+Update+issues

Sure enough, when I deleted the task entry created by the third party software and recreated it by hand in the Task Scheduler interface, it worked perfectly.  The manually created task bypasses the other software's API calls, and then everything works fine.

I just wanted to document this on Microsoft's site, so that other folks may find a workaround to the issue more quickly.

Was this discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

We have the same problem on Windows 10 version 1607.

We use the Task Scheduler API 1.0 to create scheduled tasks, that will run whether user is logged on or not and with highest privileges.

But when we try to execute this task we get the error "The requested operation requires elevation. (0x800702E4)".

We get this error only if the account who execute the task has a session opened.

If we change the execution account to other that has not session opened, it works. Or if we use the default administrator account who doesn't pass through the UAC (User Account Control) to elevate privileges, it works also.

I have not found the report of the problem in the Windows 10 Anniversary Update (Version 1607).

84 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Discussion Info


Last updated April 24, 2023 Views 6,267 Applies to: