Memory management
SvcHostSplitThresholdInKB
Why Windows 10 has so many svchost.exe processes, and what changing it costs
Last updated
Should you change SvcHostSplitThresholdInKB to merge svchost processes?
Since Windows 10 version 1703, machines with more than about 3.5 GB of RAM run most services in their own svchost.exe process instead of grouping them. That is why Task Manager shows dozens. Raising the threshold above your installed RAM reverts to grouping, which reduces process count and a little memory overhead, at the cost of the isolation the split was introduced to provide.
Registry location and values
SvcHostSplitThresholdInKB
- Location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control- Value name
SvcHostSplitThresholdInKB- Type
REG_DWORD- Default
- 380000 (0x5CC80) — approximately 3.6 GB
| Value | What it does |
|---|---|
380000 | Default. Machines with more RAM than this split services into individual processes. |
Above installed RAM in KB | Forces grouping, as on machines below the threshold. E.g. 0x4000000 on a 16 GB machine. |
What Windows actually does with this
Windows compares installed physical memory against this threshold. Above it, each service gets its own svchost.exe. The split exists so that one failing service cannot take down others sharing its process, and so that per-service resource usage is attributable in Task Manager.
What it affects
Number of processes, total memory overhead of the service host processes, and fault isolation between services.
Is it worth changing?
A real trade with a real cost, and not a performance win. Each process carries some overhead, so merging reclaims a modest amount of memory -- typically tens of megabytes, not hundreds. What you give up is that a crashing service now takes its neighbours with it, and that Task Manager can no longer tell you which service is using your CPU. That diagnostic ability is worth more than the memory on any machine with enough RAM to have triggered the split in the first place.
What can go wrong
Reduced fault isolation between services, and much harder troubleshooting when one service misbehaves.
How to undo it
Set the value back to 380000 decimal and restart.
Create a System Restore Point before editing the registry. Every setting on this page is reversible, but a restore point is the difference between undoing one change and reinstalling Windows.
Which Windows versions this applies to
Windows 10 version 1703 and later, Windows 11.
SvcHostSplitThresholdInKB: common questions
Is having 40 svchost processes a sign something is wrong?
No. It is the designed behaviour on any machine with more than about 3.6 GB of RAM. The count is not a symptom.