Startup Programs - Change

The tutorial we are posting in has had over a million views without a single complaint.

msconfig might have been considered risky during XP when System files were intermingled with other Startups, but this is no longer the case and now it is up to user preference to use a Startup manager or the more bare-bones msconfig.

You will still get better performance from Win7 with a clean boot running NO startup items except your AV. Compare this with the average factory-preinstalled Windows which has 12-25 preset startups, a horrendous resource hog that makes getting a new computer inferior to running a clean boot.

The only factory-imposed Startup which I've found will balk is HP's useless Wireless Manager which requires selecting Independent Wireless in its Prefs before deselecting in msconfig. Then I would uninstall and bury it in the backyard.

Superhans said:

StalkeR said:

Superhans said:

I was under the impression that using MSConfig to control startup entries was wrong:

Dealing with Startup Processes - MajorGeeks Support Forums

Therefore I use Autoruns.

Nobody forces you to use that method. It's just tutorial,and it helps other people... :)
And yes, Autoruns is also great.

Yes but if the tutorial is giving potentially bad advice, it's worth pointing out. If you disagree with the MajorGeeks forum post and the Microsoft support item, then may I ask why?

Hello Superhans, and welcome to Seven Forums.

The Microsoft article link at Major Geeks that you referenced is a bit out of date since it is for XP.

Plus, how can you say that this tutorial may be giving bad advice when it gives you a lot more options and locations to see your startup programs than the out of date one that you referenced. Not to mention the notes and warnings within the tutorial to help.

There is absolutely nothing wrong with using msconfig to enable or disable startup entries before deciding to want to delete them in the registry or not. msconfig is also a great tool to use to test to see what startup entry may be causing an issue if having one like in these tutorials below.

Troubleshoot Application Conflicts by Performing a Clean Startup

Perform a clean startup to determine whether background programs are interfering with your game or program

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

However, it is true that it would be best to delete the startup entries from the registry instead of just disabling them in msconfig if you do not want them to run at startup anymore. Plus, msconfig may not always show all startup entries like the registry locations would. That being said, there's still nothing wrong with using msconfig to control startup items if one wishes to as long as you are aware this.

You're welcome Superhans. I'm glad that we could help. :)

Hello Seiph, and welcome to Seven Forums.

For services, no.

For startup programs, yes. You could go through the tutorial and move the startup items in all of the "all users" locations to only be in specific users' Startup folders instead. This way there will be no startup items in the "all users" location, and only start items you want in each user's Startup folders.

Hope this helps,
Shawn

Hello Grizz,

That "Run" location in the registry is what runs at startup for all users. I'd recommend to leave them all alone, but you could delete the Adobe and Google one if you want to make sure to manually update the Adobe and Google programs they belong to. Otherwise, it's not going to hurt to leave them. :)

Those items you have listed are for this below in the same order.

• Adobe program updater
• Microsoft Office BCSSync.exe (Business Connectivity Services)
• Google updater

Hope this helps,
Shawn