Explorer.exe stops responding after SIMPLE cut/paste operations ..

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

What is this nonsense.

I've experienced this problem since using XP, only now I am actually
bothering to comment on it, after who knows how many Windows Updates and two
service packs they haven't addressed this problem.

In short. During explorer operations like cutting a bunch of files from a
folder then selecting back-up the folder tree explorer.exe will goto 99% CPU
utilization, making the system unusable meaning restarting the process in
Task Manager.

Other Explorer operation variations cause this too, like deleting a bunch of
files and going back up the folder tree.

Why is this? It is NOT system dependant as I've experienced it over several.
Can Microsoft not code basic things like this correctly?
 
Can anybody tell me how I can escalate this problem with Microsoft?

Just now I was copying a large group of directories and files to another
hard disk and explorer.exe ended up at 99% cpu utilisation after a short
while forcing me to close the process.

Upon restarting explorer.exe and running a SFV check on the ORIGINAL file
used in the copying process that has somehow been altered and fails.

How can Microsoft completely overlook this fundamental flaw?
 
How many is a large group. I ask because large is a releative figure. I have
seen reports of people having problems copying or moving 1000s or 10,000s
but for 10s or 100s there are no problems that I know of with XP. How many
times did you try and copy the files.
 
Back
Top