Looooong pause during XP startup

TechGuy71

New Member
Reaction score
0
Have a computer in the seems to be booting fine. Desktop appears and system tray begins to populate. Then there is a very long (minutes) pause where nothing happens. The cursor will move but that's about it. After a while it seems to kick into gear again and its finished. Seems to run fine after that. I've been at this for days and just can't figure out what is hanging it up. If I post a bootvis file or something would that help? I've tried "everything".
 
1) is it on a domain and looking for the domain on boot?

2) Are there any mapped drives that it may be looking for?

3) Does it do the same thing when the network is unplugged or disabled?

4) Does it do this when booting to Safe mode? If yes - what about Safe mode without networking?
 
When I run bootvis I noticed that fltmgy.sys under driver delays is taking quite a long time. But it seems like a pretty generic process from what I read. Can't really narrow it down to anything.

EDIT: fltmgr.sys - not fltmgy.sys
 
Last edited:
1) is it on a domain and looking for the domain on boot?

2) Are there any mapped drives that it may be looking for?

3) Does it do the same thing when the network is unplugged or disabled?

4) Does it do this when booting to Safe mode? If yes - what about Safe mode without networking?


Nope, no mapped drive or domains.

Makes no difference whether the ethernet is plugged in or not.

Safe mode seems to boot normally
 
Have you done any diagnostics? Your first step if to determine if it's a software issue or a hardware issue, so get to


Originally I thought I nailed the problem via a BIOS setting. It was set to raid which was causing disk caching to be turned off. Ultimately it didn't make a difference in speed. Bootvis does randomly report that disk caching is disabled, but it isn't so that confuses me a bit. I have tested the drive and don't see a problem with it.
 
next set of q's

1) does the machine have magic iso installed?

2) does the machine have roxio installed?

3) does the same issue occur on a different profile or is it profile specific?

4) is the hdd set to ide or sata mode?
 
next set of q's

1) does the machine have magic iso installed?

2) does the machine have roxio installed?

3) does the same issue occur on a different profile or is it profile specific?

4) is the hdd set to ide or sata mode?


No magic iso

No roxio - has sonic... and nero

There's only 1 profile

It's a SATA drive coming up as UDMA Mode 5
 
Last edited:
Does he have blackberry software installed? And to help us out, what programs are listed in msconfig for start up and what non-ms services are listed?
 
Does he have blackberry software installed? And to help us out, what programs are listed in msconfig for start up and what non-ms services are listed?

I was just about to ask about this. Yes, it does have blackberry software installed. Could it be that's it searching for a blackberry to sync during this period? Is there a way to test this without actually uninstalling it?

I will list the msconfig data in another post
 
Turn off the bb software from auto starting. It does nothing unless his phone is connected. It almost always slows down start time.
 
No roxio - has sonic... and nero
Are you sure? BB Desktop Manager include Roxio Media manager to mange the media on the BB.

reason : the Desktop Manager is launched when you start your Windows session, including its (very slow) module called Roxio Media Manager.
Action to perform : do not launch the Desktop Manager & Media Manager
How to do it :
when it's launched, you have a small icon in the system tray next to the clock, if you right click on it you can open a small window with several litttle tabs. On one of those tabs, there is a box you can uncheck so that Desktop Manager does not launch when you open a session.

bottom line : Desktop Manager will take 2:30 min to launch when you need it.
 
Bootvis will do you no good in this situation because whats slowing the computer up happens after bootvis compiles its report.

This has been happening to me a lot during tuneups. You need to use process explorer and watch what processes start right as the system becomes usable. Those are likely whats holding it up. I have found a lot of problems lately with dot-net 4 client profile. I don't even install the update anymore because of the problems it causes.
 
Are you sure? BB Desktop Manager include Roxio Media manager to mange the media on the BB.

reason : the Desktop Manager is launched when you start your Windows session, including its (very slow) module called Roxio Media Manager.
Action to perform : do not launch the Desktop Manager & Media Manager
How to do it :
when it's launched, you have a small icon in the system tray next to the clock, if you right click on it you can open a small window with several litttle tabs. On one of those tabs, there is a box you can uncheck so that Desktop Manager does not launch when you open a session.

bottom line : Desktop Manager will take 2:30 min to launch when you need it.


Yah you're right Chris. Roxio is part of the BB software. It doesn't show up anywhere though. I went in to keep the Desktop Manager from starting with windows and it was already unchecked... damn

I went in msconfig and unchecked everything roxio and it does seem to have made a difference.
 
It looks like that might done the trick. Restarted several times and it's up and going in about 2:15 browser and all. I'm calling that good enough :)

Thanks a lot for all the help everyone. Now I need to create a new post for a different problem. Either my brain is fried or it's Friday, now sure which...
 
run bootvis in the future its a pretty sweet diag tool

Bootvis is just for windows startup. The pause he is talking about occurs after the desktop comes together.

This has happened to me a lot lately and every time it was something else causing it. The symptoms I normally experience is everything works sluggishly and the network does not start for sometimes over 5 minuets. Its almost always after i install SP3 and then run all the updates.

One time is was IE8 causing it, a few times it was not-net 4 client profile causing it, and once I think dot-net 3.5 caused it. The dot-net 4 client profile I don't install anymore and the times IE8 and dot-net 3.5 caused the problem I was able to fix it by uninstalling and reinstalling each.
 
Back
Top