Heroic Games Launcher ships two hotfixes in two days

Heroic Games Launcher has shipped two hotfixes in two days. Version 2.22.2 landed on 15 September and version 2.22.3 followed on 16 September, both aimed at problems introduced by the releases immediately before them.

Rockstar and Ubisoft first

The developers describe 2.22.2 as a response to issues identified after the previous hotfix, "especially with Rockstar and Ubisoft games". The build searches for a heroic executable on the PATH when the launcher's own binary has been renamed, removes the last remnants of Snap packaging support, and adds a CODEOWNERS file so pull requests automatically pull in the right reviewers.

The more consequential change is a switch to using UMU to provide the Steam Runtime, enabled automatically for native GOG titles. UMU is the community compatibility layer that lets Windows and non-Steam games run inside Valve's containerised runtime, and wiring it in by default is the kind of plumbing that changes how many games simply work after an update.

A regression, fixed fast

That change is also what broke things for some users. The 2.22.3 notes are candid about it: "The last release broke UMU for a lot of people and this new Hotfix should fix it." The fix stops the launcher nesting UMU when the Steam Runtime ends up enabled for a game that is not native, with the team describing this as hopefully their last hotfix before the next major release.

Heroic is a free, open-source alternative launcher that manages Epic, GOG and Amazon libraries in one place, and it runs on Linux, Windows, macOS and Steam Deck. That breadth is why its hotfixes matter: a compatibility regression does not hit one storefront, it hits every game a user has installed through it.

Our opinion

Two hotfixes in two days reads like a warning sign and is actually the opposite. Heroic is a volunteer-heavy project doing the least glamorous job in PC gaming — making three competing storefronts behave like one library on four operating systems — and the launches that go wrong are almost always the ones where compatibility layers get rewired underneath everything else. What matters is the turnaround and the honesty. The 2.22.3 notes do not dress the regression up as an edge case; they say it broke UMU for a lot of people and that this should fix it. For a launcher with no store to fall back on and no revenue to absorb a bad month, shipping a targeted fix within a day of a self-inflicted break, and naming the cause in public, is worth more than a roadmap. It is also a reminder that the convenience layer between players and their libraries is maintained by people who get very little credit when it works.