Discussion Locked

2000 Pro startup errors

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been receiving a "svchost.exe" (occurs after the gui has loaded and I have logged in) has failed to start error on bootup of my 2000 pro client (a laptop). I seem to have eliminated it on my home network by making my 2k server a DC. Unfortunately, this doesn't help my laptop while at the office; which makes me wonder if it is really a DC issue, or some other driver.
Thank you for any assistance you can give,
bpc

3 replies

by eric.burke

The following is an excerpt from Microsoft's web site and includes some information that may help you to locate the source of this problem. I'd look for other service warnings prior to this error in the event log.
***************************************
Svchost.exe is a generic host process name for services that are run from dynamic-link libraries (DLLs). The Svchost.exe file is located in the %SystemRoot%\System32 folder. At startup, Svchost.exe checks the services portion of the registry to construct a list of services that it needs to load. There can be multiple instances of Svchost.exe running at the same time. Each Svchost.exe session can contain a grouping of services, so that separate services can be run depending on how and where Svchost.exe is started. This allows for better control and debugging.

Svchost.exe groups are identified in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Svchost
Each value under this key represents a separate Svchost group and is displayed as a separate instance when you are viewing active processes. Each value is a REG_MULTI_SZ value and contains the services that run under that Svchost group. Each Svchost group can contain one or more service_names extracted from the following registry key, whose Parameters key contains a ServiceDLL value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Service

by binarypc

Thank you for the overview. I'm doing a little more investigation into it. The problem seems to have stopped on its own. I think that somehow a group policy or something was being pushed down to my laptop, since I can't recreate it.

This discussion is closed to new replies.