If a Steam game stops launching or reports a missing installation file, verify its files before downloading the entire game again. Verification is a repair check, not a promise to fix every crash. Start with a closed game, let the check finish, and then reproduce the original problem once.
Sources checked October 3, 2026. Availability, offers and software interfaces can change.
In this guide
- Run the official verification check
- Record the problem before repairing anything
- Interpret the outcome instead of repeating the scan
- Keep installation repairs separate from save recovery
- When to move to a game-specific fix
- What to include in a support request
- Does a successful scan prove the game is fixed?
Run the official verification check
In your Steam Library, open the game’s Properties, choose Installed Files, and select Verify integrity of game files. Valve recommends restarting the computer and Steam first. Allow the process to finish without starting another verification or a disk-intensive task. Some files may fail verification because they are local configuration files that Steam does not replace; that result alone does not establish that the installation is broken. Valve’s verification instructions explain the procedure and that exception.
Record the problem before repairing anything
Write down whether the failure occurs before the menu, while loading a save, or in one specific area. Keep the exact error wording. A repair is much easier to evaluate when you know what previously failed. “The game crashed” is less useful than “the game closed while loading the same save after the menu.”
Also record any recent change: a patch, a mod installation, a moved library, or a driver update. These are investigation leads rather than proof of the cause. Do not delete a save or remove a mod collection simply because either appears in the same timeline.
Interpret the outcome instead of repeating the scan
If Steam repairs files and the original failure disappears, stop there and play normally. Keep a note of the repair in case the symptom returns. If the check completes and the game still fails at exactly the same point, repeating it indefinitely gives you little new evidence.
If the failure changes, record the new behavior separately. Reaching the menu after previously failing at startup is progress, even if a later issue remains. Treating every symptom as one undifferentiated crash can send you back through steps that already worked.
Keep installation repairs separate from save recovery
Before any follow-up that changes personal files, find the developer’s save-location instructions and make a separate backup. A cloud icon is not a reason to assume every file you care about is protected. Avoid broad advice to delete everything inside a game’s folder.
For modded installations, consult the mod manager’s own rollback instructions. Verification and a clean, supported configuration are different questions. Preserve your mod list so you can explain your setup to support instead of trying to reconstruct it from memory.
When to move to a game-specific fix
A repaired installation cannot by itself answer whether your hardware meets the requirements or whether the developer has acknowledged a current issue. Check the official support page for that game and your platform. Prefer the article that matches the error wording over a generic collection of performance tweaks.
For example, a Cyberpunk startup failure calls for a different investigation from an Apex match that runs smoothly but loses network packets. Change only the setting relevant to the symptom you actually observe.
What to include in a support request
Provide the game, operating system, error message, point of failure, and verification result. Explain whether the installation is modified and what changed immediately before the problem. A short sequence of observations is more useful than saying that every internet fix has been tried.
Do not include passwords, recovery codes, or a public screenshot containing account details. Use the developer’s official support channel for any requested diagnostic file.
Does a successful scan prove the game is fixed?
No. The useful final check is launching the game and testing the action that originally failed. Verification answers an installation question; your reproduction test answers whether that particular problem has gone away.
