Solved Installing using "Run as administrator"

[OldGrantonian]

I'm an administrator on my personal laptop (Win 7 Home Premium). On my company laptop (Win 7 Pro), I have full installation privileges (but not all of the configuration privileges).

Question: In my case, when I want to install a program, is there any difference between the following two sets of actions?:

- Double-click on a file in Win Explorer. In the UAC dialog, click "Yes".
- Right-click on a file. In the popup, select "Run as administrator". In the UAC dialog, click "Yes".

 

[ICIT2LOL]

Hello OG as I read it - it seems you can install any program with either action so I am wondering what is concerning you re the OK for doing installs etc?

What I find rather strange is how come you can install a program yet do not have configuration rights - is that on your own machine as well??

 

[theog]

As you are using Company hardware & software have a word with the Company IT Administrator, to see what rights you have.

 

[ICIT2LOL]

As you are using Company hardware & software have a word with the Company IT Administrator, to see what rights you have.

Hmm was thinking that Theog but you have put it so much more concisely

 

[andrew129260]

Question: In my case, when I want to install a program, is there any difference between the following two sets of actions?:
- Double-click on a file in Win Explorer. In the UAC dialog, click "Yes".
- Right-click on a file. In the popup, select "Run as administrator". In the UAC dialog, click "Yes".

There is a difference, When a program supports uac and you launch it, it will prompt for elevation and give the uac prompt. Older software that is not aware of UAC will need to be right clicked and ran as admin.

 

[OldGrantonian]

(a) When a program supports uac and you launch it, it will prompt for elevation and give the uac prompt.

(b) Older software that is not aware of UAC will need to be right clicked and ran as admin.

I've labelled your responses as (a) and (b).

I think my original question must have been very badly worded, because I don't understand any of the other responses. So far, I've been unable to think of a better way to ask my question. I think your post has provided the opportunity.

Here's the reworded question. For some programs, if I use your method (b), will the installed program present more options than would be available using method (a)?

Reason for question: I never used Vista, because I uninstalled it from a Dell laptop on the same day as it arrived, and I installed my own copy of XP. (At that time, Vista was only about 3 months old, and full of problems.)

But I heard that some programs had a reduced option set if installed under normal user privileges - rather than admin privileges. (Other programs presented the same set of options irrespective of who installed the program.)

Whether or not that is true for Vista is irrelevant - maybe it's all nonsense. But that's the reason I'm asking the question for Windows 7. Better safe than sorry.

Currently, when I install a new program, I automatically double-click on the EXE. It's just a habit from years of XP. As soon as I see the UAC dialog, I close the dialog and start again by right-clicking the EXE.

BTW: To answer the other good posters, who are obviously attempting to be helpful. For my company laptop, here's an example that comes to mind regarding configuration rights. In rare cases, I'm unable to install a program due to the fact that I'm unable to temporarily disable antivirus. (The option is greyed out.) In that case, a Help Desk person takes control of my laptop and installs the program. I can clearly see the AV being disabled, then re-enabled after the install.

On my personal laptop, I can do anything.

Thanks to all the responders.

 

[LMiller7]

In both cases the installer will run as administrator and the installation will proceed exactly the same. It is one of those cases where Windows provides multiple ways of doing the same thing. The "Run as Administrator" option is needed when installing older applications that don't know about UAC. Most installers require administrative rights to function properly. Older applications will simply assume they have them and fail when something doesn't work.

It appears that the computer is a member of a domain and subject to a domain group policy. This can restrict the abilities of even an admin account. IT staff would have access to an account that is not restricted by the policy.

 

[OldGrantonian]

In both cases the installer will run as administrator and the installation will proceed exactly the same.

That sounds fine by me. Problem solved

Thanks for your help.
.