How to fix Error 23 on Windows 11

by

Troubleshooting Guide: Error 23 (Data Error – Cyclic Redundancy Check)

Why This Error Happens

Error 23 (Data error: cyclic redundancy check) occurs when Windows detects that data read from a disk sector doesn’t match its stored checksum, indicating physical or logical corruption. This is typically caused by bad sectors on a hard drive/SSD, a failing storage controller, a damaged or scratched optical disc, or corruption in the file system table (MFT). Loose SATA/USB cable connections and outdated storage drivers can also trigger this error intermittently.

Step-by-Step Resolution Guide

  1. Check cable and connection integrity (for external/internal drives)
    Power down the PC, reseat the SATA/power cables (internal) or try a different USB port/cable (external drives). Loose connections often mimic CRC errors.

  2. Run CHKDSK to scan and repair the file system
    Open Command Prompt as Administrator and run:

   chkdsk X: /f /r /x

Replace X: with the affected drive letter. This scans for bad sectors and attempts to recover readable information. Allow it to complete fully, even if it requires a restart.

  1. Use built-in Windows tools to attempt file copy with retry
    For a specific corrupted file, use Robocopy with the /B (backup mode) switch to bypass permission-based read failures:
   robocopy "C:\Source\Folder" "D:\Destination\Folder" /B /R:1 /W:1
  1. Check disk health using SMART data
    Run:
   wmic diskdrive get status

Or use Manage > Storage > Optimize Drives in Windows 11, or third-party tools like CrystalDiskInfo, to check for “Caution” or “Bad” health status indicating impending drive failure.

  1. Update or reinstall storage controller drivers
    Go to Device Manager > Disk Drives / Storage Controllers, right-click the relevant device, select Update driver, and choose Search automatically for drivers. Reboot afterward.

Alternative or Verification Steps

  • Verify the fix: Re-copy or re-open the previously affected file/folder without errors, and re-run chkdsk X: /scan to confirm no new bad sectors are reported.
  • Alternative solution: If CRC errors persist after CHKDSK, the drive may be physically failing — back up all data immediately using a tool like EaseUS Data Recovery or Recuva, then replace the drive.