I'm in the process of trying to give my computer a speed boost, both on startup and during runtime, and know that windows services can sneakily contribute to consumption of RAM and cpu cycles, but the list of services is pretty extensive, and it can be a little difficult to determine which services constitute core functionality and which services are extraneous and can be changed to manual start. What approach should I take, if any, to analyzing Windows services? Does anyone have a workflow for this? Do you know of a way to identify services which ( a ) consume the most memory and ( b ) are working the most behind the scenes (without being integral to the core operation of my computer)?
Edited by Bebopx86, 03 October 2017 - 10:48 AM.