Cyberpunk 2077 mods not working after patch 2.5? Framework status and fixes

Cyberpunk 2077 is on Update 2.5, the Edgerunners 2 Update, which came out on October 22, 2026. Hotfix 2.500.200 followed on October 27. Update 2.5 changed the game code that the script frameworks hook into, so mod lists broke within hours. Official 2.5 builds of every core framework are out now. If your mods still won’t work, the usual cause is an old framework file, one outdated mod, or a mod in the wrong pipeline.

Changelog: November 13, 2026. Framework versions re-checked against the official 2.5 releases and hotfix 2.500.200. Added the Battle.net release, system checks, and the “flatlined” and TweakDB error messages.

On this page

1. Quick fix: why your Cyberpunk 2077 mods stopped working
2. Find your symptom
3. Before you start: system checks
4. Step 1: Check your game version and what changed in 2.5
5. Step 2: Update the core frameworks in the right order
6. Step 3: Find the outdated mod
7. Mods not showing up in game
8. “Enable mods” toggle or slider not working in the launcher
9. Three ways to mod Cyberpunk 2077 and how each one breaks
10. Cyberpunk 2077 mods not working in Vortex
11. CET overlay or CET mods not working
12. Crashes after installing mods
13. Log files: where they are and what to look for
14. Console mods (PS5, Xbox Series X|S) not working
15. In-game mod.io mods on PC
16. Stop the game updating itself while you’re modded
17. Nothing works: clean reset, wait, or stay on 2.31
18. FAQ

Quick fix: why your Cyberpunk 2077 mods stopped working

Update 2.5 broke the script frameworks that almost every PC mod depends on. To fix it, update RED4ext, ArchiveXL, TweakXL, Codeware, redscript and Cyber Engine Tweaks to their 2.5 builds. Then update or remove every mod that hasn’t had a release since October 22, 2026.

The short version:

1. Check the version number in the main menu. It should say 2.5 (build 2.500.200 after the hotfix).
2. Install RED4ext 1.31.0 or newer, then ArchiveXL 1.28.0, TweakXL 1.12.0, Codeware 1.21.0 and redscript 0.5.32, then Cyber Engine Tweaks 1.38.1 or newer.
3. Launch once. If a redscript error popup names a mod, disable that mod first.
4. Disable every mod with no update since October 22, 2026, then turn them back on in batches.
5. If the game still won’t start, read the logs (the paths are below), or reset to an unmodded install and rebuild.

If you already know your symptom, the triage table below tells you which section to read. The rest of the page covers each fix in detail, including console mods and the new in-game mod.io menu.

Find your symptom

Start with what you can see, not with what you think broke. Each symptom points to a different layer of the mod stack. The “Section” column uses the heading names from the table of contents.

Before you start: system checks

About five minutes of system checks rules out the crashes that no mod fix will solve. The RED Modding wiki’s troubleshooting guide puts these “first steps” ahead of any log reading, and they explain a lot of the “I updated everything and it still crashes” threads.

Two of these need more explanation.

Visual C++ and .NET. Install the latest x64 Visual C++ 2015-2022 Redistributable from Microsoft even if you think you have it. A repair install costs nothing and fixes the case where CET’s log folder stays empty. For .NET, install the Desktop Runtime (not only the plain .NET Runtime) that matches the version named in the error message. Vortex checks for it at startup.

Intel 13th and 14th gen instability. Intel traced crashes on many 13th and 14th gen desktop processors (65 W and higher) to a voltage problem it calls Vmin Shift. It released microcode 0x12B through motherboard BIOS updates as its fix. Intel’s own statement says the update prevents the damage but can’t repair a chip that is already unstable. Shader compilation is one of the workloads where the crashes showed up, and Cyberpunk compiles shaders after every patch. If you have a Core i7 or i9 from these generations and the game crashes at random even with zero mods, update the BIOS before you spend an evening bisecting. If the crashes continue, contact Intel or your retailer about the warranty.

Step 1: Check your game version and what changed in 2.5

You should be on 2.5, which means hotfix 2.500.200 if your store has patched since October 27. Every framework release since October 22 targets this version. Cyber Engine Tweaks says on its GitHub release page that its 2.5 build drops support for earlier patches.

Where to see your build number

The game version shows in the bottom corner of the main menu. If it reads 2.31, your store hasn’t updated the game yet. The 2.5 framework builds are then the wrong ones, and you need the older releases instead.

