2/3 of Services NOT Needed

Many services are not needed, and can safely be disabled. Black Viper
provides lots of guidance, but it comes down to a tedious trial 'n
error process to reliably determine what's needed and more importantly
what's not.

Services consume resources. e.g. - I found boot times with all enabled
to be far longer than with only those I needed, 50 out of 151.

I have documented everything as captures of the MSCONFIG screens.
Anyone's welcomed to take a look.

wrote:
Many services are not needed, and can safely be disabled. Black Viper
provides lots of guidance, but it comes down to a tedious trial 'n
error process to reliably determine what's needed and more importantly
what's not.

Services consume resources. e.g. - I found boot times with all enabled
to be far longer than with only those I needed, 50 out of 151.

I have documented everything as captures of the MSCONFIG screens.
Anyone's welcomed to take a look.

Services consume resources

Mostly false.

If you look at an individual SVCHOST, say one with 15 services
in it, maybe one or two services consume cycles. The others
are moribund.

The ones consuming cycles, do so when you demand a service from
them. The Windows Update rails a core, when you check Windows Update.
This is a natural result.

For most users, this kind of (Black Viper) customization is excessive.

For an enthusiast trying to get the highest benchmark
on HWBOT, it's probably worth it. Or if you're trying
to get as high a 3DMark out of your overclocked GPU
or something. Enthusiast who do this, likely keep a
"scrap OS" around which is trashed, to do benches.
And they multi-boot an unmodified OS when they want
to send emails or browse the web. Nobody tries to run
a trashed OS, expecting everything on it to work once
they're finished. (Someone in another group, ended up
with no sound on his computer, after overdoing it
with Black Viper. Turns out that sound has a dependency
not documented by Microsoft.)

If all you're doing is reading email and using a
web browser, you don't need any of this.

Maybe your shoes need a shine. If you need a hobby,
look down, see if that shoe is as shiny as it could
be. Then, go get the polish and polish that shoe
so you can see yourself.

The only time I look at services for this purpose, is
when one wastes cycles for no gain. On Windows 10,
I regularly disable SuperFetch, as "part of my religion".
But that's because I've caught it railed, when I was
trying to get something done. Switching it off, meant
the other activity could finish twice as fast.

Windows Defender on Windows 10 is the same way. On
the most extreme cases, I/O rates can rise by a factor
of 7, when Windows Defender is temporarily disabled
on "Real Time Scan". Disabling it, prevents interference
with legit I/O operations.

Paul

Services consume resources

Mostly false.

If there's loaded, there consuming something however minor.

When they're actively doing something uneeded, something else.

And loading takes a lot of boot time which most hate.


But thanks for useful info.

"Paul" wrote

| Services consume resources
|
| Mostly false.
|
| For most users, this kind of (Black Viper) customization is excessive.
|

This has been discussed numerous times. There's
sound logic in leaving it all alone because it takes some
work to figure it out. There's no one-size-fits-all
config for services. For most users, there's no sense
paying attention to anything, just as most people
don't do their own oil changes or monitor their own
medical condition. If something happens, "most people"
will call for help. But there are good reasons to deal
with services:

1) Even if they don't use a lot of resources, it's
increasing the complexity of what's running. There's
no reason to discourage basic housekeeping.

2) Many services are running by default because
the default configuration is corporate workstation.
Many of those services are unsafe and unnecessary
on a stand-alone computer. In short, nothing should
be running that allows anything to call in from
outside unless it's something you specifically need.
And nothing should be calling out unless you need it.
For me that includes anything from Microsoft, including
Windows Update. It also includes frivolous things like
Windows Time. But some people like to keep their clock
accurate to the second. Go figure. For those people
there's Windows Time.

The first time most people knew of all this was when XP
came out and hackers started exploiting the Messenger
service to create scam popups onscreen remotely.
Messenger is designed to allow corporate IT to send out
announcements to all workers, like, "Long weekend coming
up. Please don't forget to turn off lights when you leave
today."

So why was that running on XP by default? Because
Microsoft configures all computers, by default, to be
corporate workstations. What did MS do about it? In
typical finger-in-the-dike fashion they set Messenger
not to run by default. But lots of other things still do.
Remote Registry?.... Don't get me started.

wrote

| And loading takes a lot of boot time which most hate.
|

And also increases the likelihood of boot conflicts.