This document reproduces the troubleshooting flow from the original interactive guide. All links and targets are preserved. Use this as a reference for steps to diagnose and fix mod-related problems.
Title: What platform do you have the game from?
Description: This is important information if you need help.
Options:
- Steam → uptodate_q_1
- Epic → uptodate_q_1
- GoG → uptodate_q_1
- Not allowed to say → pirate
Title: Is your game up-to-date?
Description:
The good news is, as long as your game is a legal copy, you can mod it.
Do you have the most recent version of Cyberpunk 2077?
Options:
- Yes → is_your_game_crashing
- No → update_a_1
Title: You need to update your game.
Description:
The Cyberpunk 2077 Community Modding Server only supports the most recent version of the game. If you want support, please update!
Options:
- OK! → is_your_game_crashing
- I can't update → pirate
Title: Are your core mods up-to-date?
Description:
All the mods listed below must be on the most recent version
You also should update these mods if you have them
Options:
- Yes → is_your_game_crashing
- No → update_dependencies_start
Title: Let's update everything!
Description:
It's likely that the problem doesn't lie with Cyberpunk, but actually comes from something else. We'll now update everything that could be the problem.
Options:
- I did that already! → update_core_mods
- I want to reinstall the game now! → mod_remover
- OK! → update_visualc
Title: Update VisualC Redistributable
Description:
- Download the latest VisualC Redistributable for 64-bit (x64) from Microsoft
- Run the setup
- If you already have it installed, repair your installation
- Restart your computer (this step is not optional)
Does the game start now?
Options:
- Yes → success
- No → update_dependencies_02
Title: Repair VisualC Redistributable
Description: If you did not reboot your computer, do it now.
You can skip this step if you already repaired an existing install of VisualC.
- Run the setup again
- Repair the existing installation
- Restart your computer (this step is not optional)
Does the game start now?
Options:
- Yes → success
- No → update_dependencies_03
- Actually, I came here from RED4ext... → crashing_red4ext_02
Title: Install .NET Desktop Runtime
Description: Make sure that you have the most recent version of the .NET Desktop Runtime installed.
Does the game start now?
Options:
- Yes → success
- No → update_dependencies_04
Title: Update Windows
Description: Make sure that your Windows is up-to-date. You don't need to install Windows 11 for this, but make sure that you have all updates installed. Reboot the computer if Windows wants you to.
Does the game start now?
Options:
- Yes → success
- No → update_dependencies_05
Title: Update your graphics driver
Description: Since VisualC and Windows are up-to-date, this only leaves your GPU driver. Download and install the latest version:
Reboot your computer if the setup asks you to.
Does the game start now?
Options:
- Yes → success
- No → update_dependencies_06
Title: Do a clean install of your graphics driver
Description: Maybe your graphics driver has gotten corrupted. Do a clean install.
- For NVIDIA, download and run Display Driver Uninstaller first
- For AMD, you can use their Cleanup Utility
Then, reinstall the driver you updated in the previous step.
Does your game start now?
Options:
- Yes → success
- No → uptodate_q_1
- For NVIDIA user → update_dependencies_NVIDIA
Title: Try rolling back your driver version
Description: NVIDIA sometimes introduces issues with their drivers that cause the game to crash. Repeat the instructions from the previous step, but install one of these drivers:
Does your game start now?
Options:
- Yes → success
- No → uptodate_q_1
Title: Is your game crashing?
Options:
- Yes → crashing_q_2
- No, and I just want this to work! → mod_remover
- No → misc_start
Title: When does the game crash?
Description: We can tell what the problem is by checking when the game crashes. Which of the following options describes your crash?
Options:
- It doesn't even start → crashing_cybercmd
- Before the menu → crashing_cet_01
- When loading a savegame → crashing_world_start
- At a specific point → crashing_script_mod_start
- At a random point → crashing_random_start
Title: Linux mod installs
Description: For Linux, there are a few specific steps that you have to follow. Follow this guide on our wiki. Does the problem go away?
Options:
- Yes → crashing_q_2
- I'm not on Linux → crashing_q_2
- No → is_your_game_crashing
Title: Do you have CyberCMD installed?
Description: If you have the mod CyberCMD installed, remove it now. It does the same thing as Red4Ext, which you should install instead.
Can you start the game now?
Options:
- Yes! → success
- No → crashing_errormsg
- I don't have it → crashing_errormsg
Title: Do you see an error message?
Description: Do you see an error message, and does it contain... (please see options)
Options:
- No error message → crashing_red4ext_01
- Not listed → crashing_red4ext_01
- "
could not move 'xxx' to '...\\modded\\tweakdb_ep1.bin'" → delete_the_cache - Red4ext could not be loaded → update_visualc
- Redscript compilation failed → delete_the_cache
- XML document parsed with errors → crashing_xml_document_errors
- something about files → misc_something_something_files
Title: XML document parsed with errors
Description: Does the error message mention the file r6/config/inputUserMappings.xml?
Options:
- Yes → input_loader_error
Title: Input Loader
Description: This error is caused by Input Loader.
Options:
- OK, what do I do now? → broken_mod
Title: Unknown mod
Description: We're not sure which mod is the cause of your error, or if it's a base game problem. Delete the offending file, and verify your game files.
Does the error go away?
Options:
- Yes → success
- No, and I'm done with this shit → mod_remover
- No → is_your_game_crashing
Title: Redscript compilation failed
Description: You have cleared your cache and verified files, but the game is still crashing. Let's try updating redscript.
Is your problem gone?
Options:
- Yes → success
- No → crashing_redscript_compilation_failed_02
Title: Redscript compilation failed
Description: Does the popup include a list of mods that cause the error?
Options:
- Yes → crashing_redscript_compilation_failed_03
- No → crashing_redscript_compilation_failed_04
Title: This is caused by errors in...
Description: The error names a number of mods. Let's check each of them - note them down.
Options:
- OK → broken_mod
- I already have → crashing_redscript_compilation_failed_04
Title: You can't get rid of the errors
Description: You verified everything that could be the problem, but the error doesn't go away. Here's what you can do now:
Options:
- Update the core mods → update_core_mods
- Nuke your mods and start over → mod_remover
Title: Delete the cache and verify your game files
Description:
- Go to your Cyberpunk 2077
- Find the subfolder
r6\cache - Delete the entire folder.
- Now, verify your game files.
Does the game start now?
Options:
- Yes → success
- No (I have a redscript error) → crashing_redscript_compilation_failed
- No → crashing_q_2
Title: Red4Ext is not working
Description: You have a problem with Red4Ext (or one of its dependencies). Let's update them:
Does that make the problem go away?
Options:
- Yes! → success
- No... → update_visualc
Title: Red4Ext is not working
Description: You have a problem with Red4Ext (or one of its dependencies), and neither updating them nor updating VisualC fixed it. Now it's time to check the log files.
- Go to your Cyberpunk 2077
- Go to the subfolder
red4ext\logs - Find the most recently changed file, and open it with a text editor such as Notepad++
- Look out for lines with
[error], then try to resolve the problems.
If you need help, you can check this wiki page or find us on Discord in the mod-troubleshooting channel.
Options:
- OK! → success
Title: Can you start a new game?
Description: Instead of loading an existing save, can you start a new game?
Options:
- Yes → crashing_weather_mod_q
- No → crashing_archive_mod
Title: Is it a weather mod?
Description: Did you recently install any mods that change or influence the weather?
Options:
- Yes → crashing_weather_mod_a
- No → crashing_archive_mod
Title: 404 - Weather not found
Description: The game is trying to access a weather that doesn't exist, and is crashing. Reinstall the weather mod from Nexus and follow its uninstall instructions, then remove it again.
Can you load your save now?
Options:
- Yes! → success
- No → crashing_archive_mod
Title: A broken item
Description: The game is trying to load a broken item and is crashing when trying to spawn it into the world. In the next step, we'll find out which item it is. You need to examine the following folders inside your Cyberpunk 2077:
\archive\pc\mod\mods(it can be empty)
Options:
- OK! → bisect_known_folder_start
Title: You have a broken script mod
Description: At some point during your gameplay, a script mod is trying to do something that makes the game crash. Unfortunately, there won't be any log files to help you.
In the next step, we'll find out which script mod it is. You need to examine the following folders inside your Cyberpunk 2077:
\r6\scripts\bin\x64\plugins\cyber_engine_tweaks\mods
Options:
- OK! → bisect_known_folder_start
Title: Do you have Material Texture Override installed?
Description: Do you have the mod Material Texture Override installed?
Options:
- Yes → crashing_random_mto
- No → crashing_random_01
Title: ... in the inventory?
Description: Do you crash while managing your inventory?
Options:
- Yes → crashing_random_crowd_scanner_q
- No → crashing_random_03
Title: We can't narrow down the problem
Description: It's really difficult to tell what kind of mod is causing the problem. You have two options now:
Options:
- Bisect → bisect_start
- Nuke mods and start clean → mod_remover
Title: Uninstall MTO
Description: Material Texture forces the game to regenerate its materials rather than relying on cached files. That's a requirement for any mods that change base game materials, but unfortunately, it can expose bugs that CDPR never fixed.
Remove Material Texture Override and see if the crash goes away.
Options:
- It's gone! → success
- It's still there → crashing_random_03
Title: Do you have these mods installed?
Description: Do you have these mods installed?
Options:
- Yes → crashing_random_crowd_scanner_a
- No → crashing_random_03
Title: Uninstall either or both of those mods
Description: These two mods do not play nice with each other — try uninstalling one or both.
Does this resolve your problem?
Options:
- Yes! → success
- No → crashing_random_03
Title: You have a problem with a CET mod
Description: Your problem sits in the following folder inside your Cyberpunk 2077: bin\x64\plugins\cyber_engine_tweaks\mods Open Windows Explorer and rename the folder to mods_. Does your game start now?
If you need help, you can check this wiki page or find us on Discord in the mod-troubleshooting channel.
Options:
- Yes! → bisect_cet_00
- No... → crashing_cet_not_bisect
Title: You have a different problem with a plugin
Description: Navigate three levels up until you are in the folder bin\x64 and rename the entire folder plugins to plugins_. Does your game start now?
Options:
- Yes! → crashing_reinstall_cet
- No... → update_dependencies_start
Title: Reinstall CET
Description: Do a clean install of Cyber Engine Tweaks:
- If you are using a mod manager, make sure to delete the mod there
- Download the mod from Nexus
- Install it, and start the game. Does it work?
Options:
- Yes! → crashing_reinstall_cet_move_mods
- No... → mod_remover
Title: Move the mods from your backup
Description: Now that CET is starting again, let's get your mods back.
- Go to your Cyberpunk 2077
- From the old folder
plugins_, move themods_folder to your new CET install under\bin\x64\plugins\cyber_engine_tweaks - You can delete
plugins_now - Rename the folder
mods_in CET's directory tomodsand start the game. Does it work?
Options:
- Yes! → success
- No... → bisect_cet_00
Title: Your game is really really fucked
Description: Don't worry, all is not lost. But instead of individual troubleshooting, it is faster to start from a clean game:
- Download Mod Remover from Nexus
- Move the .bat or .exe file to your game directory
- If you are using MO2: Register the .bat or .exe as a tool in the mod manager
- Run the script
- Verify your game files
Does the game start now?
Options:
- Yes! → reinstalling_mods_start
- No... → update_dependencies_start
- That's it, I'm done → success_but_no
Title: Reinstalling mods
Description: STOP! Do not just put your mods back! If you do that, you will be exactly where you were before running mod remover: with a broken game.
Install only the core mods, and make sure that they are on the most recent version (re-download if necessary):
Does the game start with only core mods installed?
Options:
- Yes! → reinstalling_mods_01
- No... → update_dependencies_start
Title: Reinstalling mods, step 2
Description: Now you can restore folders from your backup, one after the other:
- Copy a folder in the backup directory, e.g.
archive(do not delete it) - Paste it into the Cyberpunk 2077 game directory
- Check if the game still starts
At which folder does your game start crashing again?
Options:
- None! → success
- archive → reinstalling_mods_archive
Title: Your problem is an .archive mod
Description: The folder you will have to check is archive/pc/mod. Browse to archive/pc, and select it. Then, proceed to the next page.
Options:
- OK! → bisect_known_folder_start
Title: How to quickly find the broken mod
Description: Bisect is a binary search and the fastest way to find your broken mod. You don't know which folder it is, so you'll have to do all 4 of them. You can find step-by-step instructions on the wiki page. If you are a visual learner, you will find a short video at the end of the section.
You have to examine the following folders inside your Cyberpunk 2077:
archive\pc\modr6\scriptsr6\tweaksbin\x64\plugins\cyber_engine_tweaks\mods
Options:
- Sounds scary, but I'll do it → bisect_known_folder_start
- I just want to start over clean → mod_remover
Title: How to quickly find the broken mod
Description:
- Go to your Cyberpunk 2077
- Create a new empty folder
bin\x64\plugins\cyber_engine_tweaks\mods - Open the folder
mods_and move half of the files and folders tomods
Does the game still start?
Options:
- Yes! → bisect_cet_01
- No... → crashing_cet_not_bisect
Title: Finding the broken CET mod
Description: Go to your Cyberpunk 2077 The folder you need to examine is bin\x64\plugins\cyber_engine_tweaks\mods. Proceed to the next step! (You have already completed item 1, so start at 2)
Options:
- OK → bisect_known_folder_start
Title: Let's get those mods examined
Description: You have found out which folder holds the containing mod. If you don't, you can check this wiki page.
Use the stepper below to perform the bisect (binary search) in the folder you identified.
{% stepper %} {% step %}
Re-name it by adding a _ to its name (e.g. mods => mods_). This is your backup.
{% endstep %}
{% step %}
Create a new empty folder with the old name. This is the game folder. {% endstep %}
{% step %}
Move half of the folder content (files and folders) from the backup to the game folder.
Is your problem back? {% endstep %} {% endstepper %}
Options:
- No! → bisect_not_these_mods
- Yes... → bisect_mods_found_01
Title: These mods are okay
Description: Now we know which mods aren't the problem. Open your backup (with the _), and once again copy half of the files and folders to your game folder.
Is your problem back?
Options:
- No... → bisect_mods_found_01
- Yes! → bisect_not_these_mods
- I know which mod it is! → bisect_found_the_mod
Title: These mods are okay
Description: The mods you just copied are not the problem. Go to your backup folder (with the _).
- If you moved mods back out of the game dir: Copy half of those
- If you didn't move mods back: Copy half of the total remaining mods
Is your problem back?
Options:
- No... → bisect_mods_found_01
- Yes! → bisect_not_these_mods
- I know which mod it is! → bisect_found_the_mod
Title: We're getting closer!
Description: You just copied a bunch of mods from your backup dir to the game dir, and now your problem is back. That means that the broken mod was part of the batch you just copied. Move half of the folder content you just copied into the backup folder again.
Is your problem still there?
Options:
- Yes... → bisect_mods_found_02
- No! → bisect_mods_found_02
- I know which mod it is! → bisect_found_the_mod
Title: These weren't it
Description: You just moved half of a batch back out of the game folder, and your problem is still there → the batch you copied were okay. From the remaining half, take half of the mods again, and move them to the backup folder.
Is your problem still there?
Options:
- Yes... → bisect_mods_found_02
- No! → bisect_mods_found_03
- I know which mod it is! → bisect_found_the_mod
Title: The mod is in those files!
Description: You just moved a batch of mods out of the game folder into the backup folder (with the _), and your problem went away. That means your problem child is one of the mods you just moved. Take half of them and put them back into the game folder.
Is your problem back?
Options:
- Yes... → bisect_mods_found_02
- No! → bisect_mods_found_03
- I know which mod it is! → bisect_found_the_mod
Title: You found the culprit!
Description: Congratulations! You found out which mod it is! Hit up its Nexus page and check the following:
- Can you update it? If yes, do so
- Is there a comment page? If yes, maybe it is no longer compatible with the current patch.
Options:
- Cool! → success
- That doesn't help! → broken_mod
Title: A broken mod
Description: You have a mod, but it's broken. What do we do now?
Options:
- Check its dependencies → misc_dependencies
- Did you update recently? → outdated_mod
- I will play without it :( → success_but_no
Title: Is the mod outdated?
Description: If the mod stopped working after you updated your game, it's possible that it is simply not up-to-date yet. Here are your options:
- Play without it
- Wait for the mod author to update it (if you ask, please ask politely)
- Try and fix the mod yourself (this can be hard, but you are welcome on our discord in
#mod-dev-chat)!
The safest way to find out is to...
Options:
- read the fucking manual → rtfm
- Actually, I have a redscript error → crashing_redscript_compilation_failed_03
- I will play without it :( → success_but_no
Title: Read the fucking manual
Description: Open the mod's Nexus page. Do the following things:
- Read the mod description. We get it, reading is hard, but somebody wrote all that text just for you!
- Open the comments tab. Is there a sticky comment? Read it.
- Check the first two comment pages. Are a lot of people reporting the same bug? Is there a solution that you can try?
- Is there a bug section? Check it out. If there are no bugs, you could file one.
Options:
- There was no solution ;( → success_but_no
- I'll just play without the mod → success
Title: Are you on Linux?
Description: Your game is not crashing, and you have a different issue. The first question is - are you on Linux?
Options:
- Yes → linux_01
- No → misc_q_01
Title: Is it an inactive mod?
Description: Is your problem that a mod isn't working?
Options:
- yes → misc_mod_not_working
- no → misc_q_02
- I don't know what that is → misc_q_02
Title: Do you have any sp0 mods?
Description: Do you have any mods by Nexus user spawn0000 (also known as sp0)?
Options:
- Yes → misc_uninstall_sp0
- Of course not! → misc_skip_loading_screen_question
Title: Are you stuck in the loading screen?
Description: Are you stuck in the initial loading screen before the menu?
Options:
- Yes → input_loader_error
- No → unspecified_problem
Title: Uninstall sp0 mods
Description: The modder uses outdated technologies and is infamous for causing compatibility issues. He is the only person who can change that, but he is not interested. Your best option at this point is to uninstall his mods and find a better body. You can find a list on this wiki page (scroll down a little)
Does that make your problem go away?
Options:
- Yes → success
- No → unspecified_problem
- I don't want to uninstall my cement tits! → success_but_no
Title: You have a problem with file permissions
Description: Please check the troubleshooting guide, section "Something something files", and follow the instructions.
Does this make your problem go away?
Options:
- yes → success
- no → crashing_errormsg
Title: An inactive mod
Description: You're not on Linux and one of your mods isn't working. Are you using the mod manager mo2?
Options:
- yes → mo2_01
- no → misc_dependencies
Title: Install the mod's dependencies
Description: You need to install all of the mod's dependencies, but here's the catch: you need to install their dependencies as well. Check this wiki page for more intel.
Does the problem go away?
Options:
- yes → success
- no → broken_mod
Title: You're using mo2
Description: When modding with mo2, you need to install the following mods manually:
Does that make your problem go away?
Options:
- Yes → success
- no → mo2_02
Title: The problem persists
Description: Since mo2 was originally intended for Bethesda games, we don't know terribly much about it. You can find everything that we do know on our wiki page. If that doesn't help, you can hit up their Discord.
Options:
- OK :/ → success_but_no
Title: You are modding on Linux
Description: If you are on Linux, there are a few specific steps that you have to follow - see this guide on our wiki. Does the problem go away?
Options:
- Yes → success
- No → linux_02
Title: The Linux guide didn't help you
Description: Double-check the troubleshooting section. If the steps listed there don't help you, then it's likely that we can't either. You're nonetheless welcome to ask for help on our discord in the #mod-troubleshooting channel, but you're probably better-off if you find a Linux-specific community.
Options:
- OK → success
Title: Progress!
Description: Awesome! You solved a problem! Does your game start now?
Options:
- Yes! → sponsors
- No → q_bisect_in_progress
- I'll just reinstall my game → mod_remover
Title: Are you bisecting?
Description: Are you currently bisecting your mods?
Options:
- Yes → bisect_mods_found_01
- No → start
Title: Sorry!
Description: It seems we're at the end of our options, choom. Sorry! Feel free to ask for help on our discord in the #mod-troubleshooting channel, though.
Options:
- OK! → sponsors
Title: The problem is in another castle
Description: It seems that you have a problem that the interactive troubleshooter does not cover yet. Please check our troubleshooting wiki page. You can use your browser's search function (Ctrl+F), or check for your problem in the table of contents or the list at the start of the page.
Options:
- Fuck this, I'm reinstalling the game → mod_remover
- OK! → sponsors
Title: Check out our sponsors
Description: The Cyberpunk 2077 modding community wishes you a good trip to Night City! There are many great things you can do:
- Shoot gonks! Check the vending machines of our sponsor Budget Arms for some cheap iron!
- Kiss joytoys! Head to Jig Jig Street, live your best life, and scan the QR code at Wakako's pachinko parlor to enter a free giveaway!
- Get run over by cars: Just stand on a road somewhere and go flying. Whee! Quality medical care at Viktor's Vector in Watson!
Disclaimer: Johnny Silverhand has many suggestions as well. We suggest to ignore his advice, and won't be liable for any damage of property or persons if you don't.
Title: We won't help you
Hide back: true
Description: You can read the full reasons here. Feel free to peruse the troubleshooting guide, but we won't help you until you buy your game.
You can get it here:
GOG.com (CD Projekt)
Buying Cyberpunk 2077 from Good Old Games (GOG.com) directly supports CD Projekt RED, as it is their own platform!
Steam (Valve)
Epic Games Store (Epic Games)
Options:
- OK, I bought the game! → start
- I can't afford the game! → sucks_to_be_poor
- Fuck you, no! → fuck_off
Title: Sorry, choomba
Description: We get it, it sucks to be poor, but pirated games do not mod well. If you don't care for an explanation, we can't help you any further.
Options:
- OK ;( → sponsors
Title: We appreciate your business
Description: The Cyberpunk 2077 Modding Community Support Team (which consists exclusively of unpaid volunteers) is glad that the interactive troubleshooter could identify your problem. Please do not ask for help on Discord, as piracy violates the TOS and we'd like to keep our server.
Options:
- OK → sponsors
Notes:
- The bisect procedure (binary search) was converted into a stepper for clarity.
- All links and targets are preserved as in the original source.
- If you want this converted into actual interactive GitBook pages or into a single flow with buttons, tell me which format you want (individual pages, one long page, or interactive logic), and I can reformat it accordingly.