Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

"The Windows Installer Service cannot be accessed."


  • Please log in to reply
36 replies to this topic

#1 ForsakenM

ForsakenM

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 04 August 2016 - 06:55 AM

So I'm trying to install the Pokemon TCGO, and every time I get this message:

 

"The Windows Installer Service cannot be accessed. This can occur if you are running in Safe Mode, or if the Windows Installers is not correctly installed. Contact your support personnel for assistance."

 

So I was confused for a number of reasons:

 

  • I'm clearly not in Safe Mode
  • I had already installed multiple different programs before this happened.
  • I can still uninstall programs
  • I can still install some programs, but not others (was able to install another game, but not League of Legends or Microsoft Office)
  • I never made any changes to anything regarding the Windows Installer before this started happening.

So I figured it was just a mishap and restarted the computer...but that didn't fix it.

 

So I tried installing as an administrator...that didn't work either.

 

So I googled the error message, and I found many different ways to approach the situation, but most of them only applied to Windows XP or 2000.

 

I will try to list everything I've attempted up until this point:

 

  • I typed 'msconfig' in Run and checked under Services to make sure Windows Installer was running and was set to manual...which it already was.
  • I checked to make sure it was started, and restarted it just to be sure.
  • I typed in 'regedit' and edited the MSIServer ImagePath value to that of where the actual msiexec.exe was located.
  • I made sure there wasn't an extra msiexec.exe anywhere, of which I could find none.
  • I opened a Command Prompt and attempted to unregister and re-register it. This was done both in and out of Safe Mode.
  • I would have verified the DCOM permissions, but that applies to Windows 2003 only apparently.
  • I made sure the SYSTEM had full permissions and verified it buy going to Run and typing 'regedt32'
  • I opened a Command Prompt and ran and SFC Scan that told me nothing in particular
  • I tried using Tweaking.com's Windows Repair Program
  • I tried putting a block of code into Notepad that I then used to attempt to update/repair the registry
  • I tried using Microsofts Repair System to Troubleshoot. When asked what wasn't installing, it only showed programs that were successfully installed, so I had to choose 'Not Listed' and it always said that I could find nothing wrong
  • I tried to find a way to reinstall the 5.0 Windows Installer Service, but I can only find 4.5 or earlier, so I can't try to reinstall it and see of that fixes it.


    I could really appreciate some help, I have no idea what to do... 

Attached Files


Edited by ForsakenM, 04 August 2016 - 06:56 AM.


BC AdBot (Login to Remove)

 


#2 Will5200

Will5200

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:United States
  • Local time:09:55 PM

Posted 04 August 2016 - 07:47 AM

Some excellent knowledgebase articles:

 

https://support.microsoft.com/en-us/kb/324516

 

https://support.microsoft.com/en-us/kb/2642495

 

(Also the two top search findings in Google).



#3 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 04 August 2016 - 08:36 AM

Some excellent knowledgebase articles:

 

https://support.microsoft.com/en-us/kb/324516

 

https://support.microsoft.com/en-us/kb/2642495

 

(Also the two top search findings in Google).

Already found those sites earlier, already tried what they said.

 

No dice.



#4 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,460 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:07:55 PM

Posted 04 August 2016 - 10:07 AM

I opened a Command Prompt and ran and SFC Scan that told me nothing in particular

 
Unless you received the message "No integrity issues were found" you should post the CBS log in your topic.
 
 
Open the Command Prompt, copy and paste the command below, then press Enter.
 
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
 
This will place a new icon on the desktop titled CBS.  Double click on this icon to open 
the CBS log, copy and paste the log in your topic.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#5 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 04 August 2016 - 03:12 PM

Got it, let me know if this helps determine anything.

Spoiler


#6 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 05 August 2016 - 04:03 PM

BUMP, stil' do not have this resolved.



#7 JohnC_21

JohnC_21

  • Members
  • 23,597 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:55 PM

Posted 05 August 2016 - 04:27 PM

When you re-registered the installer did you also do it for the 64bit component?

 