The hotfix was small, about 1 GB. Coverage of its notes, including MP1st’s report on October 27, says the main fix was for players in Argentina who couldn’t reach their saved game data. Some idle-animation and eye mods reportedly stopped working after the hotfix. If yours broke on October 27 rather than October 22, check their Nexus pages for a newer upload.

Why script frameworks break on every patch

Frameworks such as RED4ext and Cyber Engine Tweaks don’t use an official modding API. They find functions inside the game’s executable and attach to them. Any patch that rebuilds the executable moves those functions, so the hooks miss and the game crashes or the framework refuses to load.

Archive mods (textures, meshes, clothing) are far more robust because they only replace game files. They still break when a patch changes the original file they replace, which explains most of the “my textures broke” reports after big updates. Script mods sit one level higher. They depend on game classes and functions that CD PROJEKT RED can rename or remove.

That’s why 2.5 broke things in a predictable order. The frameworks failed on day one. Official builds came within days, with most of the stack fixed by October 25, and individual mods have been catching up since.

Steam, GOG, Epic and Battle.net installs

Mods behave the same on every PC store, but the install folders differ, and mod managers find the game by checking known store paths. According to Blizzard’s announcement, Cyberpunk 2077 also launched on Battle.net on November 10, 2026 (November 11 in Australia), with the Edgerunners 2 Update included.

If you bought the game on Battle.net, or moved an install there, your mod manager may not detect it automatically. Point it by hand at the folder that contains bin\x64\Cyberpunk2077.exe. Everything inside that folder (archive, r6, red4ext, mods) works the same way it does on Steam or GOG.

Step 2: Update the core frameworks in the right order

This step fixes most “can’t launch the game with mods” reports. Install the 2.5 build of every framework before you launch the game even once. Update RED4ext first, because ArchiveXL’s page says it needs RED4ext 1.31.0 or newer.

Minimum core framework versions for Cyberpunk 2077 2.5

These versions come from the mod authors’ Nexus Mods and GitHub pages and from the Nexus “Patch 2.5 Notes for Modders” post, as of November 2026. ModSafe’s compatibility tracker lists the same set, with redscript 0.5.32, and rates Patch 2.5 as safe for them. Newer point releases also work. Older ones don’t.

Two common UI dependencies sit on top of this stack. Mod Settings (by jackhumbert) is a RED4ext plugin with redscript, and Native Settings UI runs through Cyber Engine Tweaks. Neither helps until the frameworks underneath are current. After that, check their own Nexus pages for a release posted after October 22, 2026.

RED4ext 1.31.0 first

RED4ext is the loader that every RED4ext plugin depends on, including ArchiveXL, TweakXL, Codeware and Mod Settings. Install it first and overwrite the old files instead of merging with them.

GitHub issue #153 on the RED4ext repository, titled “All RED4Ext plugins broken in CP2077 2.5 Edgerunners II update”, explains the most common confusion. The maintainer confirmed that the RED4ext loader itself ran on 2.5. The crashes came from plugins built before 2.5, such as ArchiveXL 1.27.5 and TweakXL 1.11.5. Updating RED4ext alone doesn’t stop the crash. Every plugin in red4ext\plugins has to be a 2.5 build too.

A single user comment on the RED4ext Nexus page, dated November 12, reports that the newest RED4ext stopped working once other core mods updated, and that going back to the previous RED4ext fixed it. That’s one report, not a confirmed bug. If the same thing happens to you, check the Posts and Bugs tabs on the RED4ext page and the GitHub releases list for a point release before you downgrade anything.

ArchiveXL, TweakXL and Codeware

psiberx made all three, and all three load as RED4ext plugins. Install ArchiveXL 1.28.0, TweakXL 1.12.0 and Codeware 1.21.0 next. Codeware’s Nexus page lists 2.5 compatibility with redscript 0.5.32 or newer, so update redscript in the same pass.

In the first days after the patch, unofficial community 2.5 builds of RED4ext, ArchiveXL, TweakXL and Codeware circulated on GitHub. You may have used one. Their maker has retired them, and the Nexus “Patch 2.5 Notes for Modders” page now carries “(Unofficial Fix Retired)” in its title. Replace those files with the official releases. A mix of unofficial and official builds often explains the “everything is updated and it still crashes” reports.

