Windows 7 Corrupted msiexec.exe

[Cloud9ine]

I have been looking into this problem for about a week with no avail, I have tried almost every fix possibly with no solution in sight.

I am unable to install .msi files with the error 1719:

The Windows Installer Service could not be accessed.  This can occur if  you are running Windows in safe mode, or if the Windows Installer is not  correctly installed.  Contact your support personnel for assistance.

I have tried registry fixes, re-registering it, sfc gives me:

2010-08-11 19:47:02, Info                  CSI    00000009 [SR] Verifying 1 components
2010-08-11 19:47:02, Info                  CSI    0000000a [SR] Beginning Verify and Repair transaction
2010-08-11 19:47:02, Info                  CSI    0000000b [SR] Cannot repair member file [l:22{11}]"msiexec.exe" of Microsoft-Windows-Installer-Executable, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2010-08-11 19:47:02, Info                  CSI    0000000c [SR] Cannot repair member file [l:22{11}]"msiexec.exe" of Microsoft-Windows-Installer-Executable, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2010-08-11 19:47:02, Info                  CSI    0000000d [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2010-08-11 19:47:02, Info                  CSI    0000000e Repair results created:
POQ 0 starts:
 
POQ 0 ends.
2010-08-11 19:47:02, Info                  CSI    0000000f [SR] Verify complete
2010-08-11 19:47:02, Info                  CSI    00000010 [SR] Repairing 1 components
2010-08-11 19:47:02, Info                  CSI    00000011 [SR] Beginning Verify and Repair transaction
2010-08-11 19:47:02, Info                  CSI    00000012 [SR] Cannot repair member file [l:22{11}]"msiexec.exe" of Microsoft-Windows-Installer-Executable, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2010-08-11 19:47:02, Info                  CSI    00000013 [SR] Cannot repair member file [l:22{11}]"msiexec.exe" of Microsoft-Windows-Installer-Executable, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2010-08-11 19:47:02, Info                  CSI    00000014 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2010-08-11 19:47:02, Info                  CSI    00000015 Repair results created:
POQ 1 starts:
 
POQ 1 ends.
2010-08-11 19:47:02, Info                  CSI    00000016 [SR] Repair complete

This leads me to believe that msiexec itself could be corrupted as are the back up replacements that sfc would use.

All solutions I see involve toying with the registy or sfc, which in my case wont work. I even tried copying an msiexec from another machine to my own to no avail.

I would like to not have to go through the trouble of a repair install so any help would be appreciated.

Thanks
Cloud_9ine

 

[pcs3657]

Steps To Fix Windows Installer Error 1719

Error 1719 occurs in Windows XP and Windows Server 2003. It has its origins with “Windows Installer” and normally causes the error “Windows Installer Service Could Not Be Accessed”. Installing or uninstalling software can trigger this error and using Windows update also causes it (as this uses the Windows Installer process). To fix this problem, follow the steps in this article…

What Causes Windows Installer Error 1719?

If this error is encountered, the follow error message(s) may appear:

Error 1719. The Windows Installer Service Could Not Be Accessed” Error Message When You Add or Remove Program
​

The 1719 error is caused when files for Windows Installer are either corrupt or missing, which typically occurs when a computer is old or has been used frequently. The error is also known to appear when the user tries to install software that makes use of the Microsoft Windows Installer extension (.msi). If Windows Installer is corrupt or damaged, then the installation process cannot proceed, showing the error. To fix this problem, you can follow the steps below:
How To Fix Error 1719

Step 1 – Reinstall Windows Installer

Reinstalling windows installer will repair any damaged files that this protocol requires, allowing your system to run much more reliably and without the error. The first way to fix this error is to follow these steps:

1. Click Start > Run (search “run” on Vista & Win7)
2. In the “run” applet that appears, type “cmd“. This opens up the command prompt which will let us reinstall Windows Installer.
3. In command prompt enter these commands into it. Make sure they are identical to the following phrases:

cd %windir%\system32attrib -r -s -h dllcache
ren msi.dll msi.bak
ren msiexec.exe msiexec.bak
ren msihnd.dll msihnd.bak
exit
​

Restart your PCafter this to finish the uninstall of Windows Installer. It will then be necessary to install the latest Windows Installer which is available from either Link Removed or Windows update. This process should sort the problem however if it has not then carry on to the next step.
Step 2 – Re-register Windows Installer DLL Files

It’s often the case that some Windows Installer files are not “registered” properly on the system. This is a common problem and it may then be necessary to register them using the following steps.

1. Click Start > Run and in the open box type “ %windir%\system32“.
2. Note the location of the “Msiexec.exe” file on your system. (Default location is C:\Windows\system32\Msiexec.exe)
3. Next, Click Start > Run and, again, in the open box type “Regedit“. Press enter
4. In the window that appears (Registry editing window – be very careful, take care not to alter anything as this is the centre of the Windows operating system), go to this key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services“
5. Click on the MSIServer
6. In the right hand pane should be an option for ImagePath. Right click this entry and select “Modify“
7. (You will need the location of Msiexec.exe now) Type the location of the Msiexec.exe file into the Value Data field and type /V directly after it. (Eg C:\Windows\system32\Msiexec.exe /V). Click OK
8. You can now close the Registry editor window
9. Restart PC in safe mode (Press F8 before Windows Splash Screen appears and select Safe Mode from list)
10. Click Start > Run and type “msiexec /regserver”. Press enter
11. Restart your PC in safe mode as before

This should have have registered the files required for Windows Installer and hereby fixed the problem.

 

[Cloud9ine]

Thanks for the reply I see what is being done but in the 2nd command attrib -r -s -h dllcache it cannot find the file dll cache.

I do get access denied on the renames and also I have yet to find a installer for the installer on the microsoft site (verision 5.something)

 

[pcs3657]

Try using elevated cmd it will help

 

[Cloud9ine]

Ah basically I was an idiot and forgot to mention that I'm using 64 bit Windows 7. 7 does not have the dllcache if I remember correctly. And if I remember correctly a user cannot edit system files w/o taking ownership of it.

 

[cybercore]

Is the software it fails to install Win 7 compatible?

Try CMD -> regsvr32 C:\Windows\system32\msi, and reboot.



~~~~~~~~~


To take ownership of the root drive:

Right-click C:\ drive, Properties. Security tab, Add. In the Select Users, Computers, or Groups dialog box, click the SYSTEM account, click Add, and then click OK. Under Allow, click to select the Full Control check box, and then click OK.


~~~~~~~~~~~~~

Have you tried this fix:

Windows installer Error 1719 - Windows 7 Forums

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver]
"DisplayName"="Instalator Windows"
"ImagePath"=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
  74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,\
  00,73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,20,00,2f,00,\
  56,00,00,00
"Description"="@%SystemRoot%\\system32\\msimsg.dll,-32"
"ObjectName"="LocalSystem"
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000010
"DependOnService"=hex(7):72,00,70,00,63,00,73,00,73,00,00,00,00,00
"ServiceSidType"=dword:00000001
"RequiredPrivileges"=hex(7):53,00,65,00,54,00,63,00,62,00,50,00,72,00,69,00,76,\
  00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,61,00,\
  74,00,65,00,50,00,61,00,67,00,65,00,66,00,69,00,6c,00,65,00,50,00,72,00,69,\
  00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,4c,00,6f,00,63,00,\
  6b,00,4d,00,65,00,6d,00,6f,00,72,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,\
  00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6e,00,63,00,72,00,65,00,61,00,\
  73,00,65,00,42,00,61,00,73,00,65,00,50,00,72,00,69,00,6f,00,72,00,69,00,74,\
  00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,\
  65,00,43,00,72,00,65,00,61,00,74,00,65,00,50,00,65,00,72,00,6d,00,61,00,6e,\
  00,65,00,6e,00,74,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,\
  00,00,53,00,65,00,41,00,75,00,64,00,69,00,74,00,50,00,72,00,69,00,76,00,69,\
  00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,53,00,65,00,63,00,75,00,72,00,\
  69,00,74,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,\
  00,53,00,65,00,43,00,68,00,61,00,6e,00,67,00,65,00,4e,00,6f,00,74,00,69,00,\
  66,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,\
  00,65,00,50,00,72,00,6f,00,66,00,69,00,6c,00,65,00,53,00,69,00,6e,00,67,00,\
  6c,00,65,00,50,00,72,00,6f,00,63,00,65,00,73,00,73,00,50,00,72,00,69,00,76,\
  00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6d,00,70,00,65,00,\
  72,00,73,00,6f,00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,\
  00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,61,00,74,00,65,00,\
  47,00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,\
  00,67,00,65,00,00,00,53,00,65,00,41,00,73,00,73,00,69,00,67,00,6e,00,50,00,\
  72,00,69,00,6d,00,61,00,72,00,79,00,54,00,6f,00,6b,00,65,00,6e,00,50,00,72,\
  00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,52,00,65,00,\
  73,00,74,00,6f,00,72,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,\
  00,65,00,00,00,53,00,65,00,49,00,6e,00,63,00,72,00,65,00,61,00,73,00,65,00,\
  51,00,75,00,6f,00,74,00,61,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,\
  00,65,00,00,00,53,00,65,00,53,00,68,00,75,00,74,00,64,00,6f,00,77,00,6e,00,\
  50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,54,\
  00,61,00,6b,00,65,00,4f,00,77,00,6e,00,65,00,72,00,73,00,68,00,69,00,70,00,\
  50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,4c,\
  00,6f,00,61,00,64,00,44,00,72,00,69,00,76,00,65,00,72,00,50,00,72,00,69,00,\
  76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00
"FailureActions"=hex:84,03,00,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00

 

[Cloud9ine]

It has happened with multiple software installations, all compatible. One user in your link came to the same conclusion I have which is the win7 installer doesn't come in a nice "installer" like it did in XP.

 

[cybercore]

You are absolutely right there is no installer (so far), so the only way is to fix the reg entries manually. You could try one of those registry repair tools:

Link Removed-Microsoft Certified Partner

Registry Repair - Best Free Registry Cleaner

 

[Cloud9ine]

However I have tried multiple registry fixes and I already know that the issue is a corrupt msiexec.exe that sfc fails to fix. sfc would normally replace it, but it seems the replacement sources in SysWOW64 are also corrupt (they at least are not matching the checksums) Might it be possible to get a copy of the dlls and the exe from one machine and to move it onto this machine, change all the permissions to what they normally should be, and then just re-register the program in the registry?