On each program you don't want to start automatically, check its
Options to see if it has the choice not to start (make sure you
actually choose the option not to run it, not just a "don't show icon"
option). Many can easily and best be stopped that way.
That really is the best option, else you may find that whenever you
choose to run the app again (or it is launched via file association)
it has added a fresh copy of the integration setting you'd disabled.
That in turn can make things messy, if you want to re-enable all
settings suppressed elsewhere. It also avoids "orphaned" settings
that aren't cleared up when an app is uninstalled.
Finally, if you use multiple tools to reversibly disable things from
the "outside", then the undo process can get snarled up - which did
you use first? What order should they be undone in?
If that doesn't work, run MSCONFIG from the Start | Run line,
and on the Startup tab, uncheck the programs you don't want
to start automatically.
On MSConfig vs. Manage, Services; MSConfig makes it easy to hide MS
services and thus zero in on the 3rd-party additions you prolly won't
need. That's a big win not only over Manage, Services, but many
add-on service managers e.g. Nirsoft's Services and Drivers.
However, if I were you, I wouldn't do this just for the purpose of
running the minimum number of programs. Despite what many people tell
you, you should be concerned, not with how *many* of these programs
you run, but *which*. Some of them can hurt performance severely, but
others have no effect on performance.
Sometimes one may want to do this as a troubleshooting procedure, to
spot what slows down or crashes a system.
If so, the first thing to do, after baseline Safe Mode vs. normal
Windows tests, is to disconnect ALL networking, including all WiFi,
BlueTooth and IR etc. Two reasons:
- these factors may be the cause of your problem
- you may disable defenses and put a connected PC at risk
Once you've done that, you can do a "clean normal boot", i.e. with
everything disabled in MSConfig or whatever. Be careful here; many of
the most thorough tools will let you disable things that really are
part of Windows, so you could disable yourself out of bootability!
From that baseline (assuming it works) you can add back items one or a
few at a time, on a "test to break" basis. This is better that
repeatedly crashing a PC into file-rotting bad exits via repeated
attempts at "test to fix", disabling one thing at a time.
Final tip: Often a single app will have multiple integrations, and
disabling some of these (rather than all or none of these) can trigger
all sorts of bother. It's not easy to know what's part of what.
Don't just stop programs from running willy-nilly. What you should do
is determine what each program is, what its value is to you, and what
the cost in performance is of its running all the time. You can get
more information about these at
http://castlecops.com/StartupList.html. If you can't find it there,
try google searches and ask about specifics here.
Careful with Google searches, for two reasons:
- you may "find" malware sites pushing bad stuff
- you may see innocent items if full log dumps of infected PCs
A lot of the time you'll find forum threads that involve full logs,
usually from HiJackThis. Your browser may highlight the word matches
found in the page, and this may look as if your item was highlighted
in the forum discussion when this may not be the case.
Read carefully...
---------- ----- ---- --- -- - - - -
On the 'net, *everyone* can hear you scream