Slow taskbar/system tray startup

[flylice31]

Hi I have been experiencing a strange slow startup on my Windows XP. On regular startup, it takes about 2-3 minutes after windows loads, for the taskbar to be active. In other words, in those 2-3 minutes I can't click on the taskbar whatsoever which is very strange. I have narrowed it down to if I disable my wireless network connection, it starts up FINE! However when I enable it again it temporarily locks up the taskbar at startup. I was wondering if anybody has found a solution to this? I have looked through hundreds of posts and have had no success. (i.e. uninstall mcafee, spyware scan, virus scan) Any help would be appreciated. Thank you very much for your help!

 

[Peddant]

Two ideas from - HERE

1.Modify the windows service: "Wireless Zero
Configuration" startup type setting to AUTOMATIC.

2."I had the problem on our Dell laptops w/ integrated intel wireless nics.
The solution was to set the intel software to control the wireless
connection...not let windoze do it. (uncheck "use windows to configure
my wireless network settings" from the properties of the wireless
connection>>"wireless networks"). wonder if that is in effect, the
same as adjusting the settings of the service. (?).

also found that this was mainly an issue in our office, where there is
no wireless access point (yet). when I brought a laptop home and tried
it on my home wireless, it booted right up, with hardly any delay.
there is about a 10 second delay with windows managing the connection,
but thats way better than 1-2 minutes. seems to me that its searching
for a connection, and won't give up till it finds one, or the user
falls asleep. even windows can find one at my house in a timely manner."

 

[almanach]

solved

thank you for your advise.
I found a way even more simple to solve the problem.
on my wireless network connection >> properties >> wireless network
I let the windows continue managing my wireless networks, but I removed from the list of preferred networks all of the networks I had. guess windows was trying to connect to each one of them before it continued.