Q: Can't Copy a File (CRC Error) This thread is locked from future replies


I have a 0.99GB file on my Desktop that I'm unable to copy or move to other disk. I'm able to move it to other locations on the same disk (as far as I know this edits the records and not the file itself?).

In Windows 7 I get the following error message: "Can't read from the source file or disk.". When using CMD.exe, I get the following: "Data error (cyclic redundancy check). 0 file(s) copied."

I've read that this could be a hardware issue, but only if I was unable to read the file. I was able to copy the file with NUL as the destination.

The file is a movie of type .VOB and I can play it with no problem. I downloaded it from a Virtual Machine using FTP. The Created, Modified and Accessed metadata won't change when I play the movie (Accessed should change?). Even if it is corrupted, it plays fine.

How can I resolve this issue?

I've tried running chkdsk to no avail. It's a 1TB Samsung disk with NTFS.

Summary: I want to copy a file and bypass Windows 7's CRC check or resolve the error.

Thanks in advance for any assistance!

Hi Cybesystem,


Cyclic redundancy check errors normally occur with damaged or faulty discs.


I’d recommend you run a check disk on the drive using the “chkdsk /f” command from an elevated command prompt and see if that fixes any errors on the drive.


Refer the following article for instructions:




Note: If any bad sectors are found while running the check disk utility and if attempt recovery of bad sectors option is checked while checking the drive for errors, data in the bad sector may be lost while attempting to recover bad sectors.


Additionally, I’d recommend you run a diagnostic tool downloaded from the hard disk manufacturer’s website and check the disk for errors. Contact Samsung support for further assistance.

Did this solve your problem?

Sorry this didn't help.

Thanks for the help Gokul T. I've already run chkdsk to no avail, and it reported no errors.

I'm able to run "copy [file] NUL", doesn't this mean it's possible to read the file? I can't copy to the same or another disk (if that matters).

I will in the mean time find the diagnostic tools, but since it is a new hard drive and everything else checks out - I think it's Windows. But nevertheless I have to follow up every possibility.

Did this solve your problem?

Sorry this didn't help.

From prior experience, I know that target of NUL is a special case and doesn't mean file can be read.

Did this solve your problem?

Sorry this didn't help.

2 people were helped by this reply

use copy.exe or xcopy.exe from cmd.exe shell.

there may be a nice safe copy to use.

[windows-logo-flag-key]-R cmd [Enter]

cd %windir%

dir /s/od copy.exe

now look at the dates (the bottom one), and see which is latest, and xcopy that file over the old one in %windir%\system32\

click the cmd shell icon in upper left hand corner of window, properties, turn on quickedit, layout tab, 150,9999, 150,50, OK.

xcopy "C:\Windows\winsxs\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.22923_none_a58390d5e3053be4\copy.exe" %windir%\system32\copy.exe

ahh, never mind, it's cmd.exe whihc is bad. copy is a built-in command to cmd.exe sorry. so you need to re-copy  cmd.exe

[windows-logo-flag-key]-F kind:=program name:cmd.exe [Enter]

make sure no cmd shells are hrunning, otherwise they will lock cmd.exe from being copied over.

right click the latest version that is not in c:\windows\system32\ and right click on the one in  c:\windows\system32\ and paste it and replace.

Did this solve your problem?

Sorry this didn't help.

Question Info

Views: 4,037 Last updated: February 27, 2018 Applies to: