Hello @EFinish, we're tracking issues with a game's launcher with the game they're paired with. Also, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/9045#issuecomment-5331480580.
ge-proton11-5x1 2026-08proton experimentalx1 2026-080x80091007x1 2026-08
Compatibility tool and version
Public bug report
Not yet filed / linked
System information
I'm reporting a bug
Actually more accurately: the game/launcher does not run at all — it fails during the Paradox Launcher v2 prerequisite install step before the game can start.
Steps for reproducing this issue
Setup Failed — 0x80091007 - Call failed.Log excerpt (from
launcher-installer.loginside the prefix)Note the digest lengths:
expectedis 40 hex characters (20 bytes → consistent with SHA-1), whileactualis 128 hex characters (64 bytes → consistent with SHA-512). This isn't a corrupted-download or stale-cache scenario (the "actual" value would still be a same-length SHA-1 digest, just a different value, if the payload itself had changed) — the bootstrapper appears to be hashing the downloaded payload with a different algorithm than the one the manifest's expected hash was computed with. This points to an algorithm-selection bug in Wine's bcrypt/CNG hashing implementation as invoked by this WiX Burn bootstrapper, rather than a bad download.What I already tried
compatdata/529340and let Steam rebuild the prefix from scratch — same failure.protontricks 529340 vcrun2022(bypassing the bootstrapper's own install path entirely) — the bootstrapper still re-downloads and re-verifies VC_REDIST_X64 on its own and fails at the same hash-verification step regardless, since it doesn't check pre-existing installs before re-verifying its bundled payload.Notes
2026.9under current Proton/Wine.