Yousuf said:
It runs the background services in Windows, such as the print spooler,
plug'n'play, etc., etc. There are usually several instances of svchost
running simultaneously, usually each of these are running several
related services, such as network services, or system services, etc.
Yousuf Khan
You can put one item per svchost.
If you need to debug the system, you can try that, as then,
any svchost which "misbehaves", you simply check what single
thing is living inside it, and it is "guilty as charged".
See:
http://blogs.msdn.com/b/spatdsg/archive/2007/09/17/debugging-services.aspx
"You can split it out into its own service by running:
sc config <service> type= own
And revert it via
sc config <service> type= share
"
That's how you separate all the things jammed together in a svchost.
Svchosts don't seem to be balanced in any way, and it's not unusual
to see one service by itself, and fifteen other services all jammed
into a second svchost. If that svchost is behaving abnormally,
any one of the fifteen things, could be doing it. Which makes this
concept, less than idea from a debugging perspective. And that's
where "type= own" comes in.
Process Explorer may shed some light on what's going on. But
separating them might also work.
Paul