You’ll need to reboot to make it happen.Īfter CHKDSK is done, try making another copy of the file. If this is your system drive (most often C:), the command will not run immediately, but will be scheduled for the next reboot. The “/R” parameter - for “Repair” - directs CHKDSK to check for disk physical and surface errors and repair them as best it can. It’s not as thorough, and it doesn’t perform the same deep analysis and recovery, but it can recover from some types of failures. If surface analysis and repair tools don’t do it, then Window’s own CHKDSK utility is the next thing to try. If your disk is on the verge of failure, the heavy use in analyzing and recovering the data could push it over the edge into a more catastrophic failure.
Running tools like this is not without risk. If SpinRite runs on your machine (sadly, it may not on more and more machines, as it’s not been updated in some time 1) and a bad sector can be recovered, it’s very possible that SpinRite, or other tools like it, will recover it. Tools like SpinRite analyze your hard disk and repair sectors without modifying its contents. If you’re willing to spend money, there’s a possibility we can repair the hard drive. Try to fix the disk: disk surface recovery tools Now that we’ve got a “no worse than” backup copy, we can attempt to repair the disk.
#Command and conquer data error cyclic redundancy check windows
As you’ve already experienced, the default behavior of both COPY and XCOPY, as well as copying a file using Windows File Explorer, is to stop if an error occurs. Two important things to note: we’ve used the xcopy (for eXtended copy) command, and we’ve added the “/c” switch, which keeps copying even if errors are encountered. (Replace my example location with yours, and the “D:” drive with the drive letter assigned to the other drive to which you’re copying the file.) Once again, we want to copy the file to a different disk, and once again, this is best done within Command Prompt.ĬD “C:\Users\lnote\Documents\Outlook Files\” Some data within the file may be lost, but you’ll have copied as much as possible before taking any additional recovery steps. This preserves a copy in a state where “it can’t get any worse than this”. If the problem is in the file itself, we start by making as best a copy of it as we can. If the copy to NUL fails with a CRC error, then we’ve confirmed the bad sector on your hard disk is actually being used by some portion of the file. My recommendation would be to copy it to a different disk entirely - perhaps a USB stick, external drive, or something else. If a copy to NUL works without reporting an error, the problem is likely not with the file itself, but with the location you were trying to copy it to. (Replace my example location or file with yours, of course.) Run Command Prompt, and enter the two commands corresponding to the two steps we listed above:ĬD “C:\Users\lnote\Documents\Outlook Files\” If you’re not sure where a PST file is, Where is my Outlook “PST” file located? has instructions to find it. As an example, my file is at “C:\Users\lnote\Documents\Outlook Files\Outlook. This is helpful because we know the only disk access that will happen is to read the file there’s no attempt to write to the disk.įirst, locate the file. NUL is a special device file name that means “nothing”, so this operation copies the file to “nothing”.