Run as different user and elevate












20















Within Windows Explorer, I can right click on an executable file and pick 'Run as administrator' which will launch the selected process with elevated privileges or I can shift-right click on the executable file and click 'Run as different user', specify the username and password which will launch the process with standard privileges using the specified user context.



How do I run as a different user AND run in an elevated context? A perfect example of this would be opening an elevated command prompt using a different user context that the currently logged in user.










share|improve this question























  • I think powershell the start-process command might be able to do this.

    – jiggunjer
    Jan 17 '16 at 15:02
















20















Within Windows Explorer, I can right click on an executable file and pick 'Run as administrator' which will launch the selected process with elevated privileges or I can shift-right click on the executable file and click 'Run as different user', specify the username and password which will launch the process with standard privileges using the specified user context.



How do I run as a different user AND run in an elevated context? A perfect example of this would be opening an elevated command prompt using a different user context that the currently logged in user.










share|improve this question























  • I think powershell the start-process command might be able to do this.

    – jiggunjer
    Jan 17 '16 at 15:02














20












20








20


6






Within Windows Explorer, I can right click on an executable file and pick 'Run as administrator' which will launch the selected process with elevated privileges or I can shift-right click on the executable file and click 'Run as different user', specify the username and password which will launch the process with standard privileges using the specified user context.



How do I run as a different user AND run in an elevated context? A perfect example of this would be opening an elevated command prompt using a different user context that the currently logged in user.










share|improve this question














Within Windows Explorer, I can right click on an executable file and pick 'Run as administrator' which will launch the selected process with elevated privileges or I can shift-right click on the executable file and click 'Run as different user', specify the username and password which will launch the process with standard privileges using the specified user context.



How do I run as a different user AND run in an elevated context? A perfect example of this would be opening an elevated command prompt using a different user context that the currently logged in user.







windows uac






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 18 '13 at 20:08









ArtArt

1,13211022




1,13211022













  • I think powershell the start-process command might be able to do this.

    – jiggunjer
    Jan 17 '16 at 15:02



















  • I think powershell the start-process command might be able to do this.

    – jiggunjer
    Jan 17 '16 at 15:02

















I think powershell the start-process command might be able to do this.

– jiggunjer
Jan 17 '16 at 15:02





I think powershell the start-process command might be able to do this.

– jiggunjer
Jan 17 '16 at 15:02










5 Answers
5






active

oldest

votes


















17














I don't think such an option exists.



As a work around you could start the command line as an admin and execute the following command to run the command line with admin privileges as the other user.




runas /netonly /user:YourUser cmd.exe







share|improve this answer



















  • 5





    Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

    – JamesTheDev
    Oct 18 '13 at 21:02











  • @NewProgrammerJames Nice, thanks for the input :)

    – Yass
    Oct 18 '13 at 22:22











  • @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

    – Vesper
    Jul 2 '15 at 7:52











  • This will work even if the end user isn't in the admin group?

    – jiggunjer
    Jan 17 '16 at 14:56











  • @jiggunjer No, as far as I know.

    – Yass
    Jan 17 '16 at 14:57



















8














Yes, psexec absolutely does this.



The following example works cleanly on Windows 8.1; run the command prompt as Administrator, then:



// -i makes the app interactive
// -h elevates the execution context
// Omitting the password forces a secure prompt
psexec -u DOMAINuser -i -h "C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEdevenv.exe"





share|improve this answer
























  • From Mike: This works for Windows 10!

    – fixer1234
    Dec 24 '15 at 9:39



















5














You can do it through PowerShell:



Start-Process powershell -Credential domaindifferentUserName -ArgumentList '-noprofile -command &{Start-Process "TheApp.exe" -verb runas}'





share|improve this answer

































    1














    I notice this is a very old question, but the given answers are not ideal and it's already been necroed. All the existing answers require typing archaic commands and knowing the exact path to your executable. An ideal option would make this possible using the same process you already use for privilege escalation.



    If you have a non-Home edition of Windows (Vista thru 10) you can use the Security Policy Manager to make it prompt you to give your password whenever elevation occurs. It also gives you the option to select a completely different user and enter their password... which will cause the elevated process to run as them.



    Simply open the start menu and type secpol.msc and hit enter to launch it (if it's available). You're looking for Local Policies > Security Options > User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode > Prompt for credentials. Vista has a similar option that doesn't mention "Admin Approval Mode" but it does the same thing.



    I think this is a much more natural option than the other's offered here and is rather reminiscent of gksudo on *nix. But if your edition of Windows doesn't include secpol.msc you will have to do some registry hackery to enable it.






    share|improve this answer
























    • I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

      – iroel
      May 6 '18 at 3:02











    • @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

      – Cliff Armstrong
      May 7 '18 at 15:48













    • I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

      – iroel
      Jun 5 '18 at 16:09











    • If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

      – Cliff Armstrong
      Jun 18 '18 at 20:55





















    0














    I found that if I log on as the Run As account you can set the "run this program as administrator" flag on the properties / compatibility page. Then log on the secondary account and perform the shift click run as will open it as administrator.






    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%2f661979%2frun-as-different-user-and-elevate%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      5 Answers
      5






      active

      oldest

      votes








      5 Answers
      5






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      17














      I don't think such an option exists.



      As a work around you could start the command line as an admin and execute the following command to run the command line with admin privileges as the other user.




      runas /netonly /user:YourUser cmd.exe







      share|improve this answer



















      • 5





        Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

        – JamesTheDev
        Oct 18 '13 at 21:02











      • @NewProgrammerJames Nice, thanks for the input :)

        – Yass
        Oct 18 '13 at 22:22











      • @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

        – Vesper
        Jul 2 '15 at 7:52











      • This will work even if the end user isn't in the admin group?

        – jiggunjer
        Jan 17 '16 at 14:56











      • @jiggunjer No, as far as I know.

        – Yass
        Jan 17 '16 at 14:57
















      17














      I don't think such an option exists.



      As a work around you could start the command line as an admin and execute the following command to run the command line with admin privileges as the other user.




      runas /netonly /user:YourUser cmd.exe







      share|improve this answer



















      • 5





        Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

        – JamesTheDev
        Oct 18 '13 at 21:02











      • @NewProgrammerJames Nice, thanks for the input :)

        – Yass
        Oct 18 '13 at 22:22











      • @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

        – Vesper
        Jul 2 '15 at 7:52











      • This will work even if the end user isn't in the admin group?

        – jiggunjer
        Jan 17 '16 at 14:56











      • @jiggunjer No, as far as I know.

        – Yass
        Jan 17 '16 at 14:57














      17












      17








      17







      I don't think such an option exists.



      As a work around you could start the command line as an admin and execute the following command to run the command line with admin privileges as the other user.




      runas /netonly /user:YourUser cmd.exe







      share|improve this answer













      I don't think such an option exists.



      As a work around you could start the command line as an admin and execute the following command to run the command line with admin privileges as the other user.




      runas /netonly /user:YourUser cmd.exe








      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Oct 18 '13 at 20:22









      YassYass

      3,0861013




      3,0861013








      • 5





        Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

        – JamesTheDev
        Oct 18 '13 at 21:02











      • @NewProgrammerJames Nice, thanks for the input :)

        – Yass
        Oct 18 '13 at 22:22











      • @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

        – Vesper
        Jul 2 '15 at 7:52











      • This will work even if the end user isn't in the admin group?

        – jiggunjer
        Jan 17 '16 at 14:56











      • @jiggunjer No, as far as I know.

        – Yass
        Jan 17 '16 at 14:57














      • 5





        Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

        – JamesTheDev
        Oct 18 '13 at 21:02











      • @NewProgrammerJames Nice, thanks for the input :)

        – Yass
        Oct 18 '13 at 22:22











      • @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

        – Vesper
        Jul 2 '15 at 7:52











      • This will work even if the end user isn't in the admin group?

        – jiggunjer
        Jan 17 '16 at 14:56











      • @jiggunjer No, as far as I know.

        – Yass
        Jan 17 '16 at 14:57








      5




      5





      Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

      – JamesTheDev
      Oct 18 '13 at 21:02





      Or you can right click the executable, then select properties>compatability and then select Privilege Level and check Run this program as an administrator. Then shift right click the executable and run as a different user.

      – JamesTheDev
      Oct 18 '13 at 21:02













      @NewProgrammerJames Nice, thanks for the input :)

      – Yass
      Oct 18 '13 at 22:22





      @NewProgrammerJames Nice, thanks for the input :)

      – Yass
      Oct 18 '13 at 22:22













      @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

      – Vesper
      Jul 2 '15 at 7:52





      @NewProgrammerJames This trick doesn't work with CMD directly on W2008R2 and above, but tweaking a custom app should be possible.

      – Vesper
      Jul 2 '15 at 7:52













      This will work even if the end user isn't in the admin group?

      – jiggunjer
      Jan 17 '16 at 14:56





      This will work even if the end user isn't in the admin group?

      – jiggunjer
      Jan 17 '16 at 14:56













      @jiggunjer No, as far as I know.

      – Yass
      Jan 17 '16 at 14:57





      @jiggunjer No, as far as I know.

      – Yass
      Jan 17 '16 at 14:57













      8














      Yes, psexec absolutely does this.



      The following example works cleanly on Windows 8.1; run the command prompt as Administrator, then:



      // -i makes the app interactive
      // -h elevates the execution context
      // Omitting the password forces a secure prompt
      psexec -u DOMAINuser -i -h "C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEdevenv.exe"





      share|improve this answer
























      • From Mike: This works for Windows 10!

        – fixer1234
        Dec 24 '15 at 9:39
















      8














      Yes, psexec absolutely does this.



      The following example works cleanly on Windows 8.1; run the command prompt as Administrator, then:



      // -i makes the app interactive
      // -h elevates the execution context
      // Omitting the password forces a secure prompt
      psexec -u DOMAINuser -i -h "C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEdevenv.exe"





      share|improve this answer
























      • From Mike: This works for Windows 10!

        – fixer1234
        Dec 24 '15 at 9:39














      8












      8








      8







      Yes, psexec absolutely does this.



      The following example works cleanly on Windows 8.1; run the command prompt as Administrator, then:



      // -i makes the app interactive
      // -h elevates the execution context
      // Omitting the password forces a secure prompt
      psexec -u DOMAINuser -i -h "C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEdevenv.exe"





      share|improve this answer













      Yes, psexec absolutely does this.



      The following example works cleanly on Windows 8.1; run the command prompt as Administrator, then:



      // -i makes the app interactive
      // -h elevates the execution context
      // Omitting the password forces a secure prompt
      psexec -u DOMAINuser -i -h "C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEdevenv.exe"






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Dec 7 '15 at 22:29









      Paul SmithPaul Smith

      236136




      236136













      • From Mike: This works for Windows 10!

        – fixer1234
        Dec 24 '15 at 9:39



















      • From Mike: This works for Windows 10!

        – fixer1234
        Dec 24 '15 at 9:39

















      From Mike: This works for Windows 10!

      – fixer1234
      Dec 24 '15 at 9:39





      From Mike: This works for Windows 10!

      – fixer1234
      Dec 24 '15 at 9:39











      5














      You can do it through PowerShell:



      Start-Process powershell -Credential domaindifferentUserName -ArgumentList '-noprofile -command &{Start-Process "TheApp.exe" -verb runas}'





      share|improve this answer






























        5














        You can do it through PowerShell:



        Start-Process powershell -Credential domaindifferentUserName -ArgumentList '-noprofile -command &{Start-Process "TheApp.exe" -verb runas}'





        share|improve this answer




























          5












          5








          5







          You can do it through PowerShell:



          Start-Process powershell -Credential domaindifferentUserName -ArgumentList '-noprofile -command &{Start-Process "TheApp.exe" -verb runas}'





          share|improve this answer















          You can do it through PowerShell:



          Start-Process powershell -Credential domaindifferentUserName -ArgumentList '-noprofile -command &{Start-Process "TheApp.exe" -verb runas}'






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jul 13 '17 at 2:04









          Pimp Juice IT

          24.2k113974




          24.2k113974










          answered Jul 12 '17 at 21:46









          Darío LeónDarío León

          5111




          5111























              1














              I notice this is a very old question, but the given answers are not ideal and it's already been necroed. All the existing answers require typing archaic commands and knowing the exact path to your executable. An ideal option would make this possible using the same process you already use for privilege escalation.



              If you have a non-Home edition of Windows (Vista thru 10) you can use the Security Policy Manager to make it prompt you to give your password whenever elevation occurs. It also gives you the option to select a completely different user and enter their password... which will cause the elevated process to run as them.



              Simply open the start menu and type secpol.msc and hit enter to launch it (if it's available). You're looking for Local Policies > Security Options > User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode > Prompt for credentials. Vista has a similar option that doesn't mention "Admin Approval Mode" but it does the same thing.



              I think this is a much more natural option than the other's offered here and is rather reminiscent of gksudo on *nix. But if your edition of Windows doesn't include secpol.msc you will have to do some registry hackery to enable it.






              share|improve this answer
























              • I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

                – iroel
                May 6 '18 at 3:02











              • @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

                – Cliff Armstrong
                May 7 '18 at 15:48













              • I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

                – iroel
                Jun 5 '18 at 16:09











              • If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

                – Cliff Armstrong
                Jun 18 '18 at 20:55


















              1














              I notice this is a very old question, but the given answers are not ideal and it's already been necroed. All the existing answers require typing archaic commands and knowing the exact path to your executable. An ideal option would make this possible using the same process you already use for privilege escalation.



              If you have a non-Home edition of Windows (Vista thru 10) you can use the Security Policy Manager to make it prompt you to give your password whenever elevation occurs. It also gives you the option to select a completely different user and enter their password... which will cause the elevated process to run as them.



              Simply open the start menu and type secpol.msc and hit enter to launch it (if it's available). You're looking for Local Policies > Security Options > User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode > Prompt for credentials. Vista has a similar option that doesn't mention "Admin Approval Mode" but it does the same thing.



              I think this is a much more natural option than the other's offered here and is rather reminiscent of gksudo on *nix. But if your edition of Windows doesn't include secpol.msc you will have to do some registry hackery to enable it.






              share|improve this answer
























              • I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

                – iroel
                May 6 '18 at 3:02











              • @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

                – Cliff Armstrong
                May 7 '18 at 15:48













              • I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

                – iroel
                Jun 5 '18 at 16:09











              • If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

                – Cliff Armstrong
                Jun 18 '18 at 20:55
















              1












              1








              1







              I notice this is a very old question, but the given answers are not ideal and it's already been necroed. All the existing answers require typing archaic commands and knowing the exact path to your executable. An ideal option would make this possible using the same process you already use for privilege escalation.



              If you have a non-Home edition of Windows (Vista thru 10) you can use the Security Policy Manager to make it prompt you to give your password whenever elevation occurs. It also gives you the option to select a completely different user and enter their password... which will cause the elevated process to run as them.



              Simply open the start menu and type secpol.msc and hit enter to launch it (if it's available). You're looking for Local Policies > Security Options > User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode > Prompt for credentials. Vista has a similar option that doesn't mention "Admin Approval Mode" but it does the same thing.



              I think this is a much more natural option than the other's offered here and is rather reminiscent of gksudo on *nix. But if your edition of Windows doesn't include secpol.msc you will have to do some registry hackery to enable it.






              share|improve this answer













              I notice this is a very old question, but the given answers are not ideal and it's already been necroed. All the existing answers require typing archaic commands and knowing the exact path to your executable. An ideal option would make this possible using the same process you already use for privilege escalation.



              If you have a non-Home edition of Windows (Vista thru 10) you can use the Security Policy Manager to make it prompt you to give your password whenever elevation occurs. It also gives you the option to select a completely different user and enter their password... which will cause the elevated process to run as them.



              Simply open the start menu and type secpol.msc and hit enter to launch it (if it's available). You're looking for Local Policies > Security Options > User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode > Prompt for credentials. Vista has a similar option that doesn't mention "Admin Approval Mode" but it does the same thing.



              I think this is a much more natural option than the other's offered here and is rather reminiscent of gksudo on *nix. But if your edition of Windows doesn't include secpol.msc you will have to do some registry hackery to enable it.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jul 12 '17 at 22:02









              Cliff ArmstrongCliff Armstrong

              1,224112




              1,224112













              • I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

                – iroel
                May 6 '18 at 3:02











              • @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

                – Cliff Armstrong
                May 7 '18 at 15:48













              • I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

                – iroel
                Jun 5 '18 at 16:09











              • If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

                – Cliff Armstrong
                Jun 18 '18 at 20:55





















              • I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

                – iroel
                May 6 '18 at 3:02











              • @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

                – Cliff Armstrong
                May 7 '18 at 15:48













              • I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

                – iroel
                Jun 5 '18 at 16:09











              • If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

                – Cliff Armstrong
                Jun 18 '18 at 20:55



















              I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

              – iroel
              May 6 '18 at 3:02





              I did this and it doesn't work. And it always asks for my fingerprint instead although I don't configure my fingerprint auth.

              – iroel
              May 6 '18 at 3:02













              @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

              – Cliff Armstrong
              May 7 '18 at 15:48







              @iroel That sounds distinct like there is a configuration problem with your windows' authentication subsystems. You should consider searching SU for a solution to that problem and, if you find nothing, consider posting it as a question. All my systems are set up this way and none of them ask for a thumbprint. Depending on the account I'm authenticating as they ask for either a password or a pin number.

              – Cliff Armstrong
              May 7 '18 at 15:48















              I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

              – iroel
              Jun 5 '18 at 16:09





              I use fingerprint for authentication. It does happens. 2 solutions that are applicable: make the user having administrative privilege (but it doesn’t make sense in this case), create another user and set the fingerprint (use finger that’s not registered for certain user) and use that finger when asked for elevated privilege. I use the last solution in this case. At least it works for me.

              – iroel
              Jun 5 '18 at 16:09













              If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

              – Cliff Armstrong
              Jun 18 '18 at 20:55







              If you're being prompted for a fingerprint then either you have set up the user you are trying to log into to require a fingerprint or something is wrong with your installation of windows. Full stop. I use this setup on three different computers and none of them ask for fingerprints. I've set this up on dozens of computers for clients. Windows will prompt for a pin# when logging into a user with a pin# configured and a password for all other users. It uses whatever authentication method you have configured for that user.

              – Cliff Armstrong
              Jun 18 '18 at 20:55













              0














              I found that if I log on as the Run As account you can set the "run this program as administrator" flag on the properties / compatibility page. Then log on the secondary account and perform the shift click run as will open it as administrator.






              share|improve this answer




























                0














                I found that if I log on as the Run As account you can set the "run this program as administrator" flag on the properties / compatibility page. Then log on the secondary account and perform the shift click run as will open it as administrator.






                share|improve this answer


























                  0












                  0








                  0







                  I found that if I log on as the Run As account you can set the "run this program as administrator" flag on the properties / compatibility page. Then log on the secondary account and perform the shift click run as will open it as administrator.






                  share|improve this answer













                  I found that if I log on as the Run As account you can set the "run this program as administrator" flag on the properties / compatibility page. Then log on the secondary account and perform the shift click run as will open it as administrator.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 4 at 17:31









                  Alan ThompsonAlan Thompson

                  1




                  1






























                      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%2f661979%2frun-as-different-user-and-elevate%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

                      "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                      Alcedinidae

                      RAC Tourist Trophy