We help IT Professionals succeed at work.

Windows 2000 boot up time

fastcpu
fastcpu asked
on
I would appreciate some help on an issue I have with Windows 2000 Professional.
This O/S is a new full installation with a new computer I have, and came with SR1 installed.
I recently downloaded and installed SR2 with no problems, except that the boot up time from "Starting Windows 2000" to the completion of the boot up is now considerably longer. It now takes 3 to 3.5 minutes as opposed to approx 0.5 to 1 minute when SR1 was installed. Appart from this, the system operates normally, and I`ve not installed any additional software. Is there a registry change or some alteration available to speed up this time, or is it normal with this service release. The cpu I have running is an Athalon 1.4 gb Thunderbird, with 512 mb of PC2100 ram and a 64mb G3 video card (3D Power)
Thanks for any suggestions anyone could offer on this.
Comment
Watch Question

Commented:
This isn't the answer you're looking for, but check in the Event Log and see if there are any errors or warnings under the "system log".

If there are post them here and we'll see what we can come up with.

Commented:
Uninstall SP2. If it stops doing that, re-install it. see if that works.

also get a GOOD disk defragmenter -http://www.executivesoftware.com Diskeeper 6 - and possibly a registry cleanup utility.
BRONZE EXPERT
Commented:
fast, boot times are generally increased by drivers and then applications being loaded.

You may want to start by verifying that all of the drivers that are loading, beginning with the motherboard and its devices, are the most current. This alone may speed up the issue.

The next place to look would be any network cards that may be installed (if any) including those used for DSL etc.

Next, take a look at the services and applications that are loading.

Windows 2000 has two separate Run policies: the Windows 2000 Run at Startup policy and the Windows 2000 Legacy Run at Startup policy. Both Microsoft Windows 2000 Professional and Microsoft Windows 2000 Server use these policies. The Windows 2000 Run at Startup policy is similar to the other Windows family of operating systems.
 
One way to modify this list is to open the Microsoft Management Console (MMC) and to add the Group Policy snap-in. Then click Local Computer Policy, click Computer Configuration, and then click Administrative Templates. Click the System object. On the right side of the MMC is a list of Local System policies.
 
One of these is named "Run these programs at user logon". If you double-click on this policy, you can choose to Enable, Disable or Not Configure the policy. To modify the list, you must enable the policy, and then click Show to modify the list of programs to run at Startup. A list of these files can be found in the registry under the following key:
 
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\policies\Explorer\Run
 
The second Run policy involves legacy programs. Many third-party programs such as RealAudio can be included in this category. These programs use a different registry key to configure the program to run at Startup. This registry key (the same registry key that Windows 95/98 and Windows NT use) is located at:
 
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
 
   -or-
 
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
 
Programs that are configured to run at Startup from this registry key are considered legacy programs.
 
Windows 2000 does not enable you modify this list directly from the MMC Group Policy snap-in. Windows 2000 only enables you to Enable or Disable this entire list. To do this, go to the object in the MMC that contains the "Run these programs at user logon" policy. This is explained in the preceding section. Then find the policy called "Disable legacy run list". If you do not want any of your legacy programs to run, you can enable this policy.
 
If you only want to modify the list of legacy programs that run at Startup, you must use either Regedit or Regedt32. Run Regedit or Regedt32, and then go to the registry key:
 
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
 
   -or-
 
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
 
If you do not want a program to run at Startup, find that particular program and delete its entry from one of these registry keys. You can add entries here as well, but it is recommended that you use the Windows 2000 Run at Startup policy to add programs that you want to run at Startup.

Let me know how you make out.
Dennis
BRONZE EXPERT

Commented:
As an additional thought, if you have a CD burner and are using Roxies Easy CD Creator 5.0, you may have some issue to review.

If you have already performed a complete installation of the Easy CD Creator software and are experiencing computer problems, try the following methods to start your computer. After you restart your computer, uninstall the Easy CD Creator software and then reinstall it by using a custom installation without the Take Two module:
 
- If you have a Zip drive, disconnect the cable to the Zip drive. Or, make sure that a disk is inserted in the Zip drive when you turn on the computer. (Always turn the computer off before making any changes to the internal components of your computer.)
 
- Try disconnecting the IDE cable to your CD-R or CD-RW drive. (Always turn the computer off before making any changes to the internal components of your computer.) Does this change the boot time?
 
- Try disconnecting all USB devices that are attached to the computer. Does this help?
 
If you can start Windows, uninstall the Easy CD Creator software. When you reinstall Easy CD Creator, click Custom Install, and then click to clear the Take Two option.

Author

Commented:
Thanks very much to all of you folk for your helpfull advice. I`ll work on it and post a reply. Pity Windows 2000 doesn`t have that handy utility "msconfig" (like the one in Windows 98). Anyway there are other ways to find the same information as suggested by drew associates.

Author

Commented:
Thanks "dew associates" for your comments and suggestions. I`ve accepted your answer as the fix because, with the aid of the "msconfig" utility, I unloaded most of the programs which were loading at boot time. I found that this "msconfig" utility is the one found in Windows XP (not the one found in Windows 98), and because of the affinity of XP with Windows 2000 Pro, this particular version of "msconfig" is compatible with both systems and is very helpful in identifying items which load on boot up.
Thanks also to the other folk who offered suggestions.
BRONZE EXPERT

Commented:
Glad I could help!

Explore More ContentExplore courses, solutions, and other research materials related to this topic.