From time to time, when I first turn on one of my XP Pro machines and click on Windows Explorer, I get the Windows Explorer Flashlite routine. It obviously is trying to update itself - either for the files on one of it's own drives, or the files on another system connected to my network. I suspect that it's checking on a network system's drive but I'm not sure.

I need some advice on how to kill this irritating procedure. Any help (especially a good explanation) will be greatly appreciated. :huh:

I think it's either one of two things:

#1: The Indexing service. It could be attempting to update the catalog and causing the wait. Try disabling the indexing service and see what happens.

#2: It's checking network shares to make sure they are valid and updating local info as to what those shares are sharing. There is a registry tweak to take care of that, but, off hand, I can't remember it, it's a pretty well known reg tweak. I'm pretty sure someone here knows what I'm talking about, it'll remove the delay when accessing network shares.

Thanks for the reply.

After writing my original plea I disabled the Indexing Service on all three hard drives on the system. This was a puzzle as I thought I had done this following installation on this system. Guess not.

Network shares: I had 2 pointing to another system on the network, so deleted them.

So far everything seems to be correct now.