Flatlined after an update? — Boot clean. Keep your files. | Cyberpunk 2077

Mods have multiple dependencies. After a patch, one outdated framework can stop the game before the main menu appears. The safe approach is to boot vanilla first and bring mods back one at a time.

01 / INTERACTIVE QUICK TOOL

Big Six mod dependency checklist

Reference release snapshot seen in October 2026; check the maintainers for latest patch support instead of treating these as universal minimums.

Cyber Engine TweaksRecent release: 1.37.1 · check game build compatibility RED4extRecent release: 1.30.0 · check game build compatibility ArchiveXLRecent release: 1.27.4 · check game build compatibility TweakXLRecent release: 1.11.4 · check game build compatibility redscriptRecent release: 0.5.31 · check game build compatibility CodewareRecent release: 1.20.5 · check game build compatibility

Compatibility is build-specific; versions shown are not guaranteed minimum requirements or substitutes for the developer’s release notes.

02 / EASY STEPS

Do this in order.

Short, practical steps. Check each result before moving on.

Back up saves and mod lists.

Copy your ManualSave folder and export your Vortex/MO2 profile if applicable.

Disable automatic mod deployment.

Turn off your mod manager and close the game before touching any mod hooks.

Run a reversible vanilla test.

Use the quarantine script below beside Cyberpunk2077.exe root only after reading it. It MOVES specific add-ons; it does not delete original game archives.

Verify game files and launch.

If vanilla works, you know a mod or dependency is likely responsible.

Restore frameworks one by one.

Start with RED4ext, redscript, CET, ArchiveXL/TweakXL and Codeware. Test between each stage.

03 / WHY THIS WORKS

One-click mod-hook quarantine script (reversible)

Save the following as test-vanilla-clean.bat in your Cyberpunk 2077 installation root (where the bin folder lives). Read the text before running. It moves only selected mod-hook folders into a dated quarantine directory beside the game, preserving files for restoration. It does not touch archive\pc\content or your saves.

@echo off
setlocal
cd /d "%~dp0"
if not exist "bin\x64\Cyberpunk2077.exe" (
  echo Place this file in the Cyberpunk 2077 install root.
  pause
  exit /b 1
)
set "SAFE=WB_mod_quarantine_%RANDOM%%RANDOM%"
mkdir "%SAFE%"
if exist "bin\x64\plugins" move "bin\x64\plugins" "%SAFE%\plugins"
if exist "red4ext\plugins" move "red4ext\plugins" "%SAFE%\red4ext_plugins"
if exist "r6\scripts" move "r6\scripts" "%SAFE%\scripts"
if exist "r6\tweaks" move "r6\tweaks" "%SAFE%\tweaks"
echo Saved moved folders in %SAFE%.
echo No base-game archive files were deleted.
pause

Additional mod loaders in archive/pc/mod or mods/ may need disabling in your mod manager. Restore moved folders manually after testing. Do not run while the game or mod manager is open.

04 / FAQ

Quick questions.

Are these six versions required for every mod?

No. They are recent release references. Dependencies differ by mod and exact game build.

Will the script remove my 65 GB base-game archives?

No. The script targets only selected mod hook folders and MOVES them to a quarantine folder, not game archives.

Should I delete all mods to troubleshoot flatlining?

No. Back up, disable temporarily, boot vanilla, and isolate the incompatible dependency.

05 / REFERENCE CHECK

Sources and version notes.

Game patches, mod versions and tool syntax can change. Links below let you check the latest publisher or maintainer guidance. Illustrative charts and examples are labeled rather than presented as measurements.

Original topic-specific cinematic hero artwork; not a gameplay screenshot.