Problem: Steam Deck / SteamOS (Linux) “Proton forgot it exists” bug — Windows games suddenly show as “Not valid on current platform” + 0B/empty updates flooding Downloads

Published: 2026-02-23 12:15 (local time)

Quick Summary

• A recent Steam client issue on Linux/SteamOS can make Proton-capable games appear “Not valid on current platform” (as if Proton isn’t installed/available).
• Many affected users also report the Downloads page filling with “0B”/empty queued items or “updates,” making it hard to see real updates.
• It disproportionately hits Steam Deck / SteamOS users (often on Beta) and people with very large libraries.
• Valve has acknowledged and shipped a Steam Beta fix specifically for “very large libraries,” but not everyone is on the fixed build yet.
• Workarounds exist (switching Steam channels, clearing download queue, rebuilding Steam metadata), but none are perfect or universal.

What’s happening

Over the last few weeks, a frustrating Steam Deck / SteamOS (Linux) problem has been widely discussed: after a reboot or sometimes randomly, Steam appears to “forget” that Proton can run Windows games. Symptoms include:

• Installed games that previously ran fine on Steam Deck suddenly show as Windows-only or “Not valid on current platform.”
• You may be forced to open each affected game’s Properties and manually set a Proton compatibility tool again (or the game won’t launch / appears not installed).
• The Downloads view can get spammed with many “0B”/empty entries for installed games (sometimes looking like endless updates), obscuring real downloads and occasionally triggering repeated reinstall attempts for certain titles.

Reports indicate this can reproduce after restarts and can affect a large portion of a library, making it feel “account/library-driven” rather than tied to a single game. Community discussion points heavily at SteamOS/Steam client Beta users, though Linux desktop users can also encounter similar “Steam thinks I’m on the wrong platform” behavior.

Importantly, Valve has shipped a Steam Beta fix that explicitly targets a bug where Proton games show as “Not valid on current platform” for users with very large libraries, indicating this is a known client-side issue rather than “your Deck is broken.”

Likely causes (what research suggests)

• Steam client bug on Linux/SteamOS affecting Proton entitlements/visibility for large libraries. Valve’s Steam Beta changelog notes a Linux fix for Proton games showing “Not valid on current platform” for users with very large libraries, which matches the field reports closely.

• Downloads UI / queue state corruption or a scheduling bug that floods the Downloads view. The same Steam Beta changelog mentions an intermittent downloads view error when moving entries between scheduled and queued sections—consistent with “ghost/0B” queue items persisting.

• Channel mismatch or partial rollout effects (Stable vs Beta vs Preview). Many Deck owners run Beta/Preview to get features sooner. If the bug is fixed in Beta but a device isn’t updated (or is on a different channel), symptoms can continue even after other users report improvement.

Solutions & Workarounds

1) Update (or switch) to the Steam Beta build that includes the Linux large-library Proton fix

Who it helps: Steam Deck / SteamOS and Linux desktop users, especially with large libraries where games show “Not valid on current platform.”

• Steps:
  • On Steam Deck: go to Settings > System and check for updates (ensure Steam client updates are applied).
  • Opt into the Steam Beta channel (if you are on Stable and willing to test): in Steam settings, find the Beta participation option and switch to Beta.
  • Restart Steam (or reboot the Deck) after the update.
• Risks / tradeoffs: Beta can introduce new bugs. If you rely on maximum stability, consider waiting for Stable to receive the fix.
• Stop and contact official support when: You updated successfully and the issue persists across multiple restarts and after trying Solution #2 and #3 below.

2) Force a Steam client restart + clear “ghost” Downloads queue items

Who it helps: Users whose main pain is the Downloads page being flooded with empty/0B items, plus cases where Proton visibility “snaps back” after a restart.

• Steps:
  • Open Downloads and pause everything.
  • Cancel/remove the obvious 0B/empty items where possible.
  • Fully exit Steam (on Deck, restart Steam from the Power menu; on desktop Linux, quit Steam from the menu/Tray).
  • Launch Steam again and let it sit for a few minutes to rebuild state.
