Schedule a task with admin privileges without a user prompt in windows 7












25















In windows 7, I'd like to schedule a program to be run with administrative privileges, without having the user need to respond to a prompt (which requests elevated privileges) every time the scheduled task is run. Is there any way to accomplish this goal without disabling UAC prompts for all applications?



Might not be relevant, but I'm trying to get this program to run at startup.










share|improve this question




















  • 3





    What prompt are they getting now? a task can be scheduled with admin privaleges at the bottom of the first tab, check "Run with highest privaleges"

    – Wutnaut
    Jun 18 '14 at 14:38











  • As for running at startup: on the "triggers" tab choose new, then change the "on a schedule" drop-down to "on startup"

    – Wutnaut
    Jun 18 '14 at 14:39











  • The prompt is for an elevation of privileges to administrator privileges, I'll clarify in the question.

    – notAlex
    Jun 18 '14 at 17:39











  • Sounds like UAC, you'll have to disable it if you don't want your users prompted.

    – Wutnaut
    Jun 18 '14 at 17:46











  • That would work, but its desirable in my case for UAC to still prompt on other non-scheduled applications. I'll clarify again.

    – notAlex
    Jun 18 '14 at 18:29
















25















In windows 7, I'd like to schedule a program to be run with administrative privileges, without having the user need to respond to a prompt (which requests elevated privileges) every time the scheduled task is run. Is there any way to accomplish this goal without disabling UAC prompts for all applications?



Might not be relevant, but I'm trying to get this program to run at startup.










share|improve this question




















  • 3





    What prompt are they getting now? a task can be scheduled with admin privaleges at the bottom of the first tab, check "Run with highest privaleges"

    – Wutnaut
    Jun 18 '14 at 14:38











  • As for running at startup: on the "triggers" tab choose new, then change the "on a schedule" drop-down to "on startup"

    – Wutnaut
    Jun 18 '14 at 14:39











  • The prompt is for an elevation of privileges to administrator privileges, I'll clarify in the question.

    – notAlex
    Jun 18 '14 at 17:39











  • Sounds like UAC, you'll have to disable it if you don't want your users prompted.

    – Wutnaut
    Jun 18 '14 at 17:46











  • That would work, but its desirable in my case for UAC to still prompt on other non-scheduled applications. I'll clarify again.

    – notAlex
    Jun 18 '14 at 18:29














25












25








25


11






In windows 7, I'd like to schedule a program to be run with administrative privileges, without having the user need to respond to a prompt (which requests elevated privileges) every time the scheduled task is run. Is there any way to accomplish this goal without disabling UAC prompts for all applications?



Might not be relevant, but I'm trying to get this program to run at startup.










share|improve this question
















In windows 7, I'd like to schedule a program to be run with administrative privileges, without having the user need to respond to a prompt (which requests elevated privileges) every time the scheduled task is run. Is there any way to accomplish this goal without disabling UAC prompts for all applications?



Might not be relevant, but I'm trying to get this program to run at startup.







windows-7 administrator scheduled-tasks prompt






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 18 '14 at 18:30







notAlex

















asked Jun 18 '14 at 14:27









notAlexnotAlex

132126




132126








  • 3





    What prompt are they getting now? a task can be scheduled with admin privaleges at the bottom of the first tab, check "Run with highest privaleges"

    – Wutnaut
    Jun 18 '14 at 14:38











  • As for running at startup: on the "triggers" tab choose new, then change the "on a schedule" drop-down to "on startup"

    – Wutnaut
    Jun 18 '14 at 14:39











  • The prompt is for an elevation of privileges to administrator privileges, I'll clarify in the question.

    – notAlex
    Jun 18 '14 at 17:39











  • Sounds like UAC, you'll have to disable it if you don't want your users prompted.

    – Wutnaut
    Jun 18 '14 at 17:46











  • That would work, but its desirable in my case for UAC to still prompt on other non-scheduled applications. I'll clarify again.

    – notAlex
    Jun 18 '14 at 18:29














  • 3





    What prompt are they getting now? a task can be scheduled with admin privaleges at the bottom of the first tab, check "Run with highest privaleges"

    – Wutnaut
    Jun 18 '14 at 14:38











  • As for running at startup: on the "triggers" tab choose new, then change the "on a schedule" drop-down to "on startup"

    – Wutnaut
    Jun 18 '14 at 14:39











  • The prompt is for an elevation of privileges to administrator privileges, I'll clarify in the question.

    – notAlex
    Jun 18 '14 at 17:39











  • Sounds like UAC, you'll have to disable it if you don't want your users prompted.

    – Wutnaut
    Jun 18 '14 at 17:46











  • That would work, but its desirable in my case for UAC to still prompt on other non-scheduled applications. I'll clarify again.

    – notAlex
    Jun 18 '14 at 18:29








3




3





What prompt are they getting now? a task can be scheduled with admin privaleges at the bottom of the first tab, check "Run with highest privaleges"

– Wutnaut
Jun 18 '14 at 14:38





What prompt are they getting now? a task can be scheduled with admin privaleges at the bottom of the first tab, check "Run with highest privaleges"

– Wutnaut
Jun 18 '14 at 14:38













As for running at startup: on the "triggers" tab choose new, then change the "on a schedule" drop-down to "on startup"

– Wutnaut
Jun 18 '14 at 14:39





As for running at startup: on the "triggers" tab choose new, then change the "on a schedule" drop-down to "on startup"

– Wutnaut
Jun 18 '14 at 14:39













The prompt is for an elevation of privileges to administrator privileges, I'll clarify in the question.

– notAlex
Jun 18 '14 at 17:39





The prompt is for an elevation of privileges to administrator privileges, I'll clarify in the question.

– notAlex
Jun 18 '14 at 17:39













Sounds like UAC, you'll have to disable it if you don't want your users prompted.

– Wutnaut
Jun 18 '14 at 17:46





Sounds like UAC, you'll have to disable it if you don't want your users prompted.

– Wutnaut
Jun 18 '14 at 17:46













That would work, but its desirable in my case for UAC to still prompt on other non-scheduled applications. I'll clarify again.

– notAlex
Jun 18 '14 at 18:29





That would work, but its desirable in my case for UAC to still prompt on other non-scheduled applications. I'll clarify again.

– notAlex
Jun 18 '14 at 18:29










3 Answers
3






active

oldest

votes


















43















  1. Open Task Scheduler


  2. Create a new task



  3. In the "General" tab - ensure the following settings are entered:




    • "Run whether user is logged on or not"


    • "Run with highest privileges"


    • "Configure For" (your operating system)




  4. In the "Triggers" tab, when adding a trigger (schedule) - ensure that the "Enabled" checkbox is checked



The other tabs need to be looked at as well (actions etc) - but these are the options you should specify when trying to ensure a task runs regardless of which user is logged in, and without the UAC prompts.



When saving the task, you will be prompted to enter a username and password - this username and password is the user that will be used to execute the task. If you are running the task with "highest privileges" you will need to make sure this is an admin account.






share|improve this answer





















  • 1





    The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

    – Synetech
    May 10 '17 at 23:57











  • @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

    – Damian Yerrick
    Jun 8 '17 at 14:27











  • Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

    – boot13
    May 11 '18 at 13:04











  • This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

    – Ε Г И І И О
    May 25 '18 at 14:42



















2














You can provide administrator login. It will work:



enter image description here






