Booting Time, On Windows loading screen

[reddeath]

Right I have tried a load of the things serjested but cant really find any thing that works

on first install of windows 7 (and XP when I was using it) the comp ran fine booted in less than 30secs, but over the couple of weeks it just keeps getting slower and slower now it can take anywhere between 3-5min.
once it has booted to windows log on screen it takes all of a secound to load.

I built my and my brothers comps, there both using the same Mobo/CPU I have 4GB (he has 2GB) but his computer boots faster than mine.

no problems once the comp has started apart from certain settings wont save like where I leave my Icons on DT, and screens staying maximized.

would give boot log but cant remember how to get it...

 

[torrentg]

Set a static ip for slight improvement.

Defrag with O&O while Windows is offline. Run a scheduled task with in the program to do this, for when next time Windows boots.

 

[roban]

It's hard to say why without knowing what programs you have loading at boot. As you add new programs, if they load components your boot time will become longer. Download Mike Lin's startupcpl. It will add a control panel applet which when run, will list all programs that load from every possible location. You can then decide which ones you want to load when starting Windows. It's a free program and I use it all the time.

 

[torrentg]

There's msconfig for that. Startup tab.

Copy and paste to start menu search box.

 

[roban]

There's msconfig for that. Startup tab.

Copy and paste to start menu search box.

Yes but msconfig doesn't list all startup locations.

 

[torrentg]

Yes it does.

 

[reddeath]

neither of these work
drive isnt fragmented at all
and that program only shows things that start during Log on not boot up.

 

[Firestrider]

Try running in diagnostic startup.

Windows key --> Type msconfig and then Enter --> Select diagnostic startup radio button.

If your boot time is much better than you know it's a hanging service or process.

To find exactly what is going on during the boot process and which activity is the culprit you will have to run an xperf trace: Windows Performance Analysis Tools