Running a Command script with Run As despite logged on as Admin?

win10freak · 02 Jan 2019

I have two accounts. One being Admin and one being Standard.

How come some program installers or command scripts need for the Run As Admin even if I am logged on as my Admin account?

I thought that being logged on as a Standard account, then there would be always the case to Run As Admin.

But like mentioned, I signed in as the Admin account and some command script gave an error that I need to run it as elevated rights.

Not all scripts or setup files do this, only some.

Next time, is there a way to tell if any apps or command scripts need to do a Run As Admin even if logged on as an Admin account?

AndreTen · 02 Jan 2019

Being logged as Admin doesn't give the programs all rights. Still need to confirm their rights (UAC controlled settings)

win10freak · 02 Jan 2019

Not all scripts or setup files do this, only some.

Next time, is there a way to tell if any apps or command scripts need to do a Run As Admin even if logged on as an Admin account to avoid these types of error messages?

Yes, I have the UAC slider all to the maximum.

Berton · 02 Jan 2019

Also, there is another, hidden/default Administrator account which is inactive and should NEVER be routinely run or on a daily basis, does give even more rights than a User with administrative rights.

win10freak · 02 Jan 2019

Default Admin is disabled.
Created my own Admin when installing Windows.

Next time, is there a way to tell if any apps or command scripts need to perform a Run As Admin even if logged on as an Admin account to avoid these error messages?

Berton · 02 Jan 2019

win10freak said:

Default Admin is disabled.
Created my own Admin when installing Windows.

Next time, is there a way to tell if any apps or command scripts need to perform a Run As Admin even if logged on as an Admin account to avoid these error messages?

Those are not "error" messages but prompts that additional choices have to be made. Only sure way to avoid them is to turn UAC off but that leaves the computer at risk from things like viruses, malware, trojans, etc., and perhaps access from outside such as hackers.

AndreTen · 02 Jan 2019

win10freak said:

Default Admin is disabled.
Created my own Admin when installing Windows.

Next time, is there a way to tell if any apps or command scripts need to perform a Run As Admin even if logged on as an Admin account to avoid these error messages?

Any program that you know it will get access to other program's location, or to check system files, or to write in protected locations, etc., need to be run as elevated. And all should be run as elevated at the state of installation (when writing to Program data or Program file folders).

Only if program is installed in other, non protected areas, it will not need to be elevated.

nice explanation can be found in Brink's tutorial about enabling or disabling UAC

win10freak · 02 Jan 2019

With Run As selected when right clicking on the program, it ran fine.

When I logon to my Admin account, is it recommended to perform a Run As Admin account for all setup files and scripts or for some? Or it really depends on the type of app?

MS Office for example, does not require the Run As Admin. How come?

pbcopter · 02 Jan 2019

win10freak said:

Still confused as to why some apps require elevated rights even when I logon as Admin account?

This is to prevent malware from running when you are logged in as administrator. An administrator must be elevated to get full control.

win10freak · 02 Jan 2019

MS Office for example, does not require the Run As Admin. How come?

I just click on Setup and it installs from the Admin account.