http://forums.microsoft.com/technet/showpost.aspx?postid=1714300&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=20 Try adding the following registry key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System\CopyFileBufferedSynchronously REG_DWORD 1 I did receive this from MS tech support, and it solved the problems on all systems I tested, but please note that I have no idea whether it adversely affects data integrity or anything else. Tried "CopyFileBufferedSynchronously"; rebooted - no difference. I have a few observations in common with others on this forum: The problem exists when am copying/moving across a network (mapped drives, unc paths). Between disks (ISE, SATA, eSATA) or within the same volume transfer speeds are "better" (possibly due to applying the two MS patches?) but the initial hesitancy remains. The Vista boxes and W2K3 server have the relevant patches installed. The MS patches make reference to file transfers to systems other than Vista. I experience the same issue between two Vista machines. A typical scenario would be to copy an exe program using the Explorer UI from a Win 2003 network drive and involves these steps: Open up network (S drive (400+ directories, few files) [almost instant] Open up source folder (contains Blackberry software: 12 files, some compressed, ranging between 0.5MB an 240MB) [40 seconds; lots of "Not Responding and frozen screens] Persevere, eventually starts working (note: don't now try to right-click anything unless you want another 40 second wait) Click target file (besx_4.1.3.exe; 240MB) and drag to local desktop [40 seconds of inactivity] "Calculating Time Remaining..." dialog box finally appears. Transfer starts at <1MB/sec and completes at 9.03 MB/sec (the average?) Including the delays this is a transfer at 2.25 MB/sec! These times are almost identical on all Vista boxes This is a quiet gigabit network. Even at 50% throughput transfers should work at 60 MB/sec (or up to the hdd's limit) - they do for XP. Using a command prompt takes 45 seconds (5.3MB/sec) Transferring the file from the W2K3 box to the Vista desktop takes 25 seconds (9.9MB/sec) This is not much more than an annoyance for me but I have now had a real-world situation where specifying multiple Vista machines was out of the question: A film and TV composer who runs various audio applications across multiple workstations needs to replace most of his machines. Different banks of sounds are located on different devices on the network and loaded on-the-fly when needed. Some of these banks are >1GB. This works well on his XP gigabit network but I cannot see how it would work in a Vista environment. All the applications are Vista-certified - it's just Vista itself that isn't up to the job.