redscript 0.5.32

Redscript is the compiler that turns .reds script mods into the game’s script cache every time you launch. Extract the release archive into the game’s root folder so its files land in engine and r6. Codeware’s 2.5 build needs 0.5.32 or newer.

Cyber Engine Tweaks

CET goes into bin\x64\plugins. Its GitHub release for 2.5 (v1.38.0) says it supports patch 2.5 and no longer supports earlier patches. The locked sticky on the CET Nexus page tells you to update the game to 2.5 and run CET 1.38.1 or higher, together with updated redscript and RED4ext.

CET also needs the Microsoft Visual C++ Redistributable (the 2015-2022 x64 package) from the system checks list. If CET shows no overlay at all and its log folder stays empty, reinstall that package before you suspect anything else.

What you should see after this step

Once the frameworks are current, the game should reach the main menu with no redscript popup, and the CET overlay should open with the key you bound. If it does, the stack works and any remaining problem is an individual mod. If the game still crashes before the menu, go to the log files section.

Step 3: Find the outdated mod

With the frameworks updated, leftover problems almost always come from individual mods that haven’t been updated for 2.5. The quickest way to find them is by upload date: any script-based mod last updated before October 22, 2026 is a suspect.

On each mod’s Nexus Mods page, open the Files tab and compare the date of the newest file with October 22. Read the Posts and Bugs tabs too. Mod authors usually pin a “2.5 status” comment, and other users report breakage there within hours. Some mods never need an update (pure texture or mesh replacers often survive), so a missing post-2.5 file doesn’t prove a mod is broken. It only tells you where to look first.

Reading the redscript compile error popup

When redscript fails, a popup at launch says script compilation failed, usually with a file path. That path names the culprit, for example r6\scripts\SomeModName\Something.reds. Disable that mod first.

This matters more than it seems. Redscript compiles all script mods into one cache, so a single compile failure stops the whole set. One outdated mod can switch off every other script mod you have, including ones that work fine on 2.5. Players often blame the wrong mod because everything stopped at the same moment.

If the popup doesn’t clearly name a file, open r6\logs\redscript_rCURRENT.log and search for “error”. Each entry gives the file and the line number. Errors such as “unresolved function” or “unresolved type” usually mean the mod calls something 2.5 renamed, or needs a framework (often Codeware) that you don’t have.

Bisecting with Vortex

Bisecting means turning off half your mods, launching, and halving again until only the broken mod is left. It sounds slow, but 100 mods take about seven launches.

1. Leave the frameworks (RED4ext, ArchiveXL, TweakXL, Codeware, redscript, CET) enabled.
2. In Vortex’s Mods tab, select half of the remaining mods and disable them.
3. Click Deploy Mods. Vortex only changes the game folder when it deploys.
4. Launch. If the problem is gone, the culprit is in the half you disabled. If it’s still there, it’s in the half still enabled.
5. Repeat with the guilty half until one mod remains.
6. Update that mod, report it on its Nexus page, or leave it off until its author posts a 2.5 release.

Keep each mod together with its requirements when you split. Turning off a library while the mods that need it are still on creates new errors that have nothing to do with the original fault.

Bisecting manually

For manual installs, move files out of the game folder into a backup folder instead of deleting them. These are the folders to empty:

• archive\pc\mod (legacy archive mods, plus .xl files for ArchiveXL)
• mods (REDmod-format mods)
• r6\scripts (redscript mods)
• r6\tweaks (TweakXL mods)
• bin\x64\plugins\cyber_engine_tweaks\mods (CET mods)
• red4ext\plugins (RED4ext plugins, but keep the framework plugins in place)

Move half of a folder’s contents out, test, and continue the same way. Manual installs make this slow, which is a good reason to switch to a mod manager before the next major patch.

Mods not showing up in game

If the game launches fine but a mod has no visible effect, 2.5 itself is almost never the cause. The usual causes are a wrong folder, a missing requirement, or a REDmod mod that was never deployed.

Legacy archive vs. REDmod folders

Cyberpunk 2077 loads archive mods from two places, and they follow different rules.

A common mistake is unzipping a REDmod mod into archive\pc\mod, or the reverse. Open the mod’s archive and look at the folder structure. If it contains mods\<name>\info.json, it’s a REDmod. If it contains archive\pc\mod\something.archive, it’s legacy. Extract from the game’s root folder so the paths line up.

