I've noticed recently that in some circumstances Windows Explorer is maxing out when I'm trying to access flash drives. Typically, I insert a flash drive, open my shared folder (which has full access for everyone), then try copying the data I want from the PC to the flash drive. What happens is that as soon as I plug the flash drive in, CPU usage jumps to 89% or more (depending on what other bits of the system want), and getting anything on / off the flash drive is literally like using an old 486.
My thought on what might be causing it is the WSUS updater program. Since the WSUS folder is also stored in the Shared Documents folder, and the WSUS folder is pretty big, I'm wondering if the reason for the slow-down in flash drive access is due to WSUS somehow messing up Explorer's "concetration" due to heavy access to the shared folder, or something similar. Note that the max-out happens when WSUS is running / downloading updated data at the same time as I try to copy data from a different sub-folder, but in the same shared folder, to a flash drive. What do you think?
I've only just started noticing this annoying problem, which means 1 of 3 things:
1) Its something to do with the new flash drive
2) Its something to do with the shared folder
3) I've not been transferring files from the shared folder to the flash drive at the same time as running WSUS up until now and so its all just coincidental with a certain usage pattern
The flash drive is a brand new 32GB Kingston r500, which is a very fast drive (the whole reason for getting it in the first place). I use my shared folder a lot for storing all manner of programs for the computers I fix / work on - contains about 15GB at the moment. I don't know enough about the vagaries of Vista or shared folders to know what sort of issues can be created by trying to be too clever in terms of storing massive amounts of shared programs in a shared folder. Can anyone shed light on this? Or point me to somewhere on the web that might discuss this intelligently?