Download
depot / guides / gta-v

GTA V: Legacy, Enhanced and the week of waiting

When I first went looking for a "GTA V downgrade" I didn't actually need one — I needed the Legacy edition, a separate app I already owned. Half the people searching for it are in the same spot; the other half are single-player modders riding out the ScriptHookV update gap. This page sorts you into the right half, and is unusually loud about where downgraded builds must never go.

In March 2025 Rockstar split GTA V on PC into two products: Enhanced (app 3240220) — the current-gen rebuild with ray tracing and its own separate GTA Online population — and Legacy (app 271590) — the game as it had been since 2015. Everyone who owns GTA V owns both. The mod world did not migrate overnight: FiveM — the roleplay platform, now officially under Rockstar's wing — kept running on Legacy, with Enhanced support arriving on its own schedule, and the single-player modding stack (ScriptHookV and everything above it) lives its own version-locked life. Result: the words "GTA V downgrade" now mean two completely different operations, and the first job of this page is telling them apart.

01Where none of this goes: GTA Online

The bright red line Everything on this page is for story mode and FiveM. GTA Online runs anti-cheat (BattlEye on Legacy) and version-current servers, and connecting with a downgraded, modified or tool-injected client is how accounts get banned — Rockstar's tolerance for offline single-player modding famously does not extend one millimeter past the Online boundary. Keep pinned builds in their own folder, launch them offline, and let your clean, current install be the only thing that ever touches Online. FiveM is the exception by design, not by accident: its servers are separate infrastructure where modding is the point — and it manages its own client anyway.

02"Downgrading" to Legacy — actually just installing it

If your goal is FiveM RP and the Enhanced upgrade broke your setup: you don't need any downgrade tooling. Legacy is its own entry in your Steam library — install it, point FiveM at it, done. The wrinkle that confuses people is that Rockstar unlisted Legacy from the Steam store, so it can't be found by search — but unlisted is not removed: owners install it from the library as always, and the Legacy community forum is full of exactly this confusion ("why would you remove Legacy when people need it for FiveM?" — they didn't; they hid the listing). DepotDownloader sees through unlisting the same way your library does, which makes it a clean way to archive a Legacy copy while you're at it:

> .\DepotDownloader.exe -app 271590 -username you -remember-password -dir .\gtav-legacy

That's a ~100 GB archive, but it's the whole Legacy game, owned and downloaded through your own license — the kind of copy that outlives store-page decisions.

03The ScriptHookV window

The actual downgrade public. Single-player modding stands on Alexander Blade's ScriptHookV, ScriptHookV is locked to game builds, and every Rockstar title update breaks it — the "Unknown game version" error is a seasonal event. The fix arrives when Blade ships an update, historically days to a week or more after each patch; until then, a modded install has two options: wait, or roll the game back to the last build the hook supports. Hence the rhythm every LSPDFR and mod-list player knows: patch day → mods dead → either don't launch until the hook updates, or pin yesterday's build and keep playing. Prevention beats cure here — "only update when I launch" plus the read-only appmanifest_271590.acf trick means Rockstar's patch waits for you — but if the update already went through, the next section is the rollback.

04Pinning a build by manifest

Legacy's Windows content lives in depot 271591. The community's date-matching technique for this game is a nice refinement worth stealing for others: open SteamDB's patch notes for app 271590, click the update that broke things, find GTA5.exe in the modified-files list — and the crossed-out manifest ID shown there is the previous build, exactly the one you want. Then:

> .\DepotDownloader.exe -app 271590 -depot 271591 -manifest <previous-build-manifest> \ -username you -remember-password -dir .\gtav-pinned

Mind the scale — each pinned build is a full ~100 GB install, so this is a game where the filelist feature earns its keep: when a title update only touched the executable and a few RPFs, downloading just those files over a copy of your current install gets you the old build for gigabytes instead of the full hundred. (The Steam-console download_depot route works too and the older guides use it; the usual trade-offs from other pages apply.) This is Steam-copy guidance — Rockstar Launcher and Epic copies have no depot access, which is the same preservation lesson Cyberpunk taught, in Rockstar colors.

05Launching a pinned build

  1. Even Steam copies of GTA V boot through the Rockstar Games Launcher, and the launcher's instinct is to "repair" old builds forward. The community's standard companion for pinned story-mode play is the offline Social Club flag: add -scOfflineOnly to the launch arguments (or a commandline.txt in the game folder) so the launcher stops phoning home about versions.
  2. Keep the pinned build in its own folder with its era-matched ScriptHookV and mods — the era-discipline rule from every other guide here, GTA edition: game build, hook version, then mods.
  3. Returning to current is painless by design: "Verify integrity of game files" on your main install pulls you back to the live build. When I tested this, the offline flag was the piece I'd skipped at first, and the launcher quietly repaired my pinned build forward overnight — add it before you do anything else.

06Status in 2026

GTA V adds the third flavor of shelf-clearing to this series' collection: TF2's pre-2013 builds predate the system, Zomboid's pre-b41 were retired by the developer — and Legacy was unlisted, alive but hidden, one corporate decision away from the next stage. Its depots still answer (it's an actively played app with a FiveM ecosystem on top), recent-build manifests are the friendly case, and the deep history rides the usual manifest weather. The conclusion is the standing one, with extra force given whose catalog this is: if Legacy matters to your setup, the 100 GB archive folder is yours; the store listing never was. What I won't do is rely on the listing still being there next year — my own Legacy copy already sits in a folder, downloaded through my license, and that's the version I'd actually pick to keep.