Distribution
Windows only. A desktop application, not a service — nothing runs unless you open it.
Requirements
| Component | Requirement |
|---|---|
| operating_system | Windows 10 or 11, 64-bit |
| runtime | .NET 9 Desktop Runtime x64 — not the SDK, not ASP.NET |
| xbox / epic / ubisoft | An account for the service, and an internet connection |
| steam | Steam installed and signed in |
| gfwl | Nothing extra — the x86 injector ships with the app |
| xbox_360 | Profile package CON/LIVE/PIRS copied to the PC |
| disk_space | ~500 MB, mostly title data and backups |
Editing achievement and stat data carries risk on any live service — up to and including action against your account by the platform holder. That risk is real and it is yours to take.
Use a throwaway account if the account matters to you, and keep the backups the app writes before it edits anything.
Procedure
Five minutes, most of it waiting on the .NET installer.
The x64 Desktop Runtime — not the SDK, not the ASP.NET one. Without it the app will not start, and Windows reports a runtime error rather than anything useful.
A folder under your user directory or a second drive. Avoid Program Files:
the app writes backups and title data next to itself, and that directory needs admin
rights for every write.
Compare against the published SHA-256:
Get-FileHash .\AchievementLabs.exe -Algorithm SHA256
Windows marks downloads as blocked, which makes the injector fail in ways that look like bugs:
Unblock-File .\AchievementLabs.exe
The GFWL module injects into a running process and the Steam tools read and write game memory. Heuristic scanners flag that pattern regardless of intent.
Delete the executable and the data folder it created beside itself. Nothing is
written to the registry or to Program Files.
Support
Each platform module has its own support channel, plus a forum for bug reports. Include your app version, the game, and what you expected to happen.