Slow response from Windows Explorer

[Stephen Quist]

Can anyone point me in the right direction to diagnose and solve a problem
with Windows Explorer?

The situation is this:

The user navigates to a new directory in Explorer and opens a file by
double-clicking on it. This can be any kind of file, Word, Excel, text,
whatever. Explorer sits there for just about 20 seconds displaying the
hourglass and then the file opens. It matters not, if the application, e.g.,
Word, is already open.

If the user opens a second file in this directory, it opens immediately.
If the user opens a file through an application, it opens immediately.
If the user opens a file from a command prompt, it opens immediately.

IOW, Explorer is acting like it's timing out on some process before it
reacts to open the first file in a new directory.
Task Manager show no particular CPU activity during this time.
What is happening? And how can I fix it?
We have a half-dozen computers of the same vintage and OS. Only one is
showing this problem.
The OS is a fully up-to-date XP with SP2.

Thanks,

Steve

 

[John Butler]

Stephen,

My guess is that it is because Explorer is looking for the application with
which to open the file. Once you have opened one file type Explorer will
then instantly open other same type files.
I can reproduce this exactly in my system if folders are set to open in the
same Window.

John

 

[Stephen Quist]

Thanks for the reply.
I don't think that is what is going on. It doesn't matter if the application
is already open or not. I presume that if the app is already open, the OS
doesn't have to go seek it out on the disk again. Also, under other
circumstances, for instance, opening the file directly from a command
prompt, the delay is not encountered. Also, the second and subsequent
files opened in the same directory do not suffer that delay.

Steve

 

[Gary]

Possible:

1. DNS set wrong for the Server/Gateway
2. CD-ROM Drive faulty
3. Floppy Drive faulty
4. Permissions on CD-ROM active and CD-Rom in drive
5. 3rd party extension that insists on controlling Explorer
6. Network card faulty
7. RAM faulty
8. Hard disk on the way out
9. Clear Temp files out
10. Computer is not allowed to browse (see Event Logs for evidence)
11. DNS cache not flushing when rebooting
12. Other process in the way, (overactive AV program)

Cheers

 

[Stephen Quist]

Thanks. 1, 9, 10, and 12 are unlikely causes. I'll have to see
what evidence I can gather for the others.

There's a definite caching aspect to the problem, and the
way it's isolated to Windows Explorer puzzles me.

Steve

 

[Guest]

We are getting this as well. Looking at the task manager, the explorer
process is at 99 percent until the document finally opens.

Any help is appreciated.

 

[Guest]

We are getting this as well. Also, the explorer process is at 99% until the
document finally opens. The problem is identical and should be looked at
closely by MS.
Opening documents is extremely slow when double clicking a file in the
explorer window. It doesn't matter if it is on a network drive or local.
Appears to only be affecting the Windows XP machines.

If you open the application first, it is fine.

 

[Gerry Cornell]

Possibilities?

Csrss.exe uses 100% of the CPU When you Right-Click an item in Explorer
http://support.microsoft.com/default.aspx?scid=kb;en-us;555021

A Program Stops Performing a Task or Explorer.exe Uses 100 Percent of
the CPU When You Right-Click an Item in Windows Explorer
http://support.microsoft.com/default.aspx?scid=kb;en-us;819946


--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~

 

[Guest]

Not either of these. We have the pc's in our domain set to adjust for best
performance, so there it is automatically set to classic windows and no fancy
views.

The problem also occurs on all new pc's and reimaged pc's.

The csrss.exe is not the one either. It's explorer.exe that is using 100%
after double clicking the document.

Thanks for your response though.