Hello @BlackomegaTM, in general, no, the Steam client should not have a comprehensive toolset to verify or alter wineprefixes. There's too many permutations of compatibility tool that can arbitrarily change at any point in the future or by third parties builds of tools.
The only sane option when dealing with unknown snafus is to optionally copy out saves if the game doesn't support cloud saves, then purge the wineprefix so the currently selected version of Proton can generate a new one the next time its started. That general request is already being tracked at #5687.
At least in environments where it's not easy to access a file browser like Steam running on the Steam Deck in game mode, Steam provides an option to blindly delete the wineprefix.
Nothing extracted yet.
Feature Request: Add Proton Prefix Management to the Steam Client
Summary
The Steam client should provide built-in tools to inspect, reset, recreate, back up, and open Proton prefixes for individual games.
At the moment, Proton prefixes are a critical part of how Windows games run on Linux, but Steam exposes almost no controls for managing them. When a prefix becomes corrupted or contains an inconsistent configuration, users are often forced to discover the relevant
compatdatafolder manually, use the terminal, or rely on third-party tools.For experienced Linux users this is inconvenient. For new users, it can make a game appear completely broken with no clear explanation or recovery path.
Problem encountered today
Today I had a problem with Lies of P involving Steam Cloud saves.
The same Steam account, game version, and save data were being used on both a Steam Deck and a Bazzite desktop.
On the Steam Deck, the game correctly used the expected save path:
On the desktop, Steam Cloud correctly downloaded the save files and created the folder containing my Steam account ID before the game launched.
However, when the game started, it ignored that folder, behaved as though it were the first launch, and created new save files directly inside:
instead of:
Steam reported that Cloud synchronization was successful, file integrity verification found no problems, the game version was identical on both devices, and there were no mods or modified game files.
The issue was ultimately resolved only by manually deleting the game's Proton prefix from:
After Steam recreated the prefix, the game immediately detected the correct Steam account folder and loaded the cloud save normally.
From the user's perspective, nothing in the Steam client indicated that the prefix was the source of the problem.
Previous save-path problem involving case sensitivity
I have also encountered another Proton-related save issue caused by differences in path capitalization.
A game created or expected a save directory using a folder name with a capital letter, while another environment used the equivalent folder name with different capitalization.
On Windows, this difference generally does not matter because the filesystem is normally case-insensitive. On Linux, however, folders such as:
and:
are different directories.
As a result, the Windows and Linux versions effectively wrote saves to different locations, even though the paths appeared equivalent to an ordinary user.
This kind of problem is extremely difficult to diagnose through the Steam interface. Steam Cloud may report successful synchronization while the game continues reading from a different directory.
A built-in option to open the prefix and relevant save directories, or at least display their locations, would make these problems far easier to identify.
Previous corrupted shader problem
When I was still unfamiliar with Linux, I also experienced a game that stopped working correctly because of corrupted shader data.
At the time, I did not understand the distinction between:
Verifying the game files did not solve the issue, because the corrupted data was outside the normal installation directory.
There was no clear option in Steam explaining what could be safely reset. I did not know which directory was responsible, what could be deleted, or whether deleting it would also remove save files.
A less technical user could easily respond by reinstalling the entire game, reinstalling Steam, or even abandoning Linux, despite the real fix being only the removal of a corrupted prefix or shader cache.
Suggested interface
Steam could add a section under:
or:
with options such as:
Safety considerations
Steam should warn the user that a Proton prefix may contain:
Before deleting or recreating a prefix, Steam could scan for common save locations and offer to create a backup.
For example:
The client could also distinguish between:
Reset configuration only
Preserve detected save files while recreating the rest of the prefix.
Recreate entire prefix
Back up the existing prefix and generate a completely new one.
Open folder
Allow advanced users to inspect the prefix without using the terminal.
Why this belongs in Steam
Steam already provides user-facing options for:
The Proton prefix is just as important as the game installation itself. A broken prefix can prevent a game from launching, cause saves to be ignored, break launchers, preserve invalid registry settings, or create inconsistent behavior after changing Proton versions.
Yet it remains almost entirely invisible in the Steam interface.
Users should not need to know the AppID, locate the correct Steam library, navigate to
steamapps/compatdata, and manually delete directories from a terminal to perform a basic repair operation.Expected benefit
A built-in Proton prefix manager would:
The problem I experienced today was solved immediately by recreating the prefix. The difficult part was not the repair itself, but discovering that the prefix was responsible and knowing how to remove it safely.
Steam should expose this functionality directly in the client.