Win XP Home Delay On "Windows Is Starting Up" Screen

Hi,

I have a machine running windows XP Home. When the machine boots it hangs on the blue "Windows Is Starting Up Screen" for quite some time before displaying the logon user account logo's. When you login it also seems to take longer than it should to get desktop up etc considering I have disabled all programs at startup. I have checked and removed all spyware/adware. The machine is running SP1. There are a couple of errors in the Event Viewer which may be related as they appear to occur at boot time:

1) The DCOM Server Process Launcher service hung on starting.

2) The Security Center service failed to start due to the following error:
The executable program that this service is configured to run in does not implement the service.

3) The following boot-start or system-start driver(s) failed to load:
FltMgr

Any help would be greatly appreciated.

Cheers

Paul

well xp is taking long because is trying to startup those services have you try to start then up manually in the computer manager services and applications


or do a repair install of xp http://www.michaelstevenstech.com/XPrepairinstall.htm

Hi,

I tried a repair install but it made no difference. I did however, install SP2 which seems to have cured the problem.

Thanks

Paul

thank you for letting us know :)

For anyone else who has this problem but does not want to risk SP2 yet ...

If you (Start Menu->)Run the command dcomcnfg the Component Services manager widget pops up.

Navigate down to Component Services -> Computers -> My Computer ->
DCOM Config.

When you try to do this it pops up a MessageBox complaining about something
missing in the registry. If you tell it to fix it (twice - another one pops up after
the first, presumably for a different ControlSet or similar), then the DCOM
service starts OK. This seems to be the one that hangs the start-up sequence,
and also fixing this allows half a dozen other problems reported in the Event Log
to go away, presumably because they needed DCOM to work properly.

Searching around, the reason for the long start-up hang is probably a time out, but the DCOM service wants to tell you about its problem but does not have access to whatever it needs to pop up a message, so the starting wrapper
hangs around for the maximum length of time before it gives up.

This does not fix the security center, but I don't think many people care about that as it does not seem very useful. Still - if anyone knows the answer I
would be happy to hear it.

RL