Before the Creators Edition was released in March, Windows 10 had about 16 service hosts that supported all services. Since the creators Edition they have split them up so that every service has a service host - this should make it easier to discover which one is using lots of ram, if it is. So whereas before there was 16 its now close to 80.
You only have 10 more processes running than I do, its hardly a lot
Click the Processes tab to see what they are. If you can identify that a lot of them are from unnecessary programs which are starting with Windows you can set those apps to not start with Windows.
Click the Processes tab to see what they are. If you can identify that a lot of them are from unnecessary programs which are starting with Windows you can set those apps to not start with Windows.
In processes tab i have a lot of them named "service host:....."
Click the Processes tab to see what they are. If you can identify that a lot of them are from unnecessary programs which are starting with Windows you can set those apps to not start with Windows.
In processes tab i have a lot of them named "service host:....."
That is normal because they normally use 0% of RAM and use 0% of CPU.
Before the Creators Edition was released in March, Windows 10 had about 16 service hosts that supported all services. Since the creators Edition they have split them up so that every service has a service host - this should make it easier to discover which one is using lots of ram, if it is. So whereas before there was 16 its now close to 80.
You only have 10 more processes running than I do, its hardly a lot