Verification checks the installed game files and replaces files the launcher finds incorrect. It can help with corrupted-file symptoms, but is not a guaranteed repair for a quest state or damaged save.
Choose your launcher’s command
| Launcher | Where to start verification |
|---|---|
| Steam | Library → game Properties → Installed Files → Verify integrity of game files. |
| GOG Galaxy | Owned game → Customize beside Play → Manage installation → Verify/Repair. |
| Epic Games Launcher | Library → game’s three-dot menu → Manage → Verify. |
| Battle.net | Game → cog beside Play → Scan and Repair → Begin Scan. |
Prepare a comparison
- Close the game and preserve the original saves outside your test. Note any deliberately modified game files.
- Record the exact symptom and current build. If mods are involved, document their state first.
- Start verification and wait for it to finish; it may download replacement files.
- Launch and repeat the same small test. For a progression problem, compare an available save from before the issue occurred.
What a result tells you
If the symptom disappears, the tested installation now behaves differently. If it remains, a successful verification only tells you the launcher completed its file check. It does not clear every manually deployed mod file or convert a modded save into a clean one.
Choose the next branch by symptom: cannot save locally, missing DLC while loading, or missing trophy after a kill. Avoid reinstalling repeatedly without a reproducible comparison; report the test and result to support instead.
Sources and version limits
- CDPR file verification instructions — Steam, GOG, Epic and Battle.net; checked October 4.
Sources checked October 4, 2026. This is an attributed guide, not a claim that we personally tested your save, hardware or game build.