Windows Explorer slow response when disconnect from the network

Question

As a Systems Admin I have seen this issue repeatedly and it drives me crazy. Basically the problem occurs when you open My Documents or My Computer (Windows Explorer) there is a big delay ranging from 5-25 seconds before it actually opens and shows the content. Sometimes the problem continues with each subfolder you open. The problem is most common when disconnected from the network and when you have mapped drives.

The most common solution for this problem is to disconnect any mapped drives or printers that are discconected/not reaachable. I have also heard that turning off "Automatically search for network folders and printers" can solve this issue but I have yet to see this work.

Does anyone know of any other work arounds for this?

Solution 1

I found this knowledge base article which supplied a hotfix that corrected the issue. I also found out this fix is included in Windows XP SP3.

This did not solve all cases. I also found out this issue is also often caused by the WIA server. Stopping and disabling it will fix it.

Solution 2

I experience this a lot as well. It has to do with indexing network directories. If you have a network with hundreds of GB of storage, you will see this often. In XP, it's a bug, and I know Vista and 7 work much better with indexing files. I usually kill the dialog box and open it again. Slow, but it almost always works to get the access I need. I don't find the need to actually disconnect the drives as you say. One other thing that I found helps is always having these directories open for faster access and the ability to transfer files independent of apps that need to save/open. Good luck.

Solution 3

I had this problem when one of the document icons or shell extensions was registered on a network drive. Check in the registry under HKEY_CLASSES_ROOT if some of registered DLL files are on a mapped drive or on \\server\share\some.dll.

Also check the solution from this question.

Comments

[Admin]

This still seems to be an issue in Windows 10. Haven't been able to reproduce yet, but this might be caused by having a link to the mapped network drive in the Quick Access menu. Related: answers.microsoft.com/en-us/windows/forum/all/…

[harrymc]

You should have originally said that you were on XP SP2. It would have saved us some trouble.

[user2932003]

Sorry, like I stated in the original questions I have seen this on a lot of computers and did not put together that it was SP2 exclusive.

[Len]

The link is dead. (Yes, this answer is ten years old, but this question is the second result on Google).