Steam disk read error: find out whether it is the file or the drive

A disk read error means Steam tried to read a file it needs, for launching, verifying, or updating a game, and the data came back wrong or not at all. One corrupt game file is the benign cause; a drive developing read failures is the serious one. The pattern tells you which: a single game points at its files, every game and other programs too points at the drive.

Fix it, in order

  1. Verify the game's files (right-click, Properties, Installed Files, Verify integrity). Steam replaces files that fail their checksums, which cures the single-game case.
  2. Restart the PC and try again before concluding anything; a one-off read hiccup from a busy or sleeping drive is real.
  3. Check free space on the drive. Nearly full drives behave badly during updates that need scratch room.
  4. Run the drive's error check (Explorer, right-click drive, Properties, Tools, Error checking), and look at the drive's health data if the tool or vendor utility offers it.
  5. Move the game to another drive if you have one (Settings, Storage, select the game, Move). Success there isolates the original drive as the problem.
  6. If read errors spread to other games or programs, back up important data promptly. A drive producing growing read failures is announcing its retirement.

What the checksum is telling you

Steam stores a known-good fingerprint for every game file. A read error during verification means the bytes on disk no longer match, because the file was written badly (interrupted update, crash), overwritten by something else, or the disk surface or flash cells holding it are degrading. Verification fixes the file; only the drive checks answer whether it will keep happening.

Do not ignore a pattern One read error is an annoyance. Read errors that return after verification, multiply across games, or arrive with slow loads and clicking sounds from a mechanical drive are a backup-now signal. Data recovery after a full failure costs far more than a replacement drive.

Common questions

Read error vs write error, what is the difference? A write error means Steam could not save new data, usually locks, permissions, or space. A read error means existing data came back damaged. Read errors deserve more respect, because they can indicate the drive itself is failing.

Verification says all files are fine, but the game still errors. Then the file named in the error may belong to Steam's own download staging rather than the game. Clear the download cache (Settings, Downloads) and retry, and if the named path is on a second drive, test with the game moved.

Related

Steam disk write error · Steam content file locked · Steam missing file privileges · Error 0xc0000005