G
Guest
I am experiencing a problem that I’m hoping someone, preferably a Microsoft
representative, can help me with.
Where: In WindowsXP Home Edition, WinXP SP2, Windows 2000, and possibly others
What: Windows Explorer Stops Responding after File Move/Copy
Symptom: Any time you copy or move a folder containing any number of files,
Windows Explorer stops responding and consumes 100% of the CPU bandwidth.
The only solution is to log off (Ctrl+Alt+Del) or reboot. The only
permanent solution is to completely reinstall the operating system.
Possible Cause: This persistent problem seems to be triggered after a
move/copy operation involving many hundreds of files. Once the problem
starts, the problem manifests itself after any file move/copy operation, not
just a large one. My theory is that the database or file that explorer.exe
uses to move or copy files on the hard drive somehow becomes corrupted in
some minor way causing Windows Explorer to get stuck in an endless loop.
Note it does not seem to occur after a COM XCOPY or MOVE operation, only a
Windows-based one (drag & drop).
I have seen this on a variety of machines and operating systems; the common
thread seems to be Internet Explorer 6. These machines have all been in
development environments where it is common to perform high-quantity file
move/copy operations.
Given that I have seen the problem on a variety of machines and hardware
combinations, I have a feeling others have seen this problem. I’ve searched
Microsoft’s knowledge base for an answer but haven’t come up with anything.
Any help would be most appreciated.
Cheers,
Steve
http://www.stringersites.com
representative, can help me with.
Where: In WindowsXP Home Edition, WinXP SP2, Windows 2000, and possibly others
What: Windows Explorer Stops Responding after File Move/Copy
Symptom: Any time you copy or move a folder containing any number of files,
Windows Explorer stops responding and consumes 100% of the CPU bandwidth.
The only solution is to log off (Ctrl+Alt+Del) or reboot. The only
permanent solution is to completely reinstall the operating system.
Possible Cause: This persistent problem seems to be triggered after a
move/copy operation involving many hundreds of files. Once the problem
starts, the problem manifests itself after any file move/copy operation, not
just a large one. My theory is that the database or file that explorer.exe
uses to move or copy files on the hard drive somehow becomes corrupted in
some minor way causing Windows Explorer to get stuck in an endless loop.
Note it does not seem to occur after a COM XCOPY or MOVE operation, only a
Windows-based one (drag & drop).
I have seen this on a variety of machines and operating systems; the common
thread seems to be Internet Explorer 6. These machines have all been in
development environments where it is common to perform high-quantity file
move/copy operations.
Given that I have seen the problem on a variety of machines and hardware
combinations, I have a feeling others have seen this problem. I’ve searched
Microsoft’s knowledge base for an answer but haven’t come up with anything.
Any help would be most appreciated.
Cheers,
Steve
http://www.stringersites.com