If your mod list depends on a specific build of Cyberpunk 2077, the worst thing that can happen is a silent update that breaks every script mod you rely on. The fix is simple in theory: stop the launcher from updating the game, and if needed, roll back to a version your mods actually support.
Each launcher handles this differently, and Steam in particular has no built-in toggle for it. Here is how to lock your install on GOG, Epic and Steam, and what to do once you need to go back a version.
Why Modders Freeze the Game Version
A lot of core mods for Cyberpunk 2077 hook directly into the game’s executable or its scripting runtime. When the game gets patched, those hooks can break, sometimes silently, sometimes with a crash on launch. The RED Modding wiki’s general advice is blunt: don’t update the game until every framework and core mod you use has confirmed support for the new patch. That means checking mod pages before you let the launcher touch your install, not after.
This is less about being paranoid and more about sequencing. Modders who maintain the big frameworks usually need a bit of time after a patch drops to test and release updated builds. If you update the moment a new patch is live, you’re just waiting on the same timeline but with a broken game in the meantime.
Blocking Updates on GOG Galaxy
GOG gives you control both per game and globally.
- For just Cyberpunk 2077: open GOG Galaxy, find the game, click the small manage icon next to Play, choose Manage installation, then open Configure. From there you can stop the game from auto-updating.
- For every game on your account: go to Settings, then Game features, and uncheck Auto-update games.
The per-game option is cleaner if you only want to freeze Cyberpunk 2077 while letting other titles update normally.
Blocking Updates on Epic Games Launcher
Epic doesn’t offer a per-game switch, only a global one. In the launcher, open Settings and look under the Manage Games section. There you’ll find an option to disable auto-updates for all your installed games. Turn it on and Epic will stop silently patching anything, Cyberpunk 2077 included, until you manually tell it to update.
Blocking Updates on Steam
Steam simply doesn’t have a setting for this, which catches a lot of people off guard. The workaround the RED Modding wiki describes is making the game’s manifest file read-only.
- Close Steam completely.
- Find your
steamappsfolder. This sits two levels above the actual game install directory. - Inside
steamapps, locateappmanifest_1091500.acf. - Right-click the file, open its properties, and set it to read-only.
With that flag set, Steam can’t write to the manifest to register an update, so it effectively can’t patch the game. When you’re ready to update again, just undo the read-only flag on the same file and Steam will catch up on patches normally.
Downgrading to an Older Version
Blocking future updates is one thing. Sometimes you’re already on a patch that’s too new for your mods and need to go backward.
- GOG: use the same Configure dialog mentioned above. It lets you pick a specific older version of the game to install instead of the current one.
- Steam: right-click the game, open Properties, and go to Game Versions & Betas. Certain older versions are listed there and can be selected directly, though not every past patch is guaranteed to be available.
- Epic: according to the RED Modding wiki, there’s no supported way to downgrade through the Epic launcher. If you’re on Epic and need an older build, you’re stuck unless you find another way to get the files.
After switching versions, through either GOG or Steam, you may also need to clear the game’s script cache. If you run into odd behavior, stutters, broken mods that should work, or scripts that silently fail, deleting the cached compiled scripts and letting the game rebuild them on next launch often clears it up.
To confirm exactly what version you’re running, go to the game’s install folder, open binx64, right-click Cyberpunk2077.exe, open Properties, and check the Details tab. It will show you the file version, which you can match against what your mods list as supported.
Protect Your Saves Before You Switch
Before you downgrade or even update, copy your save folder somewhere safe. A save made on a newer patch can include data structures or script references that an older version simply doesn’t understand, and loading it there can fail outright or corrupt progress.
Keep a backup of your current saves before touching the version, test the downgrade or update with a copy, and only overwrite your main saves once you’ve confirmed everything loads and plays the way it should. It takes two minutes and it’s the difference between a minor annoyance and losing hours of progress.
Questions people ask
Will blocking updates on Steam also stop DLC and other content from updating?
The read-only trick targets the manifest file, which Steam uses to track the whole app, so it blocks all updates for that title, not just the base game.
Can I still play online or use cloud saves with updates blocked?
Cloud saves generally still work since they're handled separately from the update process, but some online features tied to a specific server version may not function correctly on an older build.
How do I know which game version my mods actually need?
Check the mod's page or description on the site you downloaded it from. Most core mod and framework authors list the exact patch version they've tested against.
Is there a way to downgrade on Epic at all?
Not through the launcher itself. The RED Modding wiki states plainly that Epic offers no built-in downgrade option, so Epic users are limited compared to GOG and Steam.
Browse all Cyberpunk 2077 mods on CrashMods
