Services Utility: DCOM Server Process Launcher Service
| Display Name (?): | DCOM Server Process Launcher | ||||||||||||||
| Short Name (?): | DcomLaunch | ||||||||||||||
| Executable (?): | svchost.exe | ||||||||||||||
| Library (?): | rpcss.dll | ||||||||||||||
| Depends On (?): | None. | ||||||||||||||
| Supports (?): | None. | ||||||||||||||
| Description (?): | Provides launch functionality for DCOM services. | ||||||||||||||
| OS (?): | XP Home/Professional, Server 2003 | ||||||||||||||
| Startup (?): |
| ||||||||||||||
Explanation (?): | The DCOM server process launcher service provides fundamental support for the Windows distributed-component object model (DCOM) through the remote procedure call (RPC) system. This service was added into Windows XP with service pack 2 (SP2) as an extension for DCOM/RPC. However, even though this service was added after the release of XP it should not be considered expendable. Even though the system will boot without this service it is an integral component of Windows. Without this service the disk defragmenter (dfrag.msc) will open but won't initiate an analysis or defragment a driver, disk management (diskmgmt.msc) won't be able to connect to the system through RPC, system information (msinfo32.exe) will receive a network error as it also can't communicate to the system, and the Windows Installer will not operate so programs can't be installed. I highly suggest that you leave this service set to automatic. From tests I have performed this service not only allows for interprogram communication but also maintains critical components that can affect stability if this service is not operating. |