![]() This process is a vital part of Windows that you cannot prevent from running. This allows Windows to add effects like transparency and live taskbar thumbnails. Then, sort the processes by name and scroll down to “Windows processes.” You’ll see all the processes called “Service Host” and what they’re all doing. The Desktop Window Manager process (dwm.exe) composites the display of application windows before drawing it to your screen. ![]() Open the Processes tab (usually open by default). Make sure you’re looking at the Advanced view by clicking “more details” at the bottom, if it’s there. ![]() If you’d like to take a look for yourself which processes run under svchost, you can do this by holding down Ctrl + Shift + ESC. When you expand one of the main instances, you’ll see any sub-processes listed as well. Each main service may run multiple sub-processes. One thing you will notice when viewing the svchost services is that they’re grouped by type. By having a separate process for each service, it protects the others from being disrupted should one fail. Windows has many services going on at once, so this would be catastrophic! You’d have far more crashes and likely BSoDs (blue screen of death). If Windows packed all of its services into one svchost process, the entire collection of services would collapse should a single one trip up. If a single human worker is injured or ill, the other areas of the factory can still run as normal. The AI may be able to take on all the tasks at once, but if it breaks down, it takes out every job in the factory with it. If you were running a factory, and you had the decision to put a human worker on each task or a central AI robot that handles every task, the humans would be more reliable. The reason behind this decision is to prevent a crash from bringing all the services down. Why doesn’t Windows just bundle all their processes under one svchost and call it a day? Having all these different processes can look untidy. There’s a lot going on within Windows, so it needs all those processes to keep itself running! While it’d be nice if every svchost had a different name, Windows keeps things simple with a single name. When you see multiple svchost.exe processes running at the same time, this simply means Windows is running multiple processes at once. To be more technical, any Windows process from a dynamic link library gets the honor of being called service host or svchost. When Windows wants to run a service, it uses svchost to do so. It means “service host,” and it does exactly that – hosts Windows services. Things make a little more sense when we break down what “svchost” means. In order to understand why they’re so important, however, we need to break down what exactly svchost.exe does. The short answer to this is a definite, strong “no!” Do not force any svchost process to stop! They’re vital for Windows to do its job properly.
0 Comments
Leave a Reply. |