OK -- for the love of [insert diety here]:File copy behavior in ALL OS's (including OS X)is STUPID. Please fix this. Here's what I suggest:When copying a large number of files (not an uncommon occurance when upgrading HD's, or OS's), if there is an error (HD error -- one major reason for upgrading HD's, or duplicate file), the copy process HALTS and waits for your input. Worse, if it's a file system error, it aborts the copy!This is especially galling because I don't sit and watch the copy when I am copying 10's of gigabyts or more -- I go do something else and come back in an hour or so to resume. How maddening when I see a "Duplicate file" error, and realize the whole process stalled because of one file!Maybe there is some reason for this, but it escapes me. Why not have the copy continue in the background? Further, when copying entire folder hierarchies, if a copy stops or fails, there's no way to know where the file was (especially if deeply nested) without a search. Why not log the errors to a text file -- or XML -- and let the user review the errors at the end of the copy? So when I come back after an hour, I haven't wasted time, I can either click "copy" or skip for duplicates and complete the process, or stop the process and review the XML file at my leisure. The XML file should be broken into sections for each type of error -- duplicate, file system, file locked, etc. This lets me start a large file copy, assured that it will complete with a) only the error-causing files skipped and b) that I can easily start a new copy process that copies only the skipped files. In fact, I should be able to simply right-click the XML file and chose resume copy/move after I have remedied any errors, or chosen to overwrite duplicates. Further, since I may not be able to remedy file system errors, I should have an option to copy, skipping over file system errors.

Do what I do. Use a command prompt and xcopy.You can enter xcopy /? to get the usage.There are a lot of options now, my favorite being /C"Continues copying even if errors occur".

That's odd. In both Vista and Win7, they seem to wait until the very end to ask you if you want to copy or move those stupid thumb.db files and other so-called system files or read-only files. I was happy to find they at least did that.

Something has to change wiff windows 7 auto copy of files folders herez why. I had a self inflicted windows error that needed a restart. I now have a extra windows folder here. Idelete the folder, I have to enable special permissions to do that. I am now stuck with windows.old,windows.old.000. We need to change this in windows 7

Colakid:When Windows setup is told to install to a partition with an existing Windows installation, it moves the system specific files to windows.old, ...000, etc.I think the only way to avoid this is if you can launch setup from within your existing Windows.The recommended alternative is to use the File and Settings Transfer Wizard.

Yes I knew that I had the windows.old from that, but the second one was from a windows error. I only setup windows 7 once after the first setup, my drive was formatted before the setup. Also another thing I noticed in Group policy Editor there are double even triples of the same policy.Look Here. I'm looking for a policy to change the way windows notifies copying files.Administrative Templates All Settings.

Hi Kurt, Thank you for your feedback. I will forward it to our feedback team. In addition, we have a Feedback thread available where you can post product suggestions and any other feedback. The Forum Owner will periodically collect these messages and send them directly to the Windows 7 Product Development Teams. Here is a link to that thread for your convenience. Have Comments about Windows 7 Beta? Thanks.

I completely agree with you Kurt. I've had the same experience as you when copying large files and making the copying work in the background instead of halting the process would be a great feature/change for Windows 7.+1 for this recommendation, hopefully it gets implemented!

At least in XP it gives you the option to replace all files one time. For backups I copy whole folders to a backup location on a different hard drive. There is no way I can sit there and click replace file for each file and folder as required by Win7. Windows 7 needs an option for replace all just like XP. I suppose a work around would be to delete the backup folders first and then do a copy but that is also a pain . This is a major issue and needs to be addressed. I do not understand why this feature was not implemented in the first place.