Nested folders cause another frequent fault. archive\pc\mod\SomeMod\archive\pc\mod\file.archive will never load. The .archive file has to sit directly in archive\pc\mod (some mods allow one subfolder, and their pages say so).

If two legacy archives change the same file, the one that sorts first alphabetically wins. Mod authors sometimes add a prefix such as # or zz to the file name to control this. Read the mod page before you rename anything.

Missing requirements

Every Nexus page lists its requirements near the top of the Description tab, and the Files tab often adds notes for each version. A clothing mod that needs ArchiveXL won’t show up without it. A script mod that needs Codeware fails to compile without it, which also stops all your other script mods.

Check the requirement versions too. A 2.5 update of a mod may need ArchiveXL 1.28.0 specifically. Having ArchiveXL installed isn’t enough if it’s still 1.27.5.

“Enable mods” toggle or slider not working in the launcher

The “Enable mods” toggle in the REDlauncher (and its equivalent in GOG Galaxy) only controls REDmod-format mods. It doesn’t affect Cyber Engine Tweaks, RED4ext plugins, redscript mods, TweakXL tweaks or loose archive mods. Those load whether the toggle is on or off.

That changes how you should read two common complaints:

• “The slider is on but my mods don’t work.” If your mods are CET, RED4ext or legacy archive mods, the slider was never involved. Go back to Step 2 and Step 3.
• “The slider is greyed out or won’t stay on.” On PC, the REDmod tool is a free, separate DLC. On Steam, check the game’s DLC list and make sure REDmod is installed. On GOG Galaxy, enable it in the game’s installation options. Without the DLC, the launcher has nothing to switch on.

When the toggle is on, the launcher runs REDmod’s deploy step. It merges the mods in the mods folder, rebuilds the script and tweak caches in r6\cache\modded, and starts the game in modded mode. When it’s off, the game ignores the mods folder and that cache.

If you use Vortex, you don’t need the REDlauncher toggle. According to the Vortex Cyberpunk extension’s Nexus page, launching the game from Vortex deploys REDmods first, and a separate REDmod deploy button is still there. Launching from Steam or a desktop shortcut after changing REDmods in Vortex skips that step. That explains a lot of “Vortex says it’s installed but nothing changed” posts.

Three ways to mod Cyberpunk 2077 and how each one breaks

Since 2.5, three separate mod pipelines run side by side. They break in different ways, and mixing them up sends you looking in the wrong place.

Nexus mods can’t reach consoles, and mod.io’s console-approved mods can’t use CET or RED4ext. On PC you can run all three at once, which brings its own conflicts (covered below).

Cyberpunk 2077 mods not working in Vortex

Most Vortex problems after a patch come from an outdated Vortex or Cyberpunk 2077 extension, or from forgetting to deploy. Update both first, then check deployment.

In Vortex, open Extensions and confirm that the Cyberpunk 2077 extension is enabled and current. Vortex usually updates extensions on its own, but a stalled update leaves you on an old one. Update Vortex itself from its Settings or from the Nexus Mods site. If Vortex suddenly refuses to start or install with a “.NET” error, install the .NET Desktop Runtime version named in the message (see the system checks). Recent Vortex releases moved to .NET 9, so an older runtime alone no longer satisfies them.

Deploy and purge

Vortex keeps mods in a staging folder and only writes them into the game folder when it deploys. If you enabled mods but never deployed, the game folder never changed.

1. Click Deploy Mods in the Mods tab after any change.
2. If files seem stuck (old versions still loading), click Purge Mods, then Deploy Mods again. Purge removes everything Vortex placed in the game folder, and the next deploy writes the current set fresh.
3. Launch the game from Vortex’s Dashboard so REDmods deploy too.

Vortex can’t see files you installed by hand. If you had a manual RED4ext or CET install before you switched to Vortex, delete it first, or the old copy can overwrite the new one.

Vortex can’t find the game

Vortex looks for the game in each store’s standard location. If you moved the install, use a non-default library, or bought the game on Battle.net after its November 10 release, set the path manually under Games > Cyberpunk 2077 > Manually set location and choose the folder that contains bin.

Download loops and failed installs

