Grouping multiple services into a single process conserves computing resources, and this consideration was of particular concern to NT designers because creating Windows processes takes more time and consumes more memory than in other operating systems, e.g. in the Unix family.
Problems with various hosted services, particularly with Windows Update,[3][4] get reported by users (and headlined by the press) as involving svchost.
[6] Starting with Windows 10 version 1703, Microsoft changed the way services are grouped into host processes.
On client computer systems with more than 3.5 GB of memory, services are no longer grouped into shared host processes.
In Windows 8, the Task Manager interface was streamlined so that each svchost entry can be expanded by a single click to a sub-list of services running inside it.
[9] A service-aware list of TCP connections and UDP ports opened can be obtained using the command netstat -b.
This debugging process is not foolproof however; in some cases, a heisenbug may occur, which causes the problem to go away when the service is running separately.
[12] In Windows 10, starting with release 1703, svchost was redesigned by Microsoft to host only one service per process, depending on available system memory.