Unable to install MSI file on Vista Home Premium

[Jordan]

I'm trying to install the Linq preview msi file, but it keeps saying
"The system administrator has set policies to prevent this
installation."

Why can I not perform an install on my on PC?? This is MY home
computer; I AM the administrator.

I've been trying to resolve this for a few evenings on my own and I'm
really frustrated that Microsoft's idea of security is to take away my
rights as the user.

Jordan

 

[Malke]

I'm trying to install the Linq preview msi file, but it keeps saying
"The system administrator has set policies to prevent this
installation."

Why can I not perform an install on my on PC?? This is MY home
computer; I AM the administrator.

I've been trying to resolve this for a few evenings on my own and I'm
really frustrated that Microsoft's idea of security is to take away my
rights as the user.

Have you tried right-clicking on the installation file and choosing "Run
as administrator"? If not, please try that. The Administrator account is
different in Vista than it was in XP.


Malke

 

[Jordan]

Have you tried right-clicking on the installation file and choosing "Run

as administrator"? If not, please try that. The Administrator account is
different in Vista than it was in XP.

Malke

Malke,

Right clicking the msi file does not yield a "Run as administrator"
option. That was my first thought as well. Any other ideas?

Thanks,
Jordan

 

[Jane C]

Hi Jordan,

Can you run regedit.exe (right-click and run it as Admin) and check the
following key:
HKEY_LOCAL_MACHINE > Software > Policies > Microsoft > Windows > Installer

If DisableUserInstalls has a value of 1, change it to 0 (zero) by
right-clicking on it and selecting Modify data.

Do you have any 3rd party security software that has file-protection
capabilities or similar?

 

[Jordan]

Can you run regedit.exe (right-click and run it as Admin) and check the

following key:
HKEY_LOCAL_MACHINE > Software > Policies > Microsoft > Windows > Installer

Jane, I do not have an entry for Installer.

Do you have any 3rd party security software that has file-protection
capabilities or similar?

The only third party software I'm running is my virus scanner.

jordan

 

[Adam Leinss]

Right clicking the msi file does not yield a "Run as
administrator" option. That was my first thought as well. Any
other ideas?

Elevate a command prompt, then type "msiexec /i
name_of_the_program.msi". It should install the MSI with elevated
rights.

Adan

 

[Jordan]

Elevate a command prompt, then type "msiexec /i
name_of_the_program.msi". It should install the MSI with elevated
rights.

Adan

It still returns the same message. Any other ideas?

Jordan

 

[Jordan]

Elevate a command prompt, then type "msiexec /i
name_of_the_program.msi". It should install the MSI with elevated
rights.

Adan

On a whim I re-downloaded the msi file. It is installing as I type
this.

<shrugs>

Jordan

 

[Guest]

Your idea is good, but you need to run msiexec/a

Elevate a command prompt, then type "msiexec /i
name_of_the_program.msi". It should install the MSI with elevated
rights.

Adan

 

[Andrew McLaren]

Your idea is good, but you need to run msiexec/a

I'm not sure that's correct.

"msiexec /a" performs an "administrative" install. But it doesn't grant any
additonal permissions or rights on the install process.

An "administrative install" is an installation to a shared network location,
so that individual machines can then install the application locally from
the network.

To install an MSI file "as administrator", you need to run Msiexec from a
Command Prompt running "as administrator", as Adam Leinss correctly notes.
This applies whether you're doing an administrative install or a normal
install. If you want to install the MSI package on a single machine, then
the "/a" paramter is unnecessary, and probably incorrrect.

If (and only if) the MSI package is configured to request elevation, you can
run the MSI as a normal user, and it will cause the UAC Consent prompt to be
displayed. If the MSI package does not request elevation (eg it is not
UAC-aware), then it will fail with an "access denied" error, if it tries to
updates protected regions of the system (C:\Program Files,
HKEY_LOCAL_MACHINE, etc).

Yes, the terminology is *very* confusing here . The "administrative
install" usage has been around since the early days of the ACME installer,
c1993 or before. Long before Windows had an "Administrator" user.