Some players report Vortex retrying a failed download over and over after the update. Two causes are common. First, a mod file was replaced on Nexus Mods while it sat in your download queue: cancel the download, delete the partial file in Downloads, and get the current file from the mod page. Second, Vortex lost its Nexus login: sign out and back in. If neither helps, report it in the Vortex Support forum on Nexus Mods, which is the official place for it.

CET overlay or CET mods not working

If the Cyber Engine Tweaks overlay never appears, your CET build is older than the 2.5 release, or it’s in the wrong folder. With CET 1.38.1 or newer in place, the game asks you on first launch to bind an overlay key. If you see that prompt, CET works.

Check these in order:

1. Version. Open bin\x64\plugins\cyber_engine_tweaks\cyber_engine_tweaks.log. The first lines show the CET version and whether it found a supported game version. A “game version not supported” line means the CET build is too old.
2. Folder. CET belongs in bin\x64\plugins\cyber_engine_tweaks. Extracting it one level too deep is a common mistake.
3. Key binding. If you missed or dismissed the first-launch prompt, the overlay key is unbound. The settings live in the CET folder, and once the overlay is open, its Bindings menu lets you set the key.
4. Runtime. If the log is empty or missing, reinstall the Visual C++ 2015-2022 x64 Redistributable.

The overlay can work while individual CET mods fail. Each CET mod writes its own log in its own folder under cyber_engine_tweaks\mods\, and CET’s console in the overlay shows Lua errors as they happen. A Lua error that names a game function usually means the mod needs its own 2.5 update.

Many in-game console commands and spawner-style mods, which players loosely call “hacks” or “cheats”, also run on CET. These are single-player tools, and they stop working for the same reason as every other CET mod: an outdated CET or an outdated mod.

Crashes after installing mods

When the game crashes tells you which layer is at fault. A crash before the main menu points at frameworks and plugins, and a crash while loading a save points at mods that change saved data. Random crashes during play usually come from one specific mod’s content, or from the hardware and driver problems in the system checks.

“Whoa! Cyberpunk 2077 has flatlined”

This window is CD PROJEKT RED’s crash reporter. It appears after any crash, whether or not mods are installed. The RED Modding wiki calls it the most common way the game crashes, and also notes that it tells you almost nothing about the cause. Sending the report to CD PROJEKT RED is fine, but it won’t diagnose your mods.

Use the moment of the crash instead:

1. Before the main menu: open red4ext\logs\red4ext.log and the plugin logs and read the last lines. Go back through Step 2.
2. Right after a redscript popup: fix the script mod named in r6\logs\redscript_rCURRENT.log first (Step 3).
3. On loading a save, or in one place in the world: follow the save and gameplay sections below and bisect.
4. With zero mods enabled: the cause is outside your mod list. Go through the system checks and verify the game files.

TweakDB missing or inaccessible memory errors

Players report this message in news coverage and on the Nexus forums: “Cyberpunk 2077 encountered an error caused by a corrupted or missing TweakDB file”. The TweakDB is the game’s database of items, stats and records, and TweakXL and REDmod both write a modded copy of it. The RED Modding wiki covers this under “missing tweakdb.bin or inaccessible memory” and links it to Cyber Engine Tweaks.

The fix is the same for both wordings:

1. Make sure CET is 1.38.1 or newer and TweakXL is 1.12.0. Old builds read the 2.5 TweakDB at the wrong place in memory.
2. Delete the files in r6\cache\modded. Nexus forum users report that deleting tweakdb.bin there alone was enough to get the game loading again. The cache is rebuilt the next time mods deploy.
3. Verify the game files in your store (Steam: Properties > Installed Files > Verify integrity. GOG Galaxy: Manage installation > Verify / Repair). This restores the original TweakDB files in r6\cache without touching your saves.
4. If a REDmod deploy prints “There was an error during tweak compilation”, the fault is in a REDmod-format tweak mod, not in TweakXL. Bisect your mods folder.

Crash before the main menu

This is the classic 2.5 framework crash. Go through Step 2 again, then check red4ext\logs\red4ext.log for the last plugin it tried to load. The plugin that loaded just before the log ends is the prime suspect. If the frameworks are correct and the game still crashes here, clear r6\cache\modded and verify files as described in the TweakDB section.

Crash when loading a save

Saves remember what mods added: items, appearances, quest states, vehicles. A save that references something from a mod you removed, or from a mod that broke on 2.5, can crash the game when it loads.

