Copying files

Will there ever come a day when Windows Explorer, when it encounters an error during a file copy (due to a sharing violation, for example), actually gives you the option of skipping the problem file and continuing on with the copy? As opposed to the current behavior, where it just bombs out and stops copying.

Dare to dream.

13 Comments

  • Or maybe let you roll back the copy operation? Now I know I'm asking for too much.

  • Good god, man, that's crazy talk.



    ;)



    I wonder how many extra terabytes of information I've copied over the years because I had to duplicate a massive copy after one stupid file failed.

  • Dear god! Who still uses Explorer for copying? Lots of very good tools out there (Total Commander being one of the most powerful file managers out there) just begging for your attention.

  • Ahh Kevin - your dreams are too brave and powerful. Such a time may never in your lifetime come to pass.

  • Roy,

    Something as simple as reliably copying files should hardly require a third-party tool. After all, dealing with files is one of the most basic functions of an operating system.



    There was a time when I used third-party file management tools (back in DOS and Win3x days), but I would hope we've graduated beyond that - at least for most typical uses.

  • Longhorn gives you the option to skip.



    Rolling back the copy operation is insane. What if the rollback fails? What if you said "Yes" to overwrite an existing file. How do you roll that back? Do you attempt to resurrect the original file?

  • Woo hoo! The dream lives! Thanks Raymond. I haven't dipped my toes into the Longhorn waters yet.

  • So then the next question is - if you do skip, will it give you a summary of the files that failed when the copy completes? That would be sweet.

  • Friendly file operations don't sell OSes, animated start menus do.



    There should be several options when there is an issue :

    Retry - So I can close the app that has locked the file.

    No overwite - Just copy the files that are not already there.



    There are lots of things like this. When I delete a file it is just going to the recycle bin, why force me to confirm? I don't feel the same about shift-delete, because it actualy deletes the file.





    Rollback, just thinking about makes me want to write a tool that will enable it.



    No Mr. Chen , I do not want it to attempt to resurect the original file, I want it to restore the original file. If your rollback fails, your problems are probably much more serious than a few files.



    If there are files that will be overwitten, there should be an option to have them be saved/copied to some temporary location for the duration of the operation.









  • OK, restoring the original file is a bit crazy ... I mean, especially when you start condidering this function across a network. She skipped failed file thing would be great.

  • "Longhorn gives you the option to skip."



    Correction: Longhorn WILL give you the option to skip.

  • ...only for local files.

  • Ack, really? Locally only? Lame.

Comments have been disabled for this content.