Open your Steam Library, open the game’s Properties, choose Installed Files, and select Verify integrity of game files. Let Steam finish any repairs before relaunching. If the same error returns, record where it occurs and check storage, mods, and game-specific dependencies before reinstalling.
Decide whether verification fits the symptom
Use verification when a game that previously worked begins failing after a patch, an interrupted download, or a change to its installation folder. It can also help when a game opens but crashes at a specific point where an asset should load. Record the exact error and when it appears. A message about a missing executable suggests a different path from a sign-in error displayed by a third-party launcher. Knowing what happened helps you determine whether a repaired file actually fixed the problem.
Start by closing the game and letting Steam finish any queued download for it. If the computer restarted during an update, check the download screen before starting verification. A patch may still be in progress. If several games on the same disk fail or show read errors, protect important files on that disk first. Our drive health guide explains why repeated storage errors deserve their own diagnosis. Verifying many installations in succession can consume time while leaving the underlying storage problem unresolved.
Protect saves and deliberate modifications
Find out how the game stores saves and settings. Some titles use Steam Cloud, while others use local folders or a separate account. Confirm that any sync you depend on completed and make a copy of important local saves where the game supports it. Open the copied folder and check that it contains the expected files. If you are unsure how to verify a separate copy, use the process in our home backup guide.
If you mod the game, record the mod manager profile and back up any custom files you changed in the install folder. Verification can replace modified files that belong to the game’s official installation. It may leave additional files, so a successful check does not necessarily produce a clean unmodded setup. Read the mod manager’s instructions for temporarily disabling the profile or restoring original files. If you can reproduce the failure with a supported clean configuration, you have a more useful baseline before adding mods back.
Run the Steam verification
In the Steam desktop client, go to Library and select the affected title. Open its Properties, choose Installed Files, and click Verify integrity of game files. Valve documents the procedure in its Steam file verification guide. Leave the client open while it reads the files. A large installation on slow storage can take time even if the internet connection is fast. The process can be disk-intensive before it downloads anything.
When the check finishes, see whether Steam queued replacement files. Allow those downloads and updates to complete before opening the game. Avoid verifying several games at the same time or running another disk-heavy task while trying to diagnose one title. Record the result and compare it with the symptom you started with. If Steam reports that some files failed to verify, Valve notes that certain local configuration files can account for such a message. The practical test is whether the game now behaves normally.
Reproduce the original failure once
Launch the title from the same account and try the step that failed before. If it crashed on opening a save, compare a new game or a different save if doing so is safe. If the problem appeared in a particular level, return to that point. A successful start screen is only an initial check when the failure occurs later. Keep notes about whether the error changed or disappeared.
If a game starts offline but fails when connecting to multiplayer, look at the exact network or account error. File verification may be complete while the server remains unreachable. For lag and disconnections during actual matches, our network latency guide gives ways to separate a local wireless problem from other causes. If the Steam client itself cannot complete downloads, diagnose the network and storage path before assuming each game needs a reinstall.
Investigate files that fail repeatedly
Check free space on the library drive and on the system volume. An update can need temporary working room in addition to the size shown in the library. Use our Storage Sense guide if your Windows drive is nearly full, and review what you remove. If the library is on an external drive, check its connection and whether it remains available throughout a large transfer. An intermittent disconnect can recreate an installation problem shortly after a successful repair.
If a security product flags a particular file, review the notification and seek guidance from the game publisher or your IT provider. Do not disable protection broadly just to make a download succeed. A third-party launcher or runtime can also fail separately from the Steam-managed files. Use the publisher’s supported repair instructions for that component if the error points there. Keep the exact message and verification result so that support can tell which checks you already completed.
Know when to reinstall
A reinstall is worth considering when you have confirmed the drive is healthy, verified backups and tested the game without custom modifications, but the installation still fails. Note which settings and saves live outside the install folder first. Use Steam’s normal uninstall and install controls, then test the clean game before restoring custom files. If it fails in the same place, that result points you back toward a save, an account, a system dependency or a game-specific issue.
If the game works after a repair, keep the notes long enough to spot a recurrence. A one-off patch interruption is different from repeated errors across titles or drives. Repeated repair of the same title can also be caused by a mod that changes an official file whenever you launch it. Reintroduce custom files in small groups and test after each group. That makes it easier to identify a specific change without spending another afternoon reinstalling the whole library.
For example, suppose a game crashes every time you open the same older save, while a new campaign starts normally. Keep a copy of the older save, run verification, and try it again before changing any graphics settings. If the crash still affects only that save, check the game’s known issues and whether the save depends on downloadable content or a mod that is no longer enabled. This result is more specific than simply reporting that the game crashes. It also gives support a reproducible test and protects your progress while you investigate.
Frequently asked questions
Does verification reinstall the whole game?
Steam checks the installation and downloads needed replacements. How long this takes depends on the game and storage.
Will verification remove every mod?
It can replace modified official files and leave extra files. Use the mod manager’s instructions to establish a clean configuration.
Why does verification succeed but the game still crash?
Check the exact error, game dependencies, saves, mods, and storage. Verification only addresses the files Steam checks.