1. Try an older save, or one from before you changed mods.
2. If only one save crashes, put back the last mod you removed and load the save. Remove whatever that mod placed in your inventory or the world, then uninstall the mod again.
3. Test with a new game. If a new game loads and old saves don’t, the problem is in the save, not in your install.

Random crashes during gameplay

Crashes in one district, menu or activity point to a mod that touches that content. Bisect with that situation as your test. Also check whether the crash happens with zero mods. The 2.5 release had its own reported problems that mods didn’t cause, including crashes and a freezing mission outfit menu. If the crashes stay with a clean game, go back to the system checks: GPU driver, SSD install and, on Intel 13th and 14th gen, the BIOS microcode.

Log files: where they are and what to look for

Every framework writes a log, and the last lines before a crash usually name the problem. All paths are relative to the game folder (the one that contains bin).

How to read them:

• Read from the bottom. The last few lines before the log stops matter most. The rest is usually routine loading.
• Note the timestamp. A log with an old date means the framework didn’t run at all this session, and that is the clue.
• Look for mod names, not error codes. A line that names a .reds file, an .archive or a plugin folder tells you more than any hex address.
• Share logs, not screenshots. If you ask for help on the RED Modding Discord or a mod’s Nexus Posts tab, attach the log file. Helpers there ask for it first.

Console mods (PS5, Xbox Series X|S) not working

Update 2.5 added official mod support through mod.io in the in-game Mods menu. It covers PC, Mac, PlayStation 5, PS5 Pro and Xbox Series X|S. Reports disagree on whether Nintendo Switch 2 has it yet. On consoles, that menu is the only way to mod: you sign in with a free CD PROJEKT RED account linked to mod.io, subscribe to a mod, and restart.

CD PROJEKT RED’s patch notes state that “achievements and trophies cannot be earned while playing on console from a modded save file.” Saves made with mods enabled show a mod.io cog icon in the Load Game menu, and removing the mods afterwards doesn’t reliably make a save eligible again. Keep a separate unmodded save if you’re still hunting trophies.

Mod not listed

If a mod you saw on PC or on mod.io isn’t in the console list, it hasn’t been approved for consoles. Only mods tagged “Available on consoles” on mod.io appear on PS5 and Xbox. The catalogue was small at launch, and more mods are planned over time.

Mods that depend on Cyber Engine Tweaks, RED4ext, redscript or other PC frameworks can’t run on consoles at all, because consoles don’t allow injected code. A Nexus Mods page for a “console version” of a mod doesn’t change that. Nothing from Nexus can be installed on a PS5 or Xbox.

Mod installed but not active

1. Make sure the game is on 2.5 and you’re online when you open the Mods menu.
2. Check that the mod is both subscribed and enabled in the menu. Subscribing downloads it, but some mods still need enabling.
3. Restart the game completely after you subscribe. Mods don’t load into a running session.
4. Load a save and check whether the mod changes something you can actually see at that point in the game.

Sync and account-link errors

Most sync errors clear up once you relink your CD PROJEKT RED account at mod.io. Sign out of the Mods menu, unlink the account on the mod.io side, link it again, and sign back in. Then turn the console off completely instead of letting it go into rest mode, which clears cached session data. If a mod still won’t sync, unsubscribe, restart, and subscribe again.

In-game mod.io mods on PC

On PC, the in-game Mods menu runs alongside your Nexus mods. You manage mod.io mods inside the game, and they don’t appear in Vortex or Mod Organizer 2. Vortex mods don’t appear in the game’s menu either.

That separation causes one predictable problem: the same mod installed twice. If an author publishes on both Nexus Mods and mod.io, and you subscribe in-game while Vortex also deploys the Nexus copy, the two can conflict or load different versions. Pick one source per mod. Use Nexus for anything that needs CET, RED4ext, ArchiveXL or redscript, since your frameworks live there too. Use mod.io for simple, approved mods you want to sync and manage in game.

When you bisect a PC problem, disable your mod.io subscriptions too. They can cause the problem just like anything in Vortex.

Stop the game updating itself while you’re modded

The best way to avoid a repeat of 2.5 is to wait for your frameworks before you update the game. Each store handles this differently.

Nothing works: clean reset, wait, or stay on 2.31

If bisecting and logs haven’t found the cause, a clean reset rules out leftover files from years of mods. It takes about half an hour plus the download, and it gives you a known-good base to rebuild on.