share|improve this answer

































    1














    I am reading that the task needs to be scheduled to run under the NT AUTHORITYSYSTEM account, in order to execute the job as an Administrator. "Highest privileges" hasn't produced the same effect for us. Note that in the SYSTEM-run job case, the GUI option is grayed out, so there will be no prompt.






    share|improve this answer

























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f770420%2fschedule-a-task-with-admin-privileges-without-a-user-prompt-in-windows-7%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      43















      1. Open Task Scheduler


      2. Create a new task



      3. In the "General" tab - ensure the following settings are entered:




        • "Run whether user is logged on or not"


        • "Run with highest privileges"


        • "Configure For" (your operating system)




      4. In the "Triggers" tab, when adding a trigger (schedule) - ensure that the "Enabled" checkbox is checked



      The other tabs need to be looked at as well (actions etc) - but these are the options you should specify when trying to ensure a task runs regardless of which user is logged in, and without the UAC prompts.



      When saving the task, you will be prompted to enter a username and password - this username and password is the user that will be used to execute the task. If you are running the task with "highest privileges" you will need to make sure this is an admin account.






      share|improve this answer





















      • 1





        The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

        – Synetech
        May 10 '17 at 23:57











      • @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

        – Damian Yerrick
        Jun 8 '17 at 14:27











      • Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

        – boot13
        May 11 '18 at 13:04











      • This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

        – Ε Г И І И О
        May 25 '18 at 14:42
















      43















      1. Open Task Scheduler


      2. Create a new task



      3. In the "General" tab - ensure the following settings are entered:




        • "Run whether user is logged on or not"


        • "Run with highest privileges"


        • "Configure For" (your operating system)




      4. In the "Triggers" tab, when adding a trigger (schedule) - ensure that the "Enabled" checkbox is checked



      The other tabs need to be looked at as well (actions etc) - but these are the options you should specify when trying to ensure a task runs regardless of which user is logged in, and without the UAC prompts.



      When saving the task, you will be prompted to enter a username and password - this username and password is the user that will be used to execute the task. If you are running the task with "highest privileges" you will need to make sure this is an admin account.






      share|improve this answer





















      • 1





        The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

        – Synetech
        May 10 '17 at 23:57











      • @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

        – Damian Yerrick
        Jun 8 '17 at 14:27











      • Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

        – boot13
        May 11 '18 at 13:04











      • This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

        – Ε Г И І И О
        May 25 '18 at 14:42














      43












      43








      43








      1. Open Task Scheduler


      2. Create a new task



      3. In the "General" tab - ensure the following settings are entered:




        • "Run whether user is logged on or not"


        • "Run with highest privileges"


        • "Configure For" (your operating system)




      4. In the "Triggers" tab, when adding a trigger (schedule) - ensure that the "Enabled" checkbox is checked



      The other tabs need to be looked at as well (actions etc) - but these are the options you should specify when trying to ensure a task runs regardless of which user is logged in, and without the UAC prompts.



      When saving the task, you will be prompted to enter a username and password - this username and password is the user that will be used to execute the task. If you are running the task with "highest privileges" you will need to make sure this is an admin account.






      share|improve this answer
















      1. Open Task Scheduler


      2. Create a new task



      3. In the "General" tab - ensure the following settings are entered:




        • "Run whether user is logged on or not"


        • "Run with highest privileges"


        • "Configure For" (your operating system)




      4. In the "Triggers" tab, when adding a trigger (schedule) - ensure that the "Enabled" checkbox is checked



      The other tabs need to be looked at as well (actions etc) - but these are the options you should specify when trying to ensure a task runs regardless of which user is logged in, and without the UAC prompts.



      When saving the task, you will be prompted to enter a username and password - this username and password is the user that will be used to execute the task. If you are running the task with "highest privileges" you will need to make sure this is an admin account.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited May 12 '16 at 20:47









      DavidPostill

      105k25227261




      105k25227261










      answered Jun 18 '14 at 15:18









      Fazer87Fazer87

      10.4k12639




      10.4k12639








      • 1





        The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

        – Synetech
        May 10 '17 at 23:57











      • @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

        – Damian Yerrick
        Jun 8 '17 at 14:27











      • Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

        – boot13
        May 11 '18 at 13:04











      • This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

        – Ε Г И І И О
        May 25 '18 at 14:42














      • 1





        The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

        – Synetech
        May 10 '17 at 23:57











      • @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

        – Damian Yerrick
        Jun 8 '17 at 14:27











      • Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

        – boot13
        May 11 '18 at 13:04











      • This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

        – Ε Г И І И О
        May 25 '18 at 14:42








      1




      1





      The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

      – Synetech
      May 10 '17 at 23:57





      The problem is that if you use the Run whether user is logged on or not option, the program will not have a GUI (or tray icon). You have to disable that option for it to have a GUI, but then it can only run when the user logs in, which means it cannot run as admin. It’s a frustrating and common catch-22 that Microsoft missed and still seems to ignore.

      – Synetech
      May 10 '17 at 23:57













      @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

      – Damian Yerrick
      Jun 8 '17 at 14:27





      @Synetech If the user is there to use a GUI, the user is there to use the UAC prompt.

      – Damian Yerrick
      Jun 8 '17 at 14:27













      Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

      – boot13
      May 11 '18 at 13:04





      Worked for me. But I don't understand why it was necessary to create a new task for this to start working.

      – boot13
      May 11 '18 at 13:04













      This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

      – Ε Г И І И О
      May 25 '18 at 14:42





      This works. But later I figured that if you happen to "Sleep" your computer, the opened app silently gets closed when waken up. Well at least that happened to Visual Studio.

      – Ε Г И І И О
      May 25 '18 at 14:42













      2














      You can provide administrator login. It will work:



      enter image description here






      share|improve this answer






























        2














        You can provide administrator login. It will work:



        enter image description here






        share|improve this answer




























          2












          2








          2







          You can provide administrator login. It will work:



          enter image description here






          share|improve this answer















          You can provide administrator login. It will work:



          enter image description here







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jul 2 '17 at 18:36









          Donald Duck

          1,46361830




          1,46361830










          answered Jul 2 '17 at 16:06









          Santosh AundhekarSantosh Aundhekar

          211




          211























              1














              I am reading that the task needs to be scheduled to run under the NT AUTHORITYSYSTEM account, in order to execute the job as an Administrator. "Highest privileges" hasn't produced the same effect for us. Note that in the SYSTEM-run job case, the GUI option is grayed out, so there will be no prompt.






              share|improve this answer






























                1














                I am reading that the task needs to be scheduled to run under the NT AUTHORITYSYSTEM account, in order to execute the job as an Administrator. "Highest privileges" hasn't produced the same effect for us. Note that in the SYSTEM-run job case, the GUI option is grayed out, so there will be no prompt.






                share|improve this answer




























                  1












                  1








                  1







                  I am reading that the task needs to be scheduled to run under the NT AUTHORITYSYSTEM account, in order to execute the job as an Administrator. "Highest privileges" hasn't produced the same effect for us. Note that in the SYSTEM-run job case, the GUI option is grayed out, so there will be no prompt.






                  share|improve this answer















                  I am reading that the task needs to be scheduled to run under the NT AUTHORITYSYSTEM account, in order to execute the job as an Administrator. "Highest privileges" hasn't produced the same effect for us. Note that in the SYSTEM-run job case, the GUI option is grayed out, so there will be no prompt.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Jan 11 at 23:50

























                  answered May 17 '17 at 21:49









                  access_grantedaccess_granted

                  1213




                  1213






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f770420%2fschedule-a-task-with-admin-privileges-without-a-user-prompt-in-windows-7%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                      Mangá

                       ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