• Risks / tradeoffs: You may have to re-queue legitimate updates afterward. Cancelling downloads can delay shader cache updates.
• Stop and contact official support when: The Downloads list instantly refills on every restart and you can’t identify real updates anymore.

3) Toggle Proton settings to “re-register” compatibility, then validate with a known Windows-only title

Who it helps: Cases where Steam behaves as if Proton isn’t available, and games display as Windows-only.

• Steps:
  • Steam > Settings > Compatibility.
  • Toggle “Enable Steam Play for supported titles” off, apply, then turn it back on.
  • Also enable “for all other titles” temporarily, select Proton Experimental, apply.
  • Pick one known Windows-only game (or a game that previously required Proton) and attempt launch.
  • After verification, revert “for all other titles” if you prefer stricter default behavior.
• Risks / tradeoffs: Forcing Proton on all titles can change which builds Steam chooses for some games.
• Stop and contact official support when: Compatibility options are present but have no effect and the platform status remains wrong after reboot.

4) Reduce “library stress”: temporarily hide huge collections and avoid bulk operations until fixed

Who it helps: Very large libraries where the issue appears more often (as suggested by Valve’s fix targeting “very large libraries”).

• Steps:
  • Avoid mass-installing or updating dozens of games at once.
  • Limit scheduled downloads; keep only a few active at a time.
  • If you use multiple library folders/drives, temporarily keep installs concentrated in one location while troubleshooting.
• Risks / tradeoffs: Not a real fix; it just lowers the chance of the client hitting the edge-case again.
• Stop and contact official support when: Even with minimal activity, Steam still repeatedly mis-detects Proton/platform.

5) Last resort: Steam client reset (not a full factory reset) by backing up and rebuilding Steam’s local metadata

Who it helps: Users stuck in persistent corrupted state where every restart breaks platform validity and downloads state.

• Steps (high level):
  • Back up your important data (especially save data not in Steam Cloud, and any custom configs).
  • On SteamOS/Linux, move/rename Steam’s local data folder(s) so Steam regenerates them on next launch (keep a backup so you can roll back).
  • Re-add library folders inside Steam and let it re-index.
• Risks / tradeoffs: This can be time-consuming and may require re-downloading shader caches; mistakes can lead to lost local configs if you don’t back up.
• Stop and contact official support when: You’re not comfortable manipulating folders, or the problem returns immediately after a rebuild (suggesting it’s upstream/client-bug-related).

Prevention (so it doesn’t come back)

• Keep Steam/SteamOS updated, and track whether the “large library Proton validity” fix has landed on your chosen channel.
• Avoid huge simultaneous install/update waves on Steam Deck until the issue is fully stable on your channel.
• If you’re currently stable and unaffected, think carefully before opting into Beta/Preview—especially on a primary device.

FAQ

Q: Is this a Proton update problem or a Steam client problem?
A: Research and Valve’s own Steam Beta notes point to a Steam client issue on Linux/SteamOS that can mislabel Proton games as “Not valid on current platform,” especially with very large libraries.

Q: Why do I see hundreds of 0B/empty updates?
A: It appears related to a downloads view/queue bug; Steam Beta changelogs mention downloads view errors, and affected users describe flooded queues that don’t reflect real downloads.

Q: Does switching to Stable fix it?
A: Sometimes. If your current channel has the bug and Stable doesn’t (or vice versa), switching can help. But if the fix is only in Beta right now, Stable may still be affected until it rolls out.

Q: Will a factory reset fix it permanently?
A: Not guaranteed. Some reports indicate the issue can persist even after resets, implying it may be tied to client behavior and library/account edge cases rather than only local corruption.

Q: When should I open a support ticket?
A: If you’ve updated Steam/SteamOS, tried compatibility toggles, restarted Steam, and the platform validity still flips after reboots—open an official ticket and include reproduction steps and whether you have a very large library.

Q: Could this be caused by Decky plugins?
A: Some affected users report no Decky installed, so plugins aren’t required to trigger it. Still, if you use plugins, temporarily disable them to reduce variables.

Sources & References