A checksum error means the data you downloaded, copied, or verified does not match the value it was supposed to produce, so your system flags it as corrupted or altered. You will see it when a downloaded ISO fails a hash check, a transfer aborts partway through, or a tool like certutil reports a mismatch. Here is what triggers a checksum error and the fixes that actually clear it, from re-downloading the file to checking your drive for bad sectors.

What Is a Checksum, and Why Does It Fail?

A checksum is a short string generated by running data through an algorithm such as MD5, SHA-256, or CRC32. Two matching checksums confirm the file arrived exactly as sent. Any difference means something changed along the way, whether that is corruption, a dropped packet, or a file someone altered after the original hash was published.

What Causes a Checksum Error?

Most checksum errors trace back to one of four things: an interrupted or incomplete download, a failing hard drive or SSD, faulty RAM that corrupts data mid-transfer, or a network connection dropping packets during a large file transfer. Software vendors also publish checksums specifically so a mismatch flags tampering, which is why security teams check the hash on an installer before running it.

How to Verify a File’s Checksum Yourself

On Windows, open Command Prompt and run certutil -hashfile filename.iso SHA256, then compare the output to the hash listed on the download page. On Mac or Linux, run shasum -a 256 filename.iso for the same result. If the two strings do not match exactly, the file failed verification and should not be installed.

Fixing a Checksum Error During a Download

Delete the partial file and download it again, ideally over a wired connection instead of Wi-Fi, since a wireless drop mid-transfer is a common cause of a bad checksum. If the error repeats from the same source, try a different mirror or server, since packet loss on the sending end produces the same result. The same network instability shows up when Chrome throws an ERR_SSL_PROTOCOL_ERROR mid-connection, so ruling out your network first saves time before you blame the file itself.

Fixing a Checksum Error on a Local File or Drive

If a file already sitting on your drive keeps failing verification even after a fresh copy, the drive itself may be the problem. Run CHKDSK with the /f /r flags to scan for bad sectors, the same repair that clears up a related CRC error caused by a damaged disk. Isolating whether the fault sits in the network, the drive, or the file follows the same order you would use to troubleshoot a phone screen that stops responding to touch: rule out the easy fix first, then move to hardware.

Checksum Error vs CRC Error: What Is the Difference?

CRC, or cyclic redundancy check, is one specific checksum algorithm built directly into file systems and disk drives, so it fires automatically the moment you copy or open a file. A general checksum error, using MD5 or SHA, usually needs you to run the check by hand against a hash the publisher listed for that download. Both report the same underlying issue: the data changed since it was created.

What does a checksum error mean?

It means the computed hash of a file does not match its expected value, so the data changed somewhere between the source and your device. The cause can be corruption, a dropped connection, or a file someone altered after the hash was published.

Can a checksum error be fixed?

Usually, yes. Re-downloading the file over a stable connection, switching to a wired network, or running CHKDSK on a failing drive resolves most cases without any data loss.

Is a checksum error a sign of a virus?

Not directly. It flags data corruption rather than malware, though a checksum mismatch is exactly how tampered installers get caught before anyone runs them.