Don't use msconfig. That is the wrong tool for this. I cannot tell you how sick and tired I am of seeing people recommend msconfig.
If you really want to get into this the correct way, then use Services.msc with the help of Charles "Black Viper" Sparks:
What you can do is this:
- Click a service name on the page (for example, click the first service)
- Read anything he may have typed under "Additional Information". This part sometimes has a description in his own words which is usually a tremendous help to enable you to make your own decision about which setting to use
- Review the Default Description (which is the same description found in Services.msc)
- Once you've decided on a setting (which very well could be the default setting, and that is ok), move on to the next service.
- Repeat this until you've done every service.
- Alternatively, start with his "Safe" settings (in the "Safe" column)
After this, you can Google anything you see in Task Manager's Processes
tab to learn more and to see what you may be able to do about the Process you're Googling.
After that, you can use Black Viper's Super Tweaks:
After this, you can check these three Registry keys and then Google what you find to see what can be safely deleted as well as finding alternative ways to remove what's there (that is, if you find out some of the entries in front of you are unnecessary). Usually, the associated program has an option in its Preferences or Options to remove what you're looking at.
I have never used msconfig, and I never will. There's absolutely no need to use it when my method gets the job done while allowing me to continue using msconfig's "Normal startup".Edited by TwoCables - 4/29/11 at 8:00am