If you have multiple users using your system, then you are most probably assigning them the. 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. 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. Let Standard Users Run Programs as Admin To let standard users run a program with administrator rights, we are going to use the built-in Runas command.

Add in context menu on app. File choice to run without administrative rights. File.reg and add it to the Windows. Install applications without admin. Program Antrenament Sala Arnold.

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. The above action will open the System window. Here you will find your computer name listed.

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.” 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.

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.

Enter the following command at the beginning of the file path. Don’t forget to replace ComputerName and Username with the actual details. Runas /user:ComputerName Username /savecred 'C: path to file.exe' Once you are done, click on the “Next” button to continue. Enter the name of the shortcut and click on the “Finish” button.

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

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.” 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.

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. 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. 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).