If a Steam Deck game is marked Verified but will not launch, start with the least destructive explanation: an outdated SteamOS build, a pending restart, a Desktop Mode utility, a changed Proton runtime, damaged game files, or a library-storage problem. Install SteamOS updates, restart the Deck, and disable third-party Desktop Mode applications before changing compatibility settings. If that does not help, test Proton deliberately, verify the installation, clear Steam’s download cache, and only then repair or move the game library. A Verified badge describes Valve’s compatibility baseline; it is not a guarantee that every later game update, Proton build, launcher state, or storage state will behave identically.
Why can a Verified game stop launching?
Verified means the title passed Valve’s Steam Deck compatibility checks for the criteria Valve uses. It does not freeze the game, SteamOS, Proton, or the local installation at the moment of certification. Valve says its compatibility review is ongoing and that new game updates are published every day, while its Steamworks documentation describes Proton as a work in progress.
“The game works great on Steam Deck, right out of the box.” — Valve’s Steam Deck compatibility description
That statement describes the expected starting experience, not a permanent guarantee after every game patch or SteamOS change. A title can therefore be Verified and still show “Preparing to Launch,” return immediately to the library, crash silently, or stop working after an update. Treat the badge as a useful baseline, then investigate the current software and installation state.
“Proton is a work in progress, and it’s possible that your game may not yet be fully supported.” — Valve’s Steamworks compatibility documentation
What should I check before changing game settings?
Record what actually happens and make the simplest software checks first. This prevents you from changing several variables at once and losing the clue that identifies the cause.
- Note the exact symptom: an instant return to the library, “Preparing to Launch” followed by a stop, a visible error, or a silent crash.
- Check whether other games launch. A single failing title points toward that game’s files, runtime, launcher, or developer support; widespread failures point toward SteamOS, Steam, or storage.
- Install every SteamOS update that is offered before testing compatibility settings.
- Close or disable third-party applications installed through Desktop Mode. These can alter the environment Steam games use.
- If you have changed Proton or launch settings already, write down the current choice so you can return to it.
Also check practical conditions that can mimic a software fault. Make sure the Deck is not still applying a game update, has enough free space for that update, and is connected if the game’s launcher requires an online sign-in. Do not infer a hardware failure from one failed title while the rest of the library works.
What is the safest fix order for a Verified game that will not launch?
Follow these steps in order. Each one targets a different layer, from the operating system to the game files and finally the storage device. Launch the game after each completed step so the result remains useful diagnostically.
1. Update SteamOS, restart the Deck, and disable Desktop Mode utilities
On the Deck, open Steam > Settings > System > Software Updates and install all available updates. When the installation finishes, choose Steam > Power > Restart; do not merely close the game and reopen it. After the restart, test the title with third-party Desktop Mode applications disabled or exited.
This first pass is reversible, does not remove installed games, and can resolve a mismatch between the current Steam client, SteamOS components, and the game’s launch environment. If the title still fails, continue rather than repeatedly restarting.
2. Re-check the game’s current compatibility details
Open the game’s Steam library or Store page and view its compatibility details. Confirm that the title is still identified as Verified and read any notes attached to that status. Valve’s review process continues over time, so a game’s compatibility context can change as developers publish updates or Valve revises its checks.
This check does not mean the badge is meaningless. It explains why a title that launched previously may need troubleshooting now: the game build, Proton build, launcher, or local files may no longer match the state that worked before.
3. Force Proton deliberately, one version at a time
For a game that still refuses to start, open its menu and choose Properties > Compatibility. Enable Force the use of a specific Steam Play compatibility tool, then select the latest Proton version available on the Deck. Close the Properties window and launch the game.
If the latest version does not help, return to the same menu and test another installed Proton version. Change only one version at a time and keep a note of the result. If one version launches and another does not, that comparison is useful information for a later support request; it is not proof that the working version will remain the best choice after a future game or SteamOS update.
Forcing Proton is not a universal fix. If the game has a native Linux build, this setting can cause Steam to download and run the Windows version instead, changing the runtime you are testing. If the title worked natively before, compare the forced-Proton result with the default compatibility setting rather than assuming Proton is automatically superior.
Do not switch several Proton builds in rapid succession or add unverified launch options at the same time. A controlled comparison—default setting, then one selected version—tells you more and makes it easier to restore the known configuration.
4. Verify the local game files
From the game’s Properties window, open Installed Files and select Verify integrity of game files. Wait for the process to finish completely, then launch the game again.
Verification checks the installed game content and replaces files Steam identifies as missing or damaged. Steam may report that one or more files failed verification because some files are local configuration data; that message alone does not prove that the entire installation is unusable. Let the operation complete, then retest before taking a more destructive step such as reinstalling.
Verification is scoped to the selected game. It is not the same as clearing Steam’s download cache, and it does not repair a broader SteamOS problem. Keep any cloud-save or local-save concerns in mind before deleting folders manually; use Steam’s supported verification operation first.
5. Clear Steam’s download cache
If file verification does not change the behavior, open Steam > Settings > Downloads > Clear Download Cache. Steam’s cache-clearing operation refreshes locally cached download data; it is different from file verification, which checks the game installation itself.
Clearing the cache does not remove installed games. Steam will require you to sign in again afterward, so have your account credentials available. Once Steam has restarted and you are signed in, launch the affected title before changing another setting.
Use this step when Steam’s download or update state may be stale. It should not be presented as a replacement for verifying files: one refreshes cached download data, while the other compares the installed game content with Steam’s expected files.
6. Repair the library or test another storage location
If the problem persists, inspect the library that contains the game using Steam’s Storage controls. Where Steam offers it, use the option to repair that library folder. A repair can address permissions or library-management problems without immediately deleting the game.
If the Deck has another usable library location, move the game there or reinstall it there as a diagnostic test. A title that launches from one location but not another points toward the original library, failed downloads, or storage corruption rather than a general Verified-status problem.
An optional microSD card can serve as an alternate library location for this test, but it is not a general launch fix. The relevant question is whether the game behaves differently on a known-good library path, not which brand, capacity, or speed class you buy. Moving or reinstalling also requires enough free space and can take substantially longer than a file check.
7. Decide whether the failure is game-specific or system-wide
Launch several other games after the software checks. If they work normally, keep the investigation focused on the affected title’s files, Proton behavior, bundled launcher, or developer support. Avoid resetting the whole Deck for a problem isolated to one game.
If multiple games fail, Steam itself is unstable, or SteamOS shows other errors, repeat the test with third-party Desktop Mode applications disabled. The SteamOS Beta can be considered as an escalation for broad system problems, but it is not the default response to one Verified title that will not start.
8. Escalate with a precise report
When the ordered checks do not resolve the issue, use the game’s Steam Support link to contact its developer and contact Steam Support when the problem appears to involve Steam or SteamOS. Give support information that narrows the fault instead of simply saying that the game is Verified.
- Describe the exact behavior: “Preparing to Launch” then stop, instant return to the library, a silent crash, or the text of any error.
- State whether other games launch normally.
- List the Proton version tested, including whether the default setting was also tried.
- Identify the library location used and whether the game was tested on another available location.
- Say whether the failure began after a game update, SteamOS update, or other change you noticed.
Do not assume that a particular launch option, compatibility layer, or reinstall is guaranteed to work. The value of the troubleshooting sequence is that each result gives support a narrower set of possibilities.
How do I interpret the common launch symptoms?
The wording on screen is a clue about where to look next, not a diagnosis by itself.
- “Preparing to Launch” appears, then disappears: complete the update and restart steps, then test Proton and verify the files. This pattern can occur when the selected runtime or local installation cannot complete startup.
- The game returns to the library immediately: compare the default Proton setting with one forced Proton version, then check the installation and library location.
- A visible error message appears: preserve the exact wording for the developer or Steam Support report. Avoid paraphrasing an error that may identify a launcher, runtime, or permission issue.
- Only this game fails: prioritize its compatibility details, Proton behavior, files, launcher, and storage path instead of system-wide recovery.
- Several games fail: treat the issue as potentially involving SteamOS, Steam, third-party Desktop Mode software, or storage, and postpone any factory reset until those broader checks are complete.
Which troubleshooting actions are reversible?
The sequence intentionally moves from low-impact maintenance to narrower installation and storage diagnostics.
| Action | Scope and diagnostic target | Reversibility and cost |
|---|---|---|
| Update and restart | SteamOS and Steam client state; broad maintenance | Free, low impact, no installed-game deletion |
| Change Proton | One game’s runtime; compares compatibility layers | Free and reversible per game; may download a different build for a native Linux title |
| Verify files | One installation; missing or damaged content | Free; Steam may replace files, but it is less disruptive than a reinstall |
| Clear download cache | Steam’s cached download data | Free; installed games remain, but you must sign in again |
| Repair or move library | Permissions, failed downloads, or storage path | Free if using existing storage; moving or reinstalling takes time and space |
| Buy a microSD card | Optional alternate library for storage comparison | Paid hardware; diagnostic only, not a guaranteed launch fix |
| Beta, reset, or re-image | Whole SteamOS installation | Broad and potentially disruptive; reserve for system-wide failures |
This comparison is why a factory reset belongs at the end, if at all. It has the widest scope and the least useful evidence for a single game, while updates, Proton comparisons, verification, and cache clearing are easier to undo and isolate.
What should I avoid while troubleshooting?
- Do not treat the Verified badge as proof that the present installation is healthy; certification and local files are separate questions.
- Do not change Proton, launch options, storage, and game files all at once. You will not know which change affected the result.
- Do not confuse a failed-file notice with proof that every file is corrupt; Steam notes that local configuration files can fail the comparison normally.
- Do not buy storage hardware as the first response. Use another library only when you need to test whether the original path is implicated.
- Do not factory-reset or re-image the Deck for one title before checking whether other games and SteamOS behave normally.
When should I stop troubleshooting and wait for a game update?
If SteamOS is current, the game files verify, multiple Proton versions behave the same way, and other titles launch normally, the remaining cause may be specific to the game’s current build or its bundled launcher. At that point, a developer report containing the exact symptom and the versions and storage paths tested is more useful than cycling through the same settings.
A Verified badge is a starting signal, not a promise that every future combination of game update, Proton release, launcher state, and local storage will launch unchanged. The ordered checks above let you separate a temporary Steam or installation state from a title-specific compatibility regression without immediately erasing the Deck.
Frequently Asked Questions
Can a game lose its Verified status after an update?
Valve’s compatibility review is ongoing, so the compatibility context shown for a title can change as the game and SteamOS evolve. Check the current compatibility details rather than relying only on how the badge behaved when you first installed the game.
How do I force Proton on Steam Deck?
Open the game menu, choose Properties, open Compatibility, enable “Force the use of a specific Steam Play compatibility tool,” and select one installed Proton version. Test one version at a time and compare it with the default setting.
Should I keep switching Proton versions until one works?
Test versions one at a time and record the result, then stop when the behavior is clear. Repeated untracked changes make it difficult to tell whether a later game or SteamOS update—not Proton itself—changed the outcome.
Does verifying files delete my saves?
File verification checks the game installation and replaces files Steam identifies as missing or damaged. It is less disruptive than deleting and reinstalling; do not manually remove save or configuration folders while troubleshooting.
What is the difference between file verification and clearing the download cache?
Verification checks the selected game’s installed content. Clearing the download cache refreshes Steam’s locally cached download data, leaves installed games in place, and requires signing in again.
Is a microSD card required to troubleshoot a launch failure?
No. Another library location is optional and useful only as a storage diagnostic. If the game works in a second location, that comparison gives support evidence about the original library; it does not make the card a universal compatibility solution.
When should I factory-reset a Steam Deck that will not launch one game?
Do not start with a reset. Reserve broad recovery for evidence that multiple games, Steam, or SteamOS are unstable after updates, restarts, disabled Desktop Mode applications, file checks, and storage tests.
What information makes a Steam Support report useful?
Include the exact on-screen or observed symptom, whether other games launch, the Proton setting and versions tested, and the library path. Also mention whether the failure began after a game or SteamOS update so support can distinguish a title regression from a local installation problem.
The Bottom Line
For a Steam Deck game that is Verified but will not launch, update SteamOS, restart, and disable Desktop Mode utilities first. Then compare Proton deliberately, verify the game, clear Steam’s download cache, and investigate the library or storage path. Use another location only as a diagnostic, and reserve Beta software or a factory reset for system-wide failures. If one title still fails while other games work, send the developer a precise symptom report with the Proton and storage tests you completed.