Service grouping (svchosts.exe)

Settings›Tweaks›Service grouping (svchosts.exe)

Recommendation

Situational

Grouping makes sense when RAM is in short supply.

On a modern gaming PC with sufficient memory, it is better to keep the default service isolation. Applying and reverting both require a reboot.

Scope

Service host processes

FPS and memory

See the research

What changes

Windows services run in shared “Service Host” processes (svchost.exe). Windows chooses the degree of grouping itself: with a small amount of memory it combines services into shared processes, with sufficient memory it splits them into separate ones.

The Windows process name is svchost.exe; the setting’s caption in the app contains a typo.

The BoosterX setting selectively combines verified services without enabling global forced grouping: there are fewer processes and memory is saved. The price is fault isolation: if one service in a shared process fails, its neighbors fail too. Applying and reverting require a reboot (according to the visible BoosterX description).

Exceptions and differences

The DocsX research examines the service-splitting threshold in the studied system and shows that manually changing the threshold has no universally confirmed benefit. A failure of one service in a shared process affects its neighbors — evaluate the result not only by the number of processes.

How to verify the result

1. Open Task Manager (Ctrl + Shift + Esc) → the “Processes” tab and count the “Service Host” processes before the change.
2. Enable grouping, reboot and count again: there should be fewer processes.
3. Watch for stability: if a failure of one service starts affecting its neighbors, revert the setting.

How to change and revert

In BoosterX, open “Optimization” → “Tweaks” → “Scheduler and memory” → “Service grouping (svchosts.exe)”, move the toggle to the desired state and click “Apply”. If “Instant apply” is enabled, a separate click is not required. Perform the suggested reboot and check the number of processes.

Confirmation

• Research on service host and background components — the service-splitting threshold, memory savings and loss of isolation.
• Microsoft: Service host grouping in Windows 10 — Windows itself splits services into processes when there is sufficient memory and groups them when there is little, with memory consumption growing when split, verified 2026-09-20.

Last check: 2026-09-19.