Fixing Steam Library Games That Won't Launch After a Client Update

The symptom is one of the most frustrating in PC gaming because nothing obviously crashes. You click Play, the button briefly changes to Stop, and then it returns to Play as if you never pressed it. Sometimes a launcher window flashes first. On Windows, the same class of problem can surface as an "Application was unable to start correctly" dialog that reappears every time you approve the permission prompt. Neither pattern tells you on its own whether the fault is in the game files, the client, the operating system, or a compatibility layer.

What follows is split by platform, because the evidence points to different causes. Work through the steps in order and stop when the game launches.

Windows: permissions and app data first

A user report on the Microsoft Q&A community described exactly this Windows pattern: the game would not start, an "Application was unable to start correctly" error kept appearing after approving the changes prompt, and the usual troubleshooting tips had not helped ^¹. The accepted answer there points at two likely causes, a corrupted app or permission settings that are not enabled, and recommends resetting the app. That is a reasonable first move because it is reversible in the sense that it clears app data rather than deleting the installation.

1. Open Windows Settings, go to System, then Apps and features.
2. Locate the affected game, open its Advanced options, and use Reset.
3. Restart the PC before testing again.
4. If the game still fails, check that app permissions are enabled for it, following the platform guidance linked from that answer.
5. If the reset changes nothing, verify the game's local files from Steam's own properties dialog for that title, since a corrupt download is the other common explanation for a binary that will not start.

When a step fails, do not repeat it. If the reset and a restart leave the error unchanged, the problem is unlikely to be stale app data, so move to file verification and then to the client itself. If verification reports no problems and the game still will not launch, the next suspects are the game's own prerequisites, such as redistributables, and any overlay or antivirus component intercepting the launch. The sources here do not establish a specific fix for those cases, so treat that as an area to investigate rather than a confirmed solution.

Linux and Proton: compatibility version first

On Linux the same "Play flips to Stop and back" behaviour usually traces to the Proton compatibility layer rather than to Windows permissions. An undated guide on fixing Proton launch failures identifies three usual suspects, the Proton version, leftover compatibility data, and a corrupt game file, and notes that swapping Proton builds is the single most effective fix because a title that breaks on one build often runs on another ^².

1. Right-click the game in your library and open Properties.
2. Go to the Compatibility tab and tick the option to force a specific Steam Play compatibility tool.
3. Choose a different Proton version, ideally a recent stable build, and launch again.
4. If the newest build fails, step back a version or two rather than assuming newer is better.
5. Clear the game's compatibility data if switching versions does not help.
6. Verify the local files if the game binary itself may be corrupt.
7. If all of that fails, try GE-Proton, the community build the guide names as handling many stubborn titles.

A separate report from the CachyOS forum shows why the per-game setting is not always enough. A user there replaced a proton-cachyos package during a system update and afterwards found that no games would launch, and that trying different Proton versions through the per-game dialog did not work either ^³. The fix that worked was changing the default at Steam's Settings, Compatibility level to a specific proton-cachyos build with the Steam Linux Runtime, because the previous default, experimental, apparently could not be overridden per game. After a Steam restart, everything worked again with no lost saves, including a modded title.

That last point is the useful diagnostic rule: if per-game Proton changes have no effect at all, the problem is probably above the game, in the global compatibility default, not in the individual title.

Reading the logs

The CachyOS thread's first reply is the step most people skip: check the log. Running Steam from a terminal, or enabling PROTON_LOG, is described there as the first thing to check when debugging Proton issues launched through Steam. The forum excerpt does not spell out what to look for in the output, so the honest position is that the log tells you where to look rather than what the answer is. If the log shows the game process starting and immediately exiting, that supports a compatibility or dependency problem. If it never starts at all, the launch configuration is the more likely culprit.

What remains unconfirmed

None of the sources establishes why a given update breaks a given title, and the CachyOS user explicitly said they did not know the cause, only that changing the global default resolved it. The Proton guide is undated, so its advice should be treated as general rather than tied to a specific client release. And no source here provides a fix for every Windows launch failure beyond the reset and permissions path. If the ordered steps above do not resolve it, the practical next move is to isolate variables: test a second game, test a second Steam account or library folder, and note whether the failure follows the title or the machine. That narrows the problem to the game, the client, or the system without guessing.

Sources

1. ¹ Steam - Microsoft Q&A - Skip to main content learn.microsoft.com
2. ² Fix Steam Games Not Launching Under Proton on Linux evezone.evetech.co.za
3. ³ Steam games no longer launch after last update - Issues & Assistance - CachyOS Forum - post by Raxyz on Jun 29 discuss.cachyos.org