You are reading My night fixing the dreaded “Windows Installer Service could not be accessed” error.. You can leave a comment on or trackback to this post
« Older| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| « Apr | ||||||
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
I spent a long time searching the Internet for a solution to this one. Each of the sites and blogs I found were all partially correct for my specific case. Let me share my symptoms:
At this point I would usually say “Fresh Install” since we are talking about Windows XP here, but I am stubborn sometimes so I poured a big glass of wine and settled in for the night. I had a suspicion from the beginning that this is all the cause of registry permissions, but couldn’t figure out where and why. Excuse me, the wine really kicked in there… Now, the solution.
Here is a link to the MS KB that is actually useful. Here is an excerpt from that KB that is what fixes the problem:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
To reset the registry and file permissions, follow these steps:
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
If this method resolved the error message and if you successfully installed Windows XP SP3, you are finished.
Really, that fixes the issue… except for the fact that you can’t install Subinacl from a stinking MSI if the Windows Installer is not working! Damn Microsoft. Think for just a minute here.
I’m done with that rant. The solution to Microsoft being stupid and limited becuase of the Installer and Registry technology they have designed is to install the Subinacl.msi on another computer, or just extract it and copy the whole Windows Support Tools directory (and subdirectories) to the Program Files folder on the computer having the problem(s). Since the path already includes %systemroot%\Program Files\ anything in there will run just fine from the command line or Start – Run. This is the point where you create the .cmd file from the excerpt or KB article above and run it. At completion you should be able to install XP SP3, remove applications using Add/Remove Programs and run downloaded executables with no problems. You shouldn’t even need to restart your computer.
One more glass of wine and off to bed. Cheers, good luck and hope this helps someone.
1 comment.
Hi there.
Great installation help…thanks, fixed my problem.
Anyone reading this guys stuff should bookmark it.
Names and email addresses are required (email addresses aren't displayed), url's are optional.
Comments may contain the following xhtml tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>