In Windows 10 Creators Update, there are many svchost.exe processes running all the time. If you open the Details tab of the Task Manager in Windows 10 Creators Update, you will be surprised to see a huge number of instances of the svchost.exe process.
Windows is known for having a lot of svchost.exe processes but in Windows 10, they increased even more. Even previous versions of the operating system like Windows 7 and Windows 8.1 had a large number of them. This is because the Svchost.exe (Service host) executable file is used to run various system services. Each instance combines a group of services. According to Microsoft, this model of service management allows reducing the memory consumption and reduces attack surface.
Starting with Windows 10 Creators Update, services are no longer grouped if your PC has sufficient amount of memory. Now, for every service, there is a dedicated svchost.exe process.
This increases the number of Svchost.exe processes dramatically. We explained this change in detail in the article
Today, we'll see how to configure how Windows 10 Creators Update splits up svchost processes. This can be done with a Registry tweak.
To set Split Threshold for Svhost in Windows 10, do the following.
- Open Registry Editor.
- Go to the following Registry key:
Tip: See how to open the desired Registry key directly with one click.
- Here, create or modify a new 32-bit DWORD value named SvcHostSplitThresholdInKB and change its value data from 380000 to an amount just above the total RAM you have in kilobytes (KB).
Enter the new value in decimals. For example, if you have 8 GB of RAM, you should enter the value in decimals as 8388608 (8 GB=8192 MB or 83,88,608 kilobytes). Use Winaero Tweaker to quickly find the amount just above the total RAM you have in kilobytes (KB).
Note: Even if you are running the 64-bit Windows 10 version, you need to use 32-bit DWORD as the value type.
- Restart Windows 10.
Reboot, and there will be no more 70+ processes showing. The behavior of previous versions of Windows will be restored.
Many thanks to our reader Glenn S. for sharing this tweak.