Inspecting Windows Startup Programs with MSconfig

August 18, 2009

If you are noticing that your boot time is getting longer than usual, you may need to inspect what programs your OS are loading during startup.

To do this you need to click on Start, then Run and on the field type “msconfig” without the quotes then press Enter. You’ll immediately see this window.

The tabs that you see are the different Windows startup files for your system. SYSTEM.INI, WIN.INI, BOOT.INI are text system files which you are better off leaving.

Services are loaded from the registry and best left as well if you have no idea what you are doing. The tab in which you have more freedom to edit is the one labeled Startup which contains the programs that are loaded after your system has initiated all the drivers and services.

You’ll notice when you click on the Startup tab, you’ll see the name of the files that are loaded, its path and other identifying details. By querying the web what the file actually is for, you can tick off each file that can be skipped during startup.

When you uncheck a row, you can always enable it later if its really needed by your system. Which means you’ll have to do a couple of reboots after you uncheck a couple of files and see if your system has improved or not.

Sometimes you’ll uncover that a malicious file is being loaded at startup. This file can be deleted manually which I’ll show in some future posts. Meanwhile, be familiar with your startup files, it will help you in the future when you need to troubleshoot your operating system. ^_^

{ 2 comments… read them below or add one }

Neeraj's Software Discussion August 22, 2009 at 6:20 pm

Msconfig utility is in fact a very useful tool to get a control on what programs start during system startup. Most of the programs are not needed during startup other than a firewall and antivirus. I always keep checking the msconfig utility when my system shows even slightest signs of slowing down. Also, it is a good practice to check, every time we install a software.

Jeedo August 22, 2009 at 8:26 pm

@Neeraj

Thanks for the input. I certainly agree, it doesn’t hurt to be careful. You can also use msconfig to troubleshoot erring startup programs in case error messages are being displayed just before the windows UI is displayed.

Leave a Comment

Previous post:

Next post: