Ikernel.exe problems, Windows Installer Problems, help please.

B

brendanrivers

New Member
Okay, every time I try to install something with Windows installer, I get "Ikernel.exe Could not be launched, RPC Server..." etc. So the supposed fix for this involves going to dcomcnfg.exe, and when I open that, and click on computers, the whole thing closes. I can't install anything I want to, and I need to fix this so I can make protools work, and start a small studio in my basement.


Helpless,
Brendan.
 
That would the DCom server process launcher. You need to go into Control Panel>Administrative Tools>services and make sure that is set to automatic. Otherwise you will to start that up manually. I'll quote the Microsoft workaround if you don't have a Windows id for the link there that also states the same instructions.

"WORKAROUND
To work around this problem, configure the DCOM Server Process Launcher service to start automatically, and then restart the computer. To do this, follow these steps:
1.Log on to the computer by using an account that has administrative permissions.
2.Click Start, point to Administrative Tools, and then click Services.
3.In the Services snap-in, right-click DCOM Server Process Launcher, and then click Properties.
4.In the DCOM Server Process Launcher Properties dialog box, click the list next to Startup type click Automatic, and then click OK.5.Restart the computer."
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b892504
 
hmm

Well It is already set to automatic, do but when I try to "start" it, I get

"Could not start the DCOM Server Process Launcher service on Local Computer.

Error 1503: The service did not respond to the start or control request in a timely fashion"

I know a good bit of computers, but this is crazy talk.
 
Hopefully you can get that file repaired or replaced since that is needed for a little more then just installing programs like defragging your hard drive(s) and a few other services. The system file checker is one tool if you have a Windows full install cd onhand. That compares system files to those found on the cd and will repair/replace any found damaged or missing.

Without having the exact name and command for manually expanding the file from a .cab archive file on the installation disk to write a damaged or missing file there the "sfc /scannow" command at the Run prompt is one method to try. You may be forced into a repair install of Windows(XP) to see this corrected however. A good article with the steps for this is found at http://www.michaelstevenstech.com/XPrepairinstall.htm
 
thanks.

Yeah I know how to do all that stuff, but I was hoping I wouldn't have to reinstall windows, but I guess I do. Guess I'll do that now. THank you for your help, much appreciated.


-Brendan
 
brendanrivers said:
Yeah I know how to do all that stuff, but I was hoping I wouldn't have to reinstall windows, but I guess I do. Guess I'll do that now. THank you for your help, much appreciated.


-Brendan
Click to expand...

The repair install would always be the last option to consider. The manual extraction from a cab file on the installation disk insures a fresh copy of the file is on the drive. That also eliminates any crosslinks that can come up from a bad install of some program. The link at Microsoft is the preferred method for this. Just using the ending the process as seen at the second link posted by StrangleHold is a quicky but not permanent fix if it works.
 
You must log in or register to reply here.
Back
Top