I have a few problems trying to install .msi files in my computer. I have a few executables that I want to run but I can't install them running them as administrator, I normally get the error: Windows installer service could not be accessed.
I tried to open them on command line to get the log from the 2 different MSI files and I get almost an identical result from both logs:
=== Verbose logging started: 1/30/2014 13:38:48 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (D0:30) [13:38:48:733]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (D0:30) [13:38:48:733]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (D0:60) [13:38:48:739]: Resetting cached policy values
MSI (c) (D0:60) [13:38:48:740]: Machine policy value 'Debug' is 0
MSI (c) (D0:60) [13:38:48:740]: ******* RunEngine:
******* Product: C:\Users\TR\Downloads\komodo.msi
******* Action:
******* CommandLine: **********
MSI (c) (D0:60) [13:38:48:746]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (D0:60) [13:38:48:776]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (c) (D0:60) [13:38:48:849]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\TR\Downloads\komodo.msi' against software restriction policy
MSI (c) (D0:60) [13:38:48:849]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (D0:60) [13:38:48:849]: SOFTWARE RESTRICTION POLICY: C:\Users\TR\Downloads\komodo.msi is not digitally signed
MSI (c) (D0:60) [13:38:48:850]: SOFTWARE RESTRICTION POLICY: C:\Users\TR\Downloads\komodo.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (D0:60) [13:38:48:854]: Failed to connect to server. Error: 0x8007000E
MSI (c) (D0:60) [13:38:48:861]: MainEngineThread is returning 1601
=== Verbose logging stopped: 1/30/2014 13:38:48 ===
Any ideas?
Try executing these commands with admin rights after booting your computer in safe mode:
When you launch an MSI, a client process is started (msiexec.exe). This is why you see all these (c) entries in the logs.
There is also an on demand windows service (which also happens to be msiexec.exe) The client autostarts this service and connects to it. This is failing. You can try to see if the service will start manually. If not, try unregistering, reregistering and restarting the service. Examples can be seen here.
This might be specific to that system. Perhaps it's an AV issue or an issue with the OS. If you can create a clean virtual machine OS and your install works there then you'd know it's that specific system.
It's a common error, and this may apply, but I don't know that it should be done on newer OS versions:
Open CMD as administrator
Go to the .msi parent folder for example Downloads
Inside downloads folder type xxxxx.msi
And your installation will run as administrator and you can install your file without problem
User contributions licensed under CC BY-SA 3.0