Long delay at startup after time in storage.

[Guest]

My laptop was in storage for a few months; now, when Windows boots, it freezes for ~60 seconds after loading the Taskbar (but not the desktop icons). I can open the start menu and a few programs during this time, but Windows doesn't seem to be doing anything (no hard drive access noises). This didn't happen before, and I haven't made any sort of change that could account for it. I've already tried ScanDisk, defragging, running a virus scan, checking for spyware, and disabling things through msconfig.

My specs:
Dell Inspiron 8000
P3-900
256MB RAM
20GB 4200RPM HD
WinXP SP1

 

[WinGuy]

My laptop was in storage for a few months; now, when Windows boots, it

freezes for ~60 seconds after loading the Taskbar (but not the desktop
icons). I can open the start menu and a few programs during this time, but
Windows doesn't seem to be doing anything (no hard drive access noises).
This didn't happen before, and I haven't made any sort of change that could
account for it. I've already tried ScanDisk, defragging, running a virus
scan, checking for spyware, and disabling things through msconfig.

My specs:
Dell Inspiron 8000
P3-900
256MB RAM
20GB 4200RPM HD
WinXP SP1

Right-click the taskbar and select the Task Manager, click the Processes tab
and see what is using up all the CPU time during that delay period. If you
don't see the Processes tab then double-click the border that goes around
the Task Manager.

It might be trying to do network stuff and eventually times out without
getting an IP address for the machine. Did you have DSL before it went into
storage? If so, remove the associated programs in Add/Remove Programs if you
don't still use it.

 

[WinGuy]

Task Manager shows 99% system idle processes, 1% taskmgr.exe. Other

processes running are: ccApp.exe, ccRegVfy.exe, Traybar.exe [a utility I
installed well after this started happening], SynTPEnh.exe [touchpad
software], SynTPLpr.exe, DadApp.exe [Dell Access Direct], PROMON.exe,
CCEVTMGR.EXE, LEXPPS.EXE, CTFMON.EXE, EXPLORER.EXE, SVCHOST.EXE [x4, one
Local Service, one Network Service, two System], LSASS.EXE, SERVICES.exe,
WINLOGON.EXE, CSRSS.EXE, SMSS.EXE, System.

I was on a university LAN previously, and had the same problem there, but I tried
disabling "1394 Connection" and "Local Area Connection" under Network

Connections, to no effect; also, I've never had ISP software installed.

This actually happened once before when I went without using the laptop

for an extended period, but it went away after a week or two. This time it
has been going on for over two months.

I think the 1394 connection is really your firewire connector (don't even
ask, MS does strange things) and you can leave that enabled.

The only thing that stands out without in depth investigation is that I see
LEXPPS.EXE, try temporarily disabling Lexmark startup stuff via msconfig.
Lexmark likes to go look around the network, maybe that could be associated
with the problem. Got anything for Lexmark running as a service? I once had
a slow startup problem with a Z42 under 98. Really, turning the computer off
& putting it in storage should not cause a problem, with the exception of if
the timeclock/cmos battery needs changing and your clock is now set for the
wrong year -- I've seen that give some glitches, too. If your clock is at
the wrong year then your cmos was probably reset back to its default
settings (which is probably but not guaranteed to be ok).

Other than that, I'm at a loss now. I guess I'd then use msconfig & turn
everything off & test them being turned back on one at a time ... this
really sounds like some sort of network related issue but I don't suspect a
defective hardware reason unless Event Viewer is complaining about
something.

 

[WinGuy]

I tried disabling the Lexmark service to no effect, and the computer seems

to be keeping the date/time fine, but I did notice one error in Event Viewer
that re-occurs at every startup:

Failure Audit [Date/Time] Source: Security Category: Policy Change Event: 615
User: NETWORK SERVICES

Description: IPSec Services: IPSec Services failed to get the complete

list of network interfaces on the machine. This can be a potential security
hazard to the machine since some of the network interfaces may not get the
protection as desired by the applied IPSec filters. Please run IPSec monitor
snap-in to further diagnose the problem.

Also, thanks for the help thus far.

Well, that explains the long delay problem.

Set a restore point. then try:
http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip
and if necessary:
http://www.majorgeeks.com/download4180.html

Does that help?

 

[Guest]

Well, that explains the long delay problem.

Set a restore point. then try:
http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip
and if necessary:
http://www.majorgeeks.com/download4180.html

Does that help?

No, it didn't, actually.

 

[WinGuy]

No, it didn't, actually.

Sorry for the delay, got super busy. Since you have a restore point, remove
all existing network connections (right click My Network Places or its
equivalent, right click each and select properties, uninstall each, one at a
time, & test to see if that fixes it. If so, restore system & delete the bad
one, make a new conenction for what you deleted if you want it. Does that
do it?

 

[Guest]

Sorry for the delay, got super busy. Since you have a restore point, remove
all existing network connections (right click My Network Places or its
equivalent, right click each and select properties, uninstall each, one at a
time, & test to see if that fixes it. If so, restore system & delete the bad
one, make a new conenction for what you deleted if you want it. Does that
do it?

I tried uninstalling Local Area Connection, but it apparently re-installed itself during the reboot. Other than that, all I have is the FireWire connection and a few dial-up numbers.

I've actually tried running a utility (Microsoft Bootvis) which is showing that the delay is actually about 105 seconds long, and occuring in the Login & Services phase of startup; I've also found that disabling System Services in MSConfig stops the delay.

 

[WinGuy]

I tried uninstalling Local Area Connection, but it apparently re-installed

itself during the reboot. Other than that, all I have is the FireWire
connection and a few dial-up numbers.

A restoration should put them back into working order. Be sure to set one.
Until you eliminate all network connections then you can not rule them out.
Even the firewire one). At least select to disable them for dignostic
purposes.

You might try, from a cmd prompt (Start | Run | cmd | OK):
sfc /purgecache
sfc /scannow (you might need a CD of the very same and exact OS type when
you use this command)
sfc /purgecache
exit

And THEN remove all connections so they can be rebuilt on next boot (but
this time not from potentially defective driver copies from cache).

I've actually tried running a utility (Microsoft Bootvis) which is showing

that the delay is actually about 105 seconds long, and occuring in the Login
& Services phase of startup; I've also found that disabling System Services
in MSConfig stops the delay.

Sure, that makes sense - you already know it's a networking issue and most
of that is services related.

 

[Guest]

itself during the reboot. Other than that, all I have is the FireWire
connection and a few dial-up numbers.

A restoration should put them back into working order. Be sure to set one.
Until you eliminate all network connections then you can not rule them out.
Even the firewire one). At least select to disable them for dignostic
purposes.

You might try, from a cmd prompt (Start | Run | cmd | OK):
sfc /purgecache
sfc /scannow (you might need a CD of the very same and exact OS type when
you use this command)
sfc /purgecache
exit

And THEN remove all connections so they can be rebuilt on next boot (but
this time not from potentially defective driver copies from cache).

that the delay is actually about 105 seconds long, and occuring in the Login
& Services phase of startup; I've also found that disabling System Services
in MSConfig stops the delay.

Sure, that makes sense - you already know it's a networking issue and most
of that is services related.

Turns out it was Norton AV causing the problem, as I discovered today after downloading a rather over-due patch. Thanks again for your help, though!