Cannot Copy or Move Files in Windows 11

Diagnose copy or move failure without risking data

If either drive disconnects, becomes extremely slow, or reports I/O errors during copying, stop repeated transfers and rescue readable data to a known-good drive.

Identify whether the failure depends on the source, destination, one file type, path length, permissions, cloud-sync state, or a specific drive. Test source and destination separately.

Use the exact symptom: “Small files copy but one large file fails” points toward check destination format and free space, while “Only one folder is blocked” suggests inspect permission, ownership and security. Record the full error text, source and destination paths, file-system type, free space and whether the failure affects one item or every item. That evidence prevents an access problem from being mistaken for corruption.

Copy one small test file between two simple local folders, then from the same source to the intended destination. This isolates whether the source, destination, or file itself is the boundary.

“Copy stops with an I/O or CRC error” means you should protect data and test drive, cable and source file, while “File is in use” means you should close the owning app or restart before retrying. Change one layer at a time and verify the original operation. Never accept a utility's “fixed” message without reopening the files and checking that their size and content remain correct.

Check free space, file system, write protection, BitLocker state, and health on both source and destination volumes. A healthy source with a failing destination points the repair to the destination side.

For important files, use copy first and verify the destination before deleting the source. Never rely on a move operation as your only backup path.

If the same copy fails repeatedly, check disk/NTFS events at that timestamp and compare them with the exact path and error. Repeated I/O or reset events matter more than generic Explorer warnings.

Create a controlled copy test

Copy a small non-important file from Documents to another local folder. If it succeeds, Windows copy functionality works and the boundary lies in the original item or destination. Shorten the name and path for testing without destroying the original.

Compare source and destination free space, file systems and permissions. A move within one volume mainly changes directory records; a move across volumes performs copy then delete, so either side can fail.

Handle path, cloud and network boundaries

Very long paths, unsupported characters and reserved names can break older apps even when Explorer supports the location. Rename from the top of the folder tree and test a shorter destination.

Cloud-only files must be downloaded before copying offline, and network shares can disconnect or enforce quotas. Confirm connection and server permissions; do not repeatedly move the only copy across an unstable link.

Protect data during disk and I/O errors

CRC, bad-sector or repeated disconnect errors can indicate damaged media, cable or enclosure. Copy the most important readable files first and avoid running heavy repair before backup.

For large verified transfers, Robocopy can retry and log failures, but incorrect mirror options can delete destination content. Begin with copy-only commands and a disposable test folder.

Verify the repair before making more changes

Restart Windows and confirm that the copied files open correctly at the destination and the originals remain safe until verification. Open several representative files, not only their folder, and compare file sizes or checksums when accuracy matters.

Repeat the copy with a second small file, then with the original file. Confirm the destination copy opens correctly before deleting or moving the source.

Technical order checked against Microsoft's current Windows file recovery guidance. Device-specific menus and driver availability vary by manufacturer.

Related Windows 11 file and storage fixes