Why is this preventing me installing an MSI: The System Administrator has set policies to prevent this installation
Solution 1
After spending time looking at group policy, as far as I could tell, there was nothing that was relevant. I then came across this post that suggest I try launching a command promt as an administrator and running
msiexec /a install.msi
This appeared to work, but ran very quickly - in fact it didn't. On a whim, I tried this inside the admin command prompt.
msiexec /i install.msi
which worked a treat.
Solution 2
I've run into this behavior, where MSI installation is prevented with "The system administrator has set policies to prevent this installation" before. I believe it is due to default Windows Software Restriction policy and I've seen it on both Windows Server 2008 R2 and Windows Server 2012.
There is probably a better GUI based way to alter the policy, but setting the following reg key as an admin on the machine does the trick:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"DisableMSI"=dword:00000000
Solution 3
This is usually due to a Group Policy or a Local Policy disabling Windows Installer.
Look on your Domain Controller if you have a GPO disabling "Windows Installer": Computer Configuration > Administrative Templates > Windows Components > Windows Installer > "Turn off Windows Installer".
Verify that it is set to "Not configured" or "Disabled".
If if you don't find it in your GPO's, look on the computer's local policies using gpedit.msc.
Note: the fact that you are a domain admins doesn't matter. It all depends of the scope of the GPO.
Solution 4
We had the same exact issue when building an MSI using IsCmdBld.exe
, but not when building from the InstallShield software user interface.
When running the installer, we would see the error mentioned by the OP and the installation log would show: MSI_LUA: Invalid Descriptor Format.
The cause of the problem was that we were passing a ProductCode Guid value to the IsCmdBld.exe command line like this: -z "ProductCode"="f176c219-dec0-4fa9-a373-94a711f28a3d"
.
You can see that the Guid provided here is not surrounded by {
and }
.
We fixed it by passing the guid with brackets around: -z "ProductCode"="{f176c219-dec0-4fa9-a373-94a711f28a3d}"
which works as expected and does not display the error anymore.
Solution 5
right-click -> run as administrator
Related videos on Youtube
Jason Hyland
Updated on September 18, 2022Comments
-
Jason Hyland almost 2 years
I am trying to install an MSI on a Windows Server 2012 machine which is part of my lab domain. I am local and domain admin, but I seem to be prevented from installing this MSI.
For clarification, when attempting to install the git extension for visual studio (located here) logged in as a domain user that is part of the administrator group, I get the following error
The machine reporting the error is a Windows Server 2012.
I'm almost certain it must be some sort of group policy restriction? None will have been set, unless it's the default security level?
For clarification, I'd like to know what is preventing this MSI being installed by a domain admin?
-
Jan Chrbolka almost 9 yearsThis works 100%
-
Dave M over 8 yearsHow is this different than accepted answer?
-
Mike S about 8 yearsThis worked for me. I had to add the "Installer" part of the path as a key, then add the DWORD "DisableMSI" (without the quotes).
-
Jake almost 8 yearsThis works but it can be irritating to do every time you install from an msi. See Armin Sadeghi's answer below for a long-term solution.
-
Jürgen Steinblock almost 7 years
Verify that it is set to "Not configured" or "Disabled".
That's not true. The default (Not Configured) is1
which meansmanaged only
. msdn.microsoft.com/en-us/library/aa368304.aspx Disabled in terms of gpos means the policy will be disabled, so the reg key will be deleted and the default is used. Sound's strange but you have to chooseEnabled
and selectNever
in the dropdown box. -
Kemin Zhou over 5 yearsHad same error message with AcrobatReader update, after change registry to zero install was successful.
-
Harvey Darvey over 4 yearsTried looking for the "DisableMSI" key on the "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer" registry path, but the "Installer" folder does not exist. Should I create an Installer folder and add in the DisableMSI dword?
-
jeffmjack over 4 years@JürgenSteinblock's comment is what fixed it for me on Server 2019.