1. Back up your saves folder (%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077).
2. In Vortex, Purge Mods. Mod Organizer 2 doesn’t need a purge, but disable everything.
3. Delete these from the game folder if they exist: archive\pc\mod, mods, r6\scripts, r6\tweaks, r6\cache\modded, red4ext, bin\x64\plugins, and any .dll and .asi files in bin\x64 that didn’t come with the game (for example version.dll or winmm.dll from loaders).
4. Verify or repair the game files in Steam, GOG Galaxy, Epic or Battle.net.
5. Launch without mods once and load a save to confirm the base game works. If it doesn’t, go through the system checks.
6. Install the frameworks from Step 2, launch, then add mods back in small groups.

If a mod you can’t do without still has no 2.5 build, you have three honest options, and each has a cost:

• Wait. Most popular mods updated within days of October 22, and the core frameworks were fixed by October 25. Check the mod’s Posts tab for an expected date.
• Play 2.5 without that mod, or with only a few mods. You get the new content (the Edgerunners 2 quest, dual-wielded pistols and revolvers, Glamdocs cyberware styling) without the broken mod.
• Stay on or roll back to 2.31. Users on the Nexus forums suggested this while ArchiveXL and RED4ext were still waiting for updates. It’s realistic on GOG Galaxy, which supports rollback. On Steam it depends on whether a previous-version branch is offered. The trade-offs are real: you lose the 2.5 content and fixes, your 2.5 saves may not load on 2.31, and new mod releases target 2.5, not your version.

Now that official framework builds are out, rolling back makes less sense every week. For most players, the better move is a clean 2.5 install with current frameworks, adding mods back as their authors update them. Check the weekly new Cyberpunk 2077 mods too, because many of those uploads are 2.5 updates of older favourites. Before the next patch, turn off automatic updates in your store.

FAQ

How do I get mods to work on Cyberpunk 2077?

On PC, run the system checks first: current Windows, GPU driver, the VC++ 2015-2022 x64 runtime and an SSD install. Then install the core frameworks your mods need (RED4ext, redscript, Cyber Engine Tweaks, ArchiveXL, TweakXL, Codeware) in versions that match your game version. Install mods with Vortex, Mod Organizer 2 or by hand into the right folders. On PS5 and Xbox Series X|S, use the in-game Mods menu with a CD PROJEKT RED account linked to mod.io.

Why aren’t my Cyberpunk 2077 mods working anymore?

Update 2.5 (October 22, 2026) changed the game code that the script frameworks hook into, so builds made for 2.31 crash or fail to load. Update every framework to its 2.5 release (RED4ext 1.31.0, ArchiveXL 1.28.0, TweakXL 1.12.0, Codeware 1.21.0, redscript 0.5.32, CET 1.38.1 or newer). Then update or disable mods with no release since 2.5.

Did the updated mods still break on the 2.5 patch?

Yes, in some setups. Usually one plugin in red4ext\plugins is still an old build, an unofficial 2.5 fix is mixed with official files, or one outdated redscript mod blocks every other script mod. Check the plugin folder dates and the redscript log.

What does “Whoa! Cyberpunk 2077 has flatlined” mean?

It’s the game’s crash reporter, and it appears after any crash. It doesn’t name the cause. Note when the crash happened (before the menu, on loading a save, during play), read the framework logs, and test once with zero mods. A crash without mods points to drivers, hardware or damaged game files rather than your mod list.

How do I fix the missing TweakDB file error?

Update CET and TweakXL to their 2.5 builds, delete the files in r6\cache\modded, and verify the game files in your store. Verifying restores the original TweakDB and doesn’t touch your saves. If the error comes up during a REDmod deploy, bisect the mods in your mods folder.

Why can’t I enable mods in the Cyberpunk launcher?

The toggle needs the free REDmod DLC, installed through Steam or GOG Galaxy. It also only controls REDmod-format mods in the mods folder. CET, RED4ext, redscript and legacy archive mods load without it, so a greyed-out toggle doesn’t affect them.

Why are my Cyberpunk hacks or cheats (CET) not working?

Single-player console commands and in-game spawners run through Cyber Engine Tweaks, and CET builds older than 1.38.0 don’t work on 2.5. Install 1.38.1 or newer, bind the overlay key when the game asks, and check the CET log if the overlay doesn’t open. An empty log usually means the VC++ runtime is missing.

Why are my Cyberpunk 2077 mods not showing up in game?

Usually the files are in the wrong folder (REDmod mods in archive\pc\mod, or nested subfolders). Other causes are a missing or outdated requirement such as ArchiveXL or Codeware, or REDmods that weren’t deployed because the game was launched outside Vortex or without the launcher toggle.

Why aren’t my Cyberpunk 2077 mods working in Vortex?

Update Vortex and its Cyberpunk 2077 extension, deploy after every change, and launch from Vortex so REDmods deploy. If files seem stale, purge and deploy again. If Vortex can’t find the game, which is common with Battle.net installs, set the game folder manually. A .NET startup error means you need the Desktop Runtime version that the message names.

Can random crashes be caused by my PC rather than mods?

Yes. Old GPU drivers, an HDD install and unstable Intel 13th or 14th gen desktop CPUs all cause crashes that look like mod faults. Intel’s microcode 0x12B, delivered through motherboard BIOS updates, prevents further Vmin Shift damage but doesn’t repair a chip that is already unstable. Test with zero mods to tell the two apart.

Can you use mods on Cyberpunk 2077 on PS5 or Xbox?

Yes, on PS5, PS5 Pro and Xbox Series X|S since Update 2.5, through the in-game Mods menu and mod.io. Only mods marked “Available on consoles” appear, and mods that need CET or RED4ext can’t run on consoles. PS4 and Xbox One don’t get 2.5 and have no mod support.

My mod isn’t in the in-game Mods list on PS5. Why?

It hasn’t been approved for consoles. Check its mod.io page for the “Available on consoles” tag. Mods from Nexus Mods can’t be installed on a PS5 at all.

Do mods disable achievements in Cyberpunk 2077?

On consoles, yes. The 2.5 patch notes state that trophies and achievements can’t be earned from a modded save, and those saves carry a mod.io cog icon. Removing mods later doesn’t reliably restore eligibility, so keep a clean save if trophies matter to you.

Which mods broke in Cyberpunk 2077 2.5?

Every RED4ext plugin built before 2.5 broke, including ArchiveXL 1.27.5 and TweakXL 1.11.5. CET before 1.38.0 broke too, along with any script mod that called code 2.5 changed. Some idle-animation and eye mods were reported broken after hotfix 2.500.200. Pure texture and mesh replacers mostly survived unless 2.5 changed the files they replace.

After the update my textures broke. What fixes that?

Update ArchiveXL to 1.28.0 and make sure RED4ext is 1.31.0 or newer. Then update the texture, clothing or body mod itself, plus any body framework it depends on. If two archive mods replace the same file, the one that sorts first alphabetically in archive\pc\mod wins.

Should I downgrade Cyberpunk 2077 to 2.31 to keep my mods?

Only if a mod you can’t play without has no 2.5 build and isn’t expected to get one soon. Official 2.5 builds of every core framework are out as of November 2026, so for most players a clean 2.5 setup is the better long-term choice. If you do roll back, GOG Galaxy makes it easiest, and keep your 2.31 saves separate from your 2.5 saves.

What changed

• Nov 13, 2026 First published.

About the article

NA

Written by Nico Albrecht

Nico covers RPG and action game mods, Bethesda games and the weekly trending mod roundups. He pays close attention to requirements and load order, so a mod list is something you can install without breaking your save.

• Fact-checked by Hollis Tremaine against the sources listed below before publication.
• Published November 13, 2026

Sources (8)

1. Patch 2.5 Notes for Modders (Unofficial Fix Retired) at Cyberpunk 2077 Nexus (nexusmods.com)
2. All RED4Ext plugins broken in CP2077 2.5 "Edgerunners II" update · Issue #153 · wopss/RED4ext (github.com)
3. Codeware at Cyberpunk 2077 Nexus (nexusmods.com)
4. ArchiveXL at Cyberpunk 2077 Nexus (nexusmods.com)
5. Releases · wopss/RED4ext · GitHub (github.com)
6. RED4ext at Cyberpunk 2077 Nexus (nexusmods.com)
7. Release Game version 2.5 · maximegmd/CyberEngineTweaks (github.com)
8. Cyber Engine Tweaks at Cyberpunk 2077 Nexus (nexusmods.com)

Spotted an error? Tell us