When a Windows game refuses to launch on your Steam Deck or Linux PC, the single most effective fix is choosing the right Proton version for that specific title. Start with Proton Stable (the version Steam picks by default), move to Proton Experimental if Stable fails, then try Proton GE for stubborn cases, and finally test an older Stable release if a recent update broke things. This guide walks you through that decision process step by step, explains what each Proton branch actually does, and shows you how to use ProtonDB reports to skip the guesswork.
I have spent hundreds of hours testing Windows games across Steam Deck and desktop Linux, and version switching fixes the majority of launch failures I run into. Once you understand why versions differ and how to test them quickly, troubleshooting stops feeling random and starts feeling routine.
By the end of this article you will know how Proton works under the hood, how to change the compatibility tool for any game in under a minute, and how to recognize the failure patterns that point you toward a specific version. We will also cover the hard limits, like anti-cheat games that no Proton version can save.
Table of Contents
What Proton Actually Does? (And Why Versions Matter)
Proton is Valve’s compatibility layer that translates Windows system calls into Linux equivalents so Windows games can run on Steam Deck and Linux desktops without a native port. It is not an emulator. Instead, it sits between the game and Linux, rewriting DirectX graphics calls into Vulkan, mapping Windows audio and input APIs to Linux, and handling all the little differences that would otherwise break the game.
Under the hood, Proton bundles three core components: DXVK (which translates DirectX 9, 10, and 11 into Vulkan), vkd3d-proton (which translates DirectX 12 into Vulkan), and wine-proton (which handles the rest of the Windows API surface). Together these form a translation stack that lets a Windows game “think” it is running on Windows while Linux handles the actual work.
Versions matter because that translation stack is constantly being improved. Each new release fixes bugs for specific games, adds support for newer DirectX features, and tightens compatibility with anti-cheat systems. But updates can also introduce regressions, where a game that worked fine on Proton 8 suddenly crashes on Proton 9. That tension between fixes and regressions is exactly why you sometimes need to manually choose an older or different Proton version.
Think of it like a printer driver. A newer driver often improves things, but occasionally a specific document that printed cleanly last year starts choking on the update. The fix is not to abandon the printer, it is to install the driver version that worked for that specific file. Proton works the same way.
How to Choose the Right Proton Version When a Game Won’t Run: Quick Decision Path?
When a game fails to launch, work through this decision path in order. Stop the moment a version makes the game run, and keep notes on what worked so you do not repeat the cycle later.
Step 1: Try Proton Stable first. This is the version Valve ships as the default, and it is the most tested. If a game shows a green Steam Play Verified badge, Stable should almost always run it without issue.
Step 2: Switch to Proton Experimental. Experimental includes fixes that have not graduated to Stable yet. It is the best choice for recently released games, for titles that got an update in the last few months, and for any game that Stable fails on without a clear reason.
Step 3: Check ProtonDB for the exact version other players use. Search the game’s ProtonDB page, sort reports by date, and look at which version the most recent successful reports mention. Players often call out a specific version that “just works” for that title.
Step 4: Try Proton GE. GE (GloriousEggroll) is a community build that packs in patches Valve has not merged yet, plus fixes for media playback, cutscenes, and specific game bugs. It is the go-to for games with video issues, missing codecs, or odd crashes that mainline Proton ignores.
Step 5: Roll back to an older Stable release. If a game worked before a recent Proton update and now does not, an older version like Proton 7.0 or 8.0 often restores it. Older games in particular frequently run better on older Proton builds.
Step 6: Rule out non-Proton causes. If none of the above works, the problem is likely not Proton. Verify game files, disable Steam Input, check for anti-cheat blocks, and look at the PROTON_LOG output to see what is actually failing.
Understanding the Three Main Proton Branches
Choosing the right Proton version is much easier once you understand what each branch is built for. The three branches below cover 99 percent of real-world cases.
Proton Stable: The Reliable Baseline
Proton Stable is Valve’s main release branch and the version Steam assigns by default to most games. Each Stable release is numbered (Proton 7.0, 8.0, 9.0, and so on) and represents a snapshot of Proton Experimental that Valve has tested enough to promote. Stability is the whole point here.
Stable is the right choice for any game that carries a Steam Deck Verified or Playable rating, and for older titles that have run on Linux for years. Most of the time, you should never need to change off Stable. If a Verified game fails on Stable, suspect a corrupted install, a failed update, or an anti-cheat block before you blame Proton itself.
Proton Experimental: Newer Fixes, Less Testing
Proton Experimental is Valve’s rolling branch. It receives fixes and features faster than Stable, which means it solves problems Stable cannot, but it also means it can break in ways Stable will not. Experimental is where Valve tests changes before promoting them.
Use Experimental for brand-new releases (especially in the first few months after launch), for games that received a major patch recently, and as your second try whenever Stable fails on an unknown issue. Experimental is also a good default for “Proton Hotfix,” which is a faster-moving variant Valve sometimes pushes for breaking fixes. If you are unsure, prefer Experimental over Hotfix because Experimental gets more testing.
Proton GE: Community Builds With Extra Patches
Proton GE (short for GloriousEggroll, the maintainer’s handle) is a community-maintained build of Proton that layers extra patches on top of Valve’s work. It typically includes media codec fixes, game-specific tweaks, FSR updates, and patches for titles that Valve has not gotten to yet. You install it through ProtonUp-Qt on desktop or the ProtonUp-Qt Flatpak on Steam Deck.
GE is the best tool for games that suffer from missing video, broken cutscenes, audio dropouts, or weird crashes that Stable and Experimental both ignore. It is also popular for games whose ProtonDB reports specifically mention GE as the working version. GE is not always better than Valve’s builds, so use it as a targeted fix, not as a default replacement for Stable.
Step-by-Step: How to Change the Proton Version for a Game
Changing the Proton version takes about 30 seconds once you know where the setting lives. The steps below work for any game in your Steam library, including non-Steam games you have added manually.
Step 1: Open Steam and right-click the game in your Library, then select Properties.
Step 2: In the Properties window, switch to the Compatibility tab.
Step 3: Check the box that says “Force the use of a specific Steam Play compatibility tool.”
Step 4: Open the dropdown menu and pick the Proton version you want to test (Proton Experimental, Proton GE, or any numbered Stable release you have installed).
Step 5: Close the Properties window and launch the game. Steam may show a small download the first time you switch versions, which is it installing that Proton build and rebuilding the game’s compatibility prefix.
On Steam Deck the steps are nearly identical. Press the Options button (the “…” menu) on a game in your Library, choose Properties, then Compatibility, and select your Proton version from the dropdown.
Enabling Proton for non-Steam games or all titles: If you want Proton available for everything, open Steam Settings, go to Compatibility, and toggle “Enable Steam Play for all other titles.” Choose a default version (Proton Stable or Experimental) and restart Steam. This is also required if you want to add external games like Epic or GOG titles through shortcuts and run them through Proton.
Tip: When you switch versions, Steam creates a separate compatibility prefix for each one. This is why your save files usually stay intact, but also why your first launch after a switch can take longer than usual as the prefix is rebuilt.
How to Use ProtonDB to Find the Right Version in 2026?
ProtonDB is the single best resource for picking a Proton version without guesswork. It is a community-run database where Linux and Steam Deck players submit reports on how games run, including which Proton version they used and any tweaks they applied.
To use it well, search for the game on protondb.com, then sort the reports by newest first. Recent reports matter more than old ones because they reflect the current state of Proton and the game itself. A report from two years ago may recommend Proton 5.13, which is irrelevant today.
Look for reports tagged with the Steam Deck icon if you play on Deck. Steam Deck reports are far more relevant than generic Linux desktop reports because Deck has a fixed hardware target, and what works there almost always works on similar hardware.
Pay attention to the signal-to-noise ratio. If the top five recent reports all mention Proton Experimental and describe smooth play, that is a strong signal. If they scatter across three different versions with mixed results, the game is probably finicky and you should expect to test more than one option.
Take notes from the tweaks sections. Players often list launch options like PROTON_HIDE_NVIDIA_GPU=0 or DXVK_ASYNC=1, disabled Steam Input, or specific in-game settings that made the difference. Copying the exact configuration from a successful report can save you an hour of trial and error.
Common Failure Patterns and Which Proton Fixes Them
Different failure modes point to different fixes. Matching the symptom to the right Proton version dramatically shortens troubleshooting.
Game closes instantly with no error: Often a missing dependency or a prefix problem. Try Proton Experimental first, then verify game files. If that fails, delete the game’s compatibility prefix (found in ~/.local/share/Steam/steamapps/compatdata/[appid]) so Steam rebuilds it on next launch.
Game launches but crashes during cutscenes or videos: Almost always a media codec issue. Switch to Proton GE, which includes extra codec patches Valve’s builds do not ship. This is the single most common GE use case.
Game ran fine last week and now does not launch: Likely a regression from a Proton update. Roll back to the previous Stable version, or try Proton Experimental if the regression came from a Stable update. Check the game’s ProtonDB page for recent reports that confirm the regression.
Game complains about anti-cheat or boots you from multiplayer: No Proton version fixes this. Games using EasyAntiCheat or BattlEye only work on Linux if the developer has explicitly enabled Linux support in the anti-cheat backend. Proton cannot bypass this, and trying different versions will not help.
All your Proton games suddenly fail at once: Not a per-game issue. Your Proton installation is likely corrupted or a Steam update broke something. Reinstall the affected Proton version through Steam Settings, Compatibility, and if that fails, verify your Steam installation.
Stuttering or poor performance: Often a shader cache issue rather than a version issue. Let the game run for a few minutes so the cache fills, or try Proton Experimental which tends to have better DXVK and vkd3d-proton versions. Disabling Steam Input can also reduce overhead.
Using PROTON_LOG for advanced debugging: If nothing obvious works, enable logging. Set the launch option PROTON_LOG=1 %command% in the game’s Properties, launch it, let it fail, then read the log file written to your home directory. The log path is typically ~/steam-[appid].log. Look for the last lines before the crash, which usually name the missing function or failing component and point you to the right Proton version.
When Older Proton Versions Work Better Than Newer Ones?
This is the part most guides gloss over: newer is not always better. Proton development moves fast, and a fix for one game can break another. The result is that some older titles actually run more reliably on older Proton versions, even years after newer releases shipped.
Games from the DirectX 9 and early DirectX 11 era are the most common example. A title built in 2010 may have been thoroughly tested against Proton 5 and 6, with fixes for its specific quirks, and then regressed when Proton 7 or 8 rewrote part of the translation layer. For these games, Proton 7.0 sometimes outperforms Proton 9.
Modded games can be even more sensitive. Mods that hook into specific Windows API behavior may rely on quirks present in one Proton version and gone in the next. If you run a heavily modded Skyrim or Fallout, check the mod community’s current recommended Proton version, because it is often older than you would expect.
The way to roll back safely is simple. Open the game’s Compatibility dropdown, install the older Proton version you want (Steam keeps several numbered versions available), select it, and test. Because each version uses its own compatibility prefix, switching back and forth does not corrupt your saves. Keep both versions installed if a game is finicky, so you can flip between them without waiting for a download.
If you find an older version that works and a newer one that does not, file a regression report. Valve and the community actively track these, and a clear report is often what gets the fix into a future Experimental build.
FAQs
How to know which Proton version to use?
Check the game’s ProtonDB page, sort reports by newest first, and use the version the most recent successful reports mention. As a default, start with Proton Stable, then move to Proton Experimental, then Proton GE if those fail.
How to force a game to run on Proton?
Right-click the game in your Steam Library, open Properties, go to the Compatibility tab, check ‘Force the use of a specific Steam Play compatibility tool,’ and pick a Proton version from the dropdown. On Steam Deck, use the Options button (…) and choose Properties, then Compatibility.
How to set Proton version?
Open the game’s Properties in Steam, switch to the Compatibility tab, tick the box to force a specific compatibility tool, and select the Proton version from the dropdown list. The change applies immediately and Steam rebuilds the prefix on the next launch.
What games don’t work with Proton?
Games that use EasyAntiCheat or BattlEye without Linux support enabled by the developer do not work on Proton, no matter which version you choose. A small number of games with aggressive DRM or kernel-level anti-cheat also block Linux play. Always check the game’s ProtonDB page before buying.
Should I use Proton Experimental or Proton GE?
Use Proton Experimental for newly released games and as your second try when Stable fails. Use Proton GE for games with broken cutscenes, missing video codecs, audio issues, or specific bugs Valve has not patched yet. GE is a targeted fix, not a daily driver.
Which version of Proton should I use as my default?
Use Proton Stable as your default for everything, since it is the most tested branch and what Valve ships by default. Switch to Experimental or GE only for specific games that fail on Stable. Avoid setting GE or Experimental as your global default, because their faster update pace can introduce regressions across your whole library.
Conclusion
Choosing the right Proton version comes down to a simple order: Stable first, Experimental second, GE third, and an older Stable release when an update breaks a previously working game. Pair that decision path with ProtonDB reports and you can solve most launch failures in minutes instead of hours.
Knowing how to choose the right Proton version when a game won’t run is the difference between trusting the Steam Deck Verified badge and actually getting every title in your library playable. Keep a note of what works for each finicky game, file regression reports when updates break things, and remember that anti-cheat games are a hard limit no Proton version can overcome.