“The Windows Installer Service could not be accessed"

[Capt.Jack Sparrow]

Unfortunately .NET 3.0 and 3.5 is inbuilt with Windows 7

 

[Chaurigol]

Unfortunately .NET 3.0 and 3.5 is inbuilt with Windows 7

I am aware of that, but what difference does it make?

I found this Automated cleanup tool to remove the .NET Framework 1.0, 1.1, 2.0, 3.0 and 3.5 on the same site, do you think doing that and reinstalling .NET could work?

 

[Chaurigol]

Tried the Cleanup Tool, also disabling/enabling .NET Framework through the Windows Components menu, but nothing... I'm sure its installation is faulty though. Can anyone come up with a way to reinstall/repair .NET Framework without using Windows Installer?

 

[Tepid]

I will say that,,, all my times messing around trying to fix .Net issues (even with direct MS help) have always resulted in taking a shortcut.

Nuke and Reload

I think I have maybe fixed one or 2 total, but they were not that badly messed up.
Once .Net gets royaly hosed,, forget it.

 

[Chaurigol]

It seems so... I finally gave up and reinstalled Windows. I guess we're still not prepared to face this kind of issues on 7.

 

[Tepid]

This is not a Win 7 only issue. This has been since .Net was released. It is a .Net issue, not a Windows version issue.

 

[btlastic]

I am experiencing the exact same problem, and none of the solutions posted on Microsoft KB and any other site worked. I had tried everything Chaurigol did, but none of it solved the problem.

I guess there really isn't a solution to this yet; I'm looking to reinstall Windows soon. That would probably be easier too.

 

[neonlights78]

can we try these? It seems to have worked with few of the guys..

1) Boot OS in Safe Mode.
2) Then in Run Command type msiexec\regserver
3) restart in Normal Mode

Click Start/Run and type:

net start MSIServer

press ENTER and try installing again.

 

[Chaurigol]

I tried that, once of the first fixes I found, but no positive results. Apparently Windows Installer can't be started manually. Would've liked to find the solution anyway, although it isn't useful now... I think the most reasonable thing to do is just forget about it and do a clean install.

 

[Capt.Jack Sparrow]

I tried that, once of the first fixes I found, but no positive results. Apparently Windows Installer can't be started manually. Would've liked to find the solution anyway, although it isn't useful now... I think the most reasonable thing to do is just forget about it and do a clean install.

If you think its .NET Frameworks you could remove .NET from Program Features

 

[Chaurigol]

Tried the Cleanup Tool, also disabling/enabling .NET Framework through the Windows Components menu, but nothing... I'm sure its installation is faulty though. Can anyone come up with a way to reinstall/repair .NET Framework without using Windows Installer?

Been there

 

[stevieray]

Well, I'm a few weeks too late to help, but I'd like to offer a few observations.

A few months ago I had the same issue with the Installer, and tried just about every fix you did... the only thing that fixed it was a custom install.

My problem was a side effect of either:
patching system files for custom themes, or...
modifying explorer for custom start buttons.

Try using this method for installing custom themes... I've had no issues since using Zidane's method. As for custom start orbs... I haven't found another way to use them besides replacing the files in explorer... so I got used to looking at the standard start orb.

Just my 2 cents.