Windows 11 services

inoperable · Apr 8, 2023

SlicEnDicE said:
This is significant

GPU: You can measure it more efficently/reliable during real game play by simply installing reshade its an special injected dll hook
that will attach to the GPU pipeline and allow you to do some fancy things with post processing (extra sharpening etc.. eyecandy basically but can do hell of a difference in rendered frame) and it gives you a overlay fps/latency/timer stats that are much more reliable then some other tools.

SYSTEM: Try SystemInformer (previously known as processhacker, they changed the name since Microsoft was so fond of them and blocked their kernel driver certificate without any reason/feedback as to why...)
I heavily recommend to try it first and then set it as default task manager - task-manager seems like toy in compare.
You can get reliable measurements if I/O, threads, handles, private bytes, disk writes,reads and network incl. firewall in readable fashion.
Services handling with SystemInformer is superior to any other tool known to me (you can easily change permissions if Windows tries to block it with permissions). You can check any all of running process/services true execution arguments instead of useless Task-Manager saying "svchost.exe" which means exactly nil if its run with arguments you aren't able to see (and not differentiate).
SystemInformer needs a bit of tuning in columns that are bing displayed. If you choose the "Command Line" column you will see each running
svchost.exe instance with arguments - makes a lot of difference since you finally can gawk what it does (to a degree)

inoperable · Apr 8, 2023

To get the services count that are currently running you can use this one-line powershell command:

Powershell:

Get-Service -ErrorAction SilentlyContinue | where { $_.Status -eq "Running" }  | Measure-Object -Line

and to get global services count in whatever state they are you can do it with:

Powershell:

Get-Service -ErrorAction SilentlyContinue | Measure-Object -Line

in my case its 55 from 256

Powershell:

Get-Service -ErrorAction SilentlyContinue | where { $_.Status -eq "Running" }  | Measure-Object -Line

Lines Words Characters Property
----- ----- ---------- --------
   55

Code:

Get-Service -ErrorAction SilentlyContinue | where { $_.Status -eq "Stopped" }  | Measure-Object -Line

Lines Words Characters Property
----- ----- ---------- --------
  201

inoperable · Apr 8, 2023

Take note though, that those 201 not running plus 55 running are 256 in all in Windows 10 10.0.19044.2728
I bet those numbers will be much higher on any Windows 11 version

SlicEnDicE · Apr 8, 2023

inoperable said:
Take note though, that those 201 not running plus 55 running are 256 in all in Windows 10 10.0.19044.2728
I bet those numbers will be much higher on any Windows 11 version

You are correct:

This is on latest Build

This is on latest Canary Build

inoperable · Apr 8, 2023

SlicEnDicE said:
You are correct:

This is on latest Build
View attachment 57443

303, that is 21% more then Windows 10 runs with (303 vs. 255)

What is also worth mentioning - stopped status - does not mean that the particular service wasn't running before during current uptime.
It is often so that a service completes whatever it is designed to do and then has an stopped status, but, TaskScheduler can still launch those Services because it has a Task with a timer,trigger that will be executed. To make sure a service is truly disabled it "Start Type" needs to be disabled and you need to be sure there isn't any Task from TaskScheduler capable of changing it on a whimp.

To make it be absolutely sure that neither TaskScheduler or some other init time service will change a service "Start Type" at any point
after you set it t o disabled is to remove all of Permissions of the services, by eradicating all in advanced security tab, disabling inheritance and clicking apply. I do this if nothing else works - so its a lost-resort option.
Odd trivia: wiping all permissions from a Service that normally BSODs Windows during boot seems to be fine with Windows, if you wipe out the permissions from it - it seems as if the services does not exist any more and Windows does not care, still - this is a last resort to get rid of a service since it can brick your system and you will need to revert with booting through Windows Restore and selecting a previous "System Restore Point"

Windows still can tell you "Access Denied" when you try to apply the new 0 permissions - in that case you need to run SystemInformer.exe with highest privilege possible. I use the built-in SYSTEM non-profile account to run cmd.exe first, and then launch any other executable through it making sure SYSTEM is the process owner with all permissions necessary to change Services settings.

inoperable · Apr 8, 2023

I wish there is a easier way to determine the "core" or "essential" or "critical" services to be active so you can login into a session
and have all things you need running and not everything instead