Error 0x800710E0 The operator has refused the request (Solved)

Windows Task Scheduler is used to created automated tasks with no user intervention. A couple users, especially system administrators have reported some tasks failing with the message: “The operator or administrator has refused the request (0x800710E0)”.

This issue largely comes as a result of the wrong permissions set during the scheduling. Tasks created with an administrator or system account require the involving applications to run with admin privileges. Such tasks cannot run on normal accounts without any elevated privileges. Another less obvious reason is the power options enabled. If your computer is not running plugged into a power source, you are likely to get this error, unless ofcourse you change this setting.

In this article, we’ll see how to fix this error using by either setting the right privileges or additional settings.

Method 1: Setting User Permissions

Consider the following tips:

  • When creating a task, under the Security options, make sure the right User Account is selected or is spelled correctly. Click on the Change User or Group button to assign the task to the right user or group. Creating a task with an administrator or System user account may not work on a normal users account.
  • Enable the option: Run whether the user is logged on or not if you want the task to run at all times.
  • When you select the Run with highest privileges option, make the user to which the task runs under has the privileges to run it. For example, if the task is supposed to run application X under user A, and the application requires admin privileges but the user isn’t authorized, this error will occur. Make sure the user is part of the administrators group or the application. You can try the following:
  1. Right-click on the application and select Properties.
  2. Select the Security tab and click Edit.
  3. Under the Permissions, select the user account and check the allowed permissions that apply. If the user isn’t available, click on the Add button and add the user.

This tip also applies to folders and not just applications.

Method 2: Changing the Power Setting

If you’re using a laptop rather than a server which is always plugged to AC power, you will get this error is your laptop isn’t connected to a power source. To fix this error, you should make sure the right power settings are applied.

  1. In the new task scheduler window, select the Conditions tab

  2. Under the Power subsection, uncheck Start the task only if the computer is on AC power.

You should check Wake the computer to run this task if you want the task to run when the computer is asleep. This will prevent the error from occurring as a result of the PC being offline.

  1. Run the schedule again to see the the error ceases.

ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

4
    SS
    SSRREEDD Apr 28, 2018

    Thanks.

    I get this 0x800710E0 task scheduler error when I playback videos on full screen even if I check “Run with elevated privileges” option in the task options.

    Is there a way to fight this?

    DO
    Dolphyn5 Aug 15, 2019

    For a task that runs multiple times in a day (hourly, for example), I’ve seen this error occur if the computer wasn’t running at the first start time of the day. In this case, try checking the box for “Run task as soon as possible after a scheduled start is missed.” I haven’t fully tested this, but I think it worked for me.

    LH
    Lord Helmet Oct 9, 2019

    This can also happen if your program/script is paused and waiting for user input for any reason. In my
    case I had a Powershell script that was creating SQL backups and copying them to a backup location, and also deleting any backups that were older than 30 days. It worked fine for the first 30 days (because there was nothing to delete yet), then stopped working and gave the “The operator or administrator has refused the request (0x800710E0)” error in the task scheduler. This was because I did not have the -Recurse option defined in my delete command, running it manually revealed that the Powershell script was sitting with a Y/N confirmation prompt on deleting subfolders and would eventually time out with the “The operator or administrator has refused the request (0x800710E0)” in the task scheduler.

    JU
    Juan Jan 13, 2022

    In my case this error was because in my task I had defined many triggers, each every 5 seconds. However the task took a little bit longer than 5 seconds to be executed, so it gave this error. After deleting some triggers and leaving them every 10 seconds instead of 5, everything was ok.