If every single service ran under a one Service Host process, a failure in one service could potentially bring down all of Windows. If you’ve ever taken a look at the Services section in Control Panel, you’ve probably noticed that Windows requires a lot of services. RELATED: What Is This Process and Why Is It Running on My PC? Why Are There So Many Service Host Processes Running? And so the Service Host process (svchost.exe) was born.
Instead, a shell that is loaded from a executable file is used to host these DLL services. The problem is that you can’t launch a DLL file directly from Windows the same way you can an executable file. From a programming perspective, this makes code more reusable and arguably easier to keep up to date. Svchost.exe is a generic host process name for services that run from dynamic-link libraries.īut that doesn’t really help us much. Some time ago, Microsoft started changing much of the Windows functionality from relying on internal Windows services (which ran from EXE files) to using DLL files instead. Here’s the answer, according to Microsoft: This article is part of our ongoing series explaining various processes found in Task Manager, like dwm.exe, ctfmon.exe, mDNSResponder.exe, conhost.exe, rundll32.exe, Adobe_Updater.exe, and many others. Don’t know what those services are? Better start reading! What Is the Service Host Process?
You can’t kill them, and you sure didn’t start them. If you’ve ever browsed through Task Manager, you may have wondered why there are so many Service Host processes running. There are usually many instances of svchost.exe running because Windows requires numerous services to operate correctly. Services are organized into groups, and each group is run inside a different instance of the Service Host Process. The Service Host process (svchost.exe) is a shell for loading services from DLL files.
0 kommentar(er)