%windir%\system32\msiexec.exe /unregister

%windir%\syswow64\msiexec.exe /unregister

%windir%\system32\msiexec.exe /regserver

%windir%\syswow64\msiexec.exe /regserver

 



#8 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 05 August 2016 - 10:52 PM

 

When you re-registered the installer did you also do it for the 64bit component?

 

%windir%\system32\msiexec.exe /unregister

%windir%\syswow64\msiexec.exe /unregister

%windir%\system32\msiexec.exe /regserver

%windir%\syswow64\msiexec.exe /regserver

 

 

Swore I tried both already, but I did it again...

 

Nothing, before or after reboot.



#9 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 06 August 2016 - 07:16 PM

Bump, hoping for something I haven't done yet.



#10 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 08 August 2016 - 05:03 PM

Posted my CBS as required, still having the issue, could use some help.

 

BUMP.



#11 JohnC_21

JohnC_21

  • Members
  • 23,597 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:55 PM

Posted 08 August 2016 - 06:18 PM

If you create a new admin account do you still get the error. You have pretty much done everything possible to correct the problem. You maybe looking at a Repair Install. 

 

See this page for another possible solution. If you see any entries under DisabledSessions delete them.

 

http://blog.tiensivu.com/aaron/archives/1823-Windows-7-fix-for-crashing-Windows-Installer-errors-cannot-install-or-uninstall-MSI-packages.html



#12 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 08 August 2016 - 07:05 PM

If you create a new admin account do you still get the error. You have pretty much done everything possible to correct the problem. You maybe looking at a Repair Install. 

 

See this page for another possible solution. If you see any entries under DisabledSessions delete them.

 

http://blog.tiensivu.com/aaron/archives/1823-Windows-7-fix-for-crashing-Windows-Installer-errors-cannot-install-or-uninstall-MSI-packages.html

 

The only one I have is the Default, and I was unable to delete it.

Made a new Admin user and tried it again, still no dice: same issue.

 

I have no WOW64 under the MSIServer, is that an issue for a Windows 7 Home 64-bit user?


Edited by ForsakenM, 08 August 2016 - 07:05 PM.


#13 JohnC_21

JohnC_21

  • Members
  • 23,597 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:55 PM

Posted 08 August 2016 - 07:33 PM

Do you mean there is no msiexec.exe file in the syswow64 folder?

 

Go here. Look for the solution by Mark Schuurman   near the end of the comment section. Always be careful when editing the registry. It would be wise to export the Msiserver registry key.

 

https://blogs.msdn.microsoft.com/astebner/2006/07/20/repairing-the-windows-installer-service-on-a-64-bit-os/



#14 ForsakenM

ForsakenM
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:09:55 PM

Posted 08 August 2016 - 09:10 PM

uggghhhh_zpsu2rwxlui.png

 

So...I did exactly what you said and followed the steps listed, and this is what happened.

 

Well, at least something changed: the prompt looks different now. Is it bad that this feels like progress?

 

Should I try repeating anything I've already done? Does this hint at something else?


Edited by ForsakenM, 08 August 2016 - 09:13 PM.


#15 JohnC_21

JohnC_21

  • Members
  • 23,597 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:55 PM

Posted 09 August 2016 - 07:40 AM

Is the Windows Installer Service enabled? Use the Windows all in one repair again to repair the installer or reregister msiexec.exe in system32 and syswow.

 

I see another potential issue if the Installed Service is not started and set to Automatic. Where the poster said to change the path to

Description:  C:WindowssysWOW64msimsg.dll,-32
Image path:   C:WindowssysWOW64msiexec /V

Are backslashes shown for the Description and Path? If not then change the keys to the following.

Description:  @%SystemRoot%\sysWOW64\msimsg.dll,-32
Image path:   @%SystemRoot%\SysWOW64\msiexec.exe /V

After doing the above then run the unregister and regserver commands again for both system32 and sysWow64  then make sure the Windows Installer Service is started and set to automatic. 

 

 

 

 

 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users