Allen said:
My new netbook is slower now then when I first got it. I have added
nothing and just let it sit there for over a month. By boot is
noticeably longer. I am thinking of removing all the updates and
starting over again and never allowing them to be installed and
compare that system to all the other systems I have. I think the
whole update system sucks. There is no "analyzing" your system to see
what you need and what you don't. Just what updates you don't have.
The time it takes to actually read about each one is time consuming to
no end. Security my butt. This is how each widows OS get bloated IMO.
All parts of the core system will receive updates.
Anything which is a separate add-on (something that required actually
adding software to the computer), will be selectively updated. For
example, if you install .NET 4.0, then expect to start receiving
..NET 4.0 security updates. It wouldn't make sense to deliver those
to you, if .NET 4.0 wasn't on the machine.
The reason the core OS has to be updated, is you could start using
the most obscure feature of the core, at a moments notice. And then,
it could be until the end of the day, before the OS gets updates to
patch and protect that feature. It's better to just keep the store
that holds the core stuff, updated at all times.
If you do decide to "level and reload", keep careful notes. And
be objective about the results. The hard part of your experiment,
is determining when the OS has "finished booting", because modern
OSes have lots of asynchronism, and you could be confusing the
AV software scanning files, for the OS not being finished booting.
That's where a tool like Bootvis would help, with its nice graphs.
I'm surprised Microsoft didn't realize how much people liked those
graphs. I like the look of them. They could have dropped the optimization
portion, and just kept the part that measures boot time.
Paul