An error occurs while copying, moving, or extracting files

Symptoms

• Error appears during a copy, move, or extraction operation
• May reference a specific file within a larger batch that's causing the failure
• Some files may copy successfully before the error appears
• Error message may mention things like path length, disk space, or a data error

Likely causes

• CommonDestination drive doesn't have enough free spaceThis is one of the most straightforward and common causes of failed copy operations.
• CommonFile or folder path is too long for Windows to handleDeeply nested folders with long names can exceed Windows's traditional path length limits.
• PossibleSource file has corruption or bad sectors ('cyclic redundancy check' error)A CRC error specifically indicates the source data itself can't be read cleanly.
• PossibleDestination drive has a different file system that doesn't support certain file sizes (like FAT32's 4GB file limit)Trying to copy a large file to an incompatible file system fails at that size threshold.
• Less commonAntivirus software interfering with the copy processSome security software can interrupt file operations while scanning.

What to do

1. Check available free space on the destination drive and ensure there's enough room for all the files being copied.
2. If the error mentions a path being too long, try moving the source folder closer to the drive root (like directly under C:\) to shorten the path, or rename folders to be shorter.
3. If you see a 'cyclic redundancy check' error, the source file itself likely has physical damage; try copying just that specific file alone to see if it consistently fails, which points to a failing source drive.
4. Check the destination drive's file system (right-click it in File Explorer, Properties) if copying a very large single file; FAT32 drives can't hold files over 4GB, so reformat to exFAT or NTFS if needed (this erases the drive, so back up its contents first).
5. Temporarily disable antivirus real-time scanning and retry the copy to rule out interference.
6. Try copying the problematic files in smaller batches rather than one huge operation, which can help isolate exactly which file is causing the failure.
7. If a specific source file consistently fails with a CRC or read error, treat the source drive as potentially failing and prioritize backing up what you can before it gets worse.

When to call a pro

If a specific file consistently fails to copy with a CRC-type error, this points to a failing source drive, and a data recovery professional can attempt to retrieve it more thoroughly.

Safety