English · Español
Play a Steam family-shared game at the same time as its owner. SinglePayer injects into Steam and flips the client-side checks that would otherwise block you when your friend is already in-game.
- Grab
SinglePayer.exefrom Releases. - Run as admin.
- Search a game, click + Add, click Launch Steam with bypass.
That's it. Steam boots normally, the block is gone, both of you play.
Steam has a "family lock" that fires when a shared license is in use. It's enforced on your side by two branches inside steamclient64.dll message handlers — the "friend started playing this" handler sets a lock flag, the "please stop playing" handler acts on it. SinglePayer patches those branches to no-ops in memory at launch. No proxy DLL in your Steam folder, no files touched on disk.
Those patch offsets are pinned to a specific steamclient64.dll build. If Steam ships a new one, SinglePayer.exe will log patch SKIPPED — bytes don't match expected in %LOCALAPPDATA%\SinglePayer\singlepayer.log. Open an issue with that log and I'll push new offsets.
Needs .NET 8 SDK and MSVC BuildTools 2022 with the C++ workload.
powershell -ExecutionPolicy Bypass -File publish.ps1Output: publish\SinglePayer.exe.
- Windows 10/11, x64 Steam.
- Admin required — the injector needs write access into
steam.exe. - Doesn't touch Denuvo titles that verify per-launch server-side.
- GPL-3.0.