DCOM Server Process Launcher
12 September 2004 by Snakefoot | Comment » | Trackback OffDescription:
The RPC and DCOM features have been split into two services. This one handles all local requests and runs with Local System privileges. Remote Procedure Call (RPC) handles remote requests and runs with limited Network Service privilege. If an attacker compromises the Remote Procedure Call (RPC), then it will only have limited access to the machine.Note the following things will fail if this service is not running:
- The builtin defrag will fail to work, and if running Defrag.exe from the command line one gets this error:
Windows cannot connect to the Disk Defragmenter engine
- System Information (MsInfo32) will fail to work and give this error:
Can't Collect Information
A network error occurred in connecting to Windows Management Instrumentation. Ensure that your network connection is functioning properly. - If Windows Firewall is enabled, then it will fail to start and all incomming traffic will be blocked. More Info MS KB Q892199
- Disk Management will fail and give this error:
The RPC server is unavailable
- Media Player 10 will fail to burn and sync and give this error:
The RPC server is unavailable
- The install of new applications will fail and give this error:
The InstallShield Engine (iKernel.exe) could not be launched.
The RPC server is unavailable.
Recommended State:
- Automatic
Default State:
- Win8/Win7/Vista: Automatic
- WinXP SP2: Automatic
- Win2k3 SP1: Automatic
Process Name:
- svchost.exe -k DcomLaunch (DcomLaunch)
Supports:
- Remote Procedure Call (RPC) (Vista+)
- Load Session Manager (Win8+)
- Background Task Infrastructure Service (Win8+)
Depends:
- None
Category:
1f89Updated: 13 December 2012
Comment by clogman - 14 February 2008 @ 23:33 Reply
Good info, but….
After sustaining a damaged registry, I found that RPC Server was always unavailable and finally tracked down this link with DCOM. BUT, in Services there is no mention of DCOM on my machine, so how do I re-instate DCOM?
HELP!