How to Enable Standard Users to Run a Program with Admin Rights without the Password

How to Enable Standard Users to Run A Program with Admin Right Without Giving the Password

If you have multiple users using your system, then you are most probably assigning them the standard user accounts. This allows you to regulate what they install and how they can manipulate the system and application settings. As good as that is, you sometimes may need to allow a standard user to run a program with administrator rights. In those situations, you can use a free third party utility called RunAs Tool. But if you don’t want to use a third-party tool, hre is how you can create your own shortcut of the target program in such a way that it runs with the admin rights without entering any admin password whatsoever.

To let standard users run a program with administrator rights, we are going to use the built-in Runas command. To start, you need to know two things before you can do anything. The first one is the  computer name, and the second one is the username of your administrator account.

If you don’t know the  computer name, press “Win + X,” and then select the “System” option. If you are using Windows 7, you can search for it in the Start menu.

win-run-as-admin-select-system

The above action will open the System window. Here you will find your computer name listed.

win-run-as-admin-computer-name

You can find your administrator username in the User Accounts window.

Once you have the details, you can create the shortcut. To do that, right-click on your desktop and then select the “New” option and then “Create Shortcut.”

win-run-as-admin-new-shortcut

The above action will open the “Create Shortcut” window. Click on the “Browse” button, and select the application you want users to  run with admin rights.

win-run-as-admin-create-shortcut-window

In my case I’m selecting a simple application called Speccy. Though this app only shows the system information and temperatures, it requires admin privileges to work.

After selecting the application, this is how the Create Shortcut window looks.

win-run-as-admin-add-program

Enter the following command at the beginning of the file path. Don’t forget to replace ComputerName and Username with the actual details.

The completed command looks something like this.

win-run-as-admin-add-command

Once you are done, click on the “Next” button to continue.

Enter the name of the shortcut and click on the “Finish” button.

win-run-as-admin-name-shortcut

That’s it. You’ve created a custom shortcut for your program. By default, the shortcut you’ve created will have no proper icon.

win-run-as-admin-shortcut-created

However, you can change the icon by clicking on the “Change Icon” button  from the Properties window. You can access the Properties window by right-clicking on the shortcut and then selecting the option “Properties.”

win-run-as-admin-change-icon

Once you are done changing the icon, double-click on it. For the first time, you need to enter the administrator password. So, enter the admin password and press the Enter button.

win-run-as-admin-launch-program

After the first time, whenever a user launches the application using the shortcut you just created, it will be launched with admin rights. The savecred option in the above command will save the admin password so that users can run the application as an admin without actually entering the password.

In fact, if you open the Windows Credentials Manager and navigate to “Windows Credentials,” you will see the saved password.

win-run-as-admin-credential-manager

If you ever want to restrict the user from running the target app as an administrator, simply delete the shortcut or remove the saved credential from the Windows Credential Manager.

Do comment below sharing your thoughts and experiences about using the above method to let standard users run an application with admin rights.

16 comments

  1. Why would you want to???!!!

    Using this, you are bypassing any shreds of security Windows might have.

  2. Robert, not necessarily. Of course before you do this you need to know everything the elevated application is capable of. If it has functionality that could be used to escalate privilege for other things, don’t do it.
    I see your concern though. And is it even possible beyond the simplest utilities to really know all they are capable of?
    Still, if there is a mission-critical app that has no other decent alternative, this is still much better than granting the user admin rights just to be able to use a single app.

  3. Nice tutorial on using this nifty “Save Credentials” workaround – I can attest to the fact that these ‘elevated’ (i.e., elevated privilege) shortcuts provide a convenient way to prevent UAC (“User Account Control”) from negatively impacting a standard-privilege account’s workflow, as I’ve been creating and using them since UAC was introduced in Windows Vista. One of the things I’ve learned to follow as best practice in creating them is to do so on the desktop of the built-in administrator account, then move the new shortcut to the desktop of the standard user’s account (I always enable the right-click ‘Context Menu’ options “Copy To” & “Move to” to facilitate actions such as this type of moving of files). I might suggest that the tut could be made even better if it’s pointed out that the icon for whatever program one is trying to provide elevated privileges for is typically located in the program’s .exe file itself (or occasionally, inside another file in the same folder, typically a .dll) – especially since clicking the “Change Icon…” button on the Properties sheet will invoke a complaint from Windows that “System32 contains no icons”, and one must then navigate to folder containing the .exe & click on the file to see a list of icons to choose from – Speccy, as is typically the case w/ other of Piriform ‘s handy programs, includes only a single icon, but some programs offer several choices.

  4. Nice guide. But will it work if i need to run the application in elevated privileges. If i right click the shortcut and “run as administrator” it will prompt for the UAC.
    I need this option to allow a user to publish website from Visual studio and he need to run it as administrator, but we dont want to give him local admin rights.

  5. Everything works perfectly until last step. I cannot type password because keyboard is not working. It works with standard command prompt, but when it comes to “Enter the password for..” there is no keyboard. Weird :-(.

  6. Thanks for the guide but I have one question..
    What if the admin forgot the password he’s using and he’s only using his PIN to access his admin account
    in the /savecred, can you set it as PIN instead of password?

  7. Great tipp! I’m just wondering if the changes are the same for all user, I mean, if a PC have 5 User, do I make the changes for each one?

  8. I have the same problem with Tomek B … please help me

    Tomek B
    Everything works perfectly until last step. I cannot type password because keyboard is not working. It works with standard command prompt, but when it comes to “Enter the password for..” there is no keyboard. Weird :-(.

    Nov 1, 2016 at 3:08 pm Reply

  9. By this tutorial you give standard users full administrator permissions on system,
    because the credentials stored in Credential Manager of the users and can be used to start every applications, system tools or program installations.
    The standard users just have to change
    >> runas /user:ComputerNameUsername /savecred “C:pathtofile.exe” <> runas /user:ComputerNameUsername /savecred “C:pathtoanother.exe” <<
    The command can input by command line, batch file, new short cut or any other input option.

    This tutorial is a very good solution for a single user system on computer, who doesn't want to work under administrator account and just want to run some applications as administrator from this limited account.
    This tutorial is not unsuitable for a multiple user system.

    Dany

  10. Bro, Plz Help me. I have done as you have shown above but I am unable to type anything on the cmd when the first time the administrator password is asked. Why is that? Is there any solution?

    • S.A.Rajkumar, as any secured systems, paswords are not visible, it acualy gets writen, but you wont be able to see it.
      This is like on linux, when you writing pasword in console, it hides every symbol that gets writen.

Comments are closed.

Sponsored Stories