🆘
Troubleshooting
If your mods are causing trouble, here's what you can do
dThis page contains troubleshooting information for people who are using mods rather than making mods. You will find step-by-step guides, grouped by different problems.
Did you know? You can us your browser's search function (Ctrl+F) to quickly find your problem on the page – simply type a word from your error message.
Before you start debugging, make sure that
- your graphics driver is up-to-date
If you are on RED4Ext >= 1.13, make sure to uninstall cybercmd!
This section aims to give you a quick overview. If your exact problem isn't listed here, please look through the different sections below and try anything that looks promising.
- A mod is causing problems, and you have no idea which:
- Deleting user settings
If you can't play because the game is crashing, this section will point you towards the right troubleshooting steps in the guide below.
If you're trying to start your game, but it never even launches, this is the right section for you. Otherwise:
If you think that your error is file-related, you can check the section "Something something files" or use your browser's search function (
Ctrl+F) to search this page for your error.Your problem lies with either red4ext or redscript. Find the section "Your game isn't starting" below and follow the steps for your error message.
If you're starting the game, but never make it to the in-game menu, this is the right section for you.
Otherwise:
Cyberpunk 2077 encountered an error caused by a corrupted or missing TweakDB file and will now be forced to close
If you run into the error above, or if the game complains about attempting to read inaccessible memory, do this:
- 1.Go to your Cyberpunk directory and find the folder
r6\cache. - 2.Find the file
tweakDB.binand copy it (Ctrl+C) - 3.
In r6\cache, browse to the foldermodded(create it if it doesn't exist) - 4.paste
tweakDB.binhere (Ctrl+V) - 5.If asked to overwrite, select
Yes - 6.If you have Phantom Liberty, repeat the process with
tweakdb_ep1.bin
Your problem most likely related to Cyber Engine Tweaks. To find out how to troubleshoot it, check the "disable CET" section.
If you can make it to the menu but crash out when you're loading a save or starting a new game, this is the right section for you.
Otherwise:
Most likely, you have an issue with an .archive mod. Here's what you can do:
- 1.To rule out that it's a save game problem (those are extremely rare), start a new game.
- 2.
If that doesn't solve your problem, or if the issue is save-game related, feel free to browse around some more.
You only need to read this if you can start a new game without mods, but crash on loading a previous save game. For any other problem, please see the corresponding section(s).
Some mods store data in save files. Removing those mods may (but doesn't have to) lead to your save game crashing until you install them again.
At the current time (09/2023, before PL), that has been confirmed to affect those mods:
- Immersive Rippers - see the expandable list below for uninstall instructions, or check the mod's pinned post on Nexus
Error reason: Unhandled exception Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005) Message: The thread attempted to read inaccessible data at 0x10. File: <Unknown>(0)- 1.
- 2.
- 3.
- 4.Load into your previously-crashing save
- 5.Move at least 100m away from the closest ripper
- 6.Copy the following commands and run them in the CET-Console:
Game.SetDebugFact("bls_ina_se1_ripperdoc_01_default_on", 0)
Game.SetDebugFact("cct_dtn_ripdoc_01_default_on", 0)
Game.SetDebugFact("hey_spr_ripperdoc_01_default_on", 0)
Game.SetDebugFact("pac_wwd_ripdoc_01_default_on", 0)
Game.SetDebugFact("std_arr_ripperdoc_01_default_on", 0)
Game.SetDebugFact("std_rcr_ripperdoc_01_default_on", 0)
Game.SetDebugFact("wat_kab_ripperdoc_01_default_on", 0)
Game.SetDebugFact("wat_kab_ripperdoc_03_default_on", 0)
Game.SetDebugFact("wat_nid_ripperdoc_01_default_on", 0)
Game.SetDebugFact("wbr_hil_ripdoc_01_default_on", 0)
Game.SetDebugFact("wbr_jpn_ripdoc_01_default_on", 0)
Game.SetDebugFact("wbr_jpn_ripdoc_02_default_on", 0)
- 7.Save your game in a new slot and close it
- 8.Remove Immersive Rippers .archive file("Cyberpunk 2077\archive\pc\mod\ImmersiveRippers.archive")
- 9.Save your game again and remove all mods used in version 1.63
- 10.OPTIONAL: Load the save in vanilla 1.63, it should work there too.
- 11.Download the newest version of Cyberpunk2077! The clean created save should work for vanilla and modded instances of the game.
If you are experiencing this issue with a mod that is not on this list, please check Broken mods: How to help
This section tells you how to deal with crashes during gameplay.
Kiroshi Crowd Scanner and Tooltip Fixer do not play together (source, discord). Uninstall one of them.
If you can make it crash reliably
You're lucky, because it means that you can systematically troubleshoot. Go to the bisect section; start with .archive mods, but if that doesn't fix it, do the other folders as well.
If you can't
Occasionally, crashes can be triggered by cross-platform saves. You can disable them in the main menu under Gameplay -> Miscellaneous
… that puts you in the same boat as the rest of us: most veteran players live with occasional crashes, especially while tabbing out and back in under certain circumstances.
That being said, if the crashes exceed what you're willing to live with, you'll have to find out a way to improve it, but your options are thin on the ground. Depending on how long it takes for the crash to occur, you might try
- temporarily disabling certain types of mod to home in on the cause (see the bisect section for an overviev)
Best of luck!
When your game doesn't even start up, either of these frameworks isn't working properly. Below, you can find a list of the most common error messages with steps to resolve them.
Cyberpunk 2077 encountered an error caused by a corrupt or missing script file and will now be forced to close. Please verify...
You have a problem with Red4ext.
If you are using RED4ext >= 1.13, uninstall cybercmd if you have it — it's no longer necessary and can cause false positives.
The first step whenever you run into this error is deleting the folder
r6/cache and verifying your game files.If that doesn't help, it's time for more detailed troubleshooting:
- If you are on Linux, make sure to double-check the launch options, as Steam sometimes resets these between updates
- if you don't have red4ext/logs/red4ext.log, then RED4ext doesn't work, you have to update / fix RED4ext
- if you have red4ext/logs/red4ext.log, then look inside, it will tell you which mods aren't compatible with the current game patch and may be the cause of this issue
- if that doesn't help, go to 3. Reset Redscript in the corresponding section (you will need to verify your game files).
If that doesn't solve your problem, you can
Cyberpunk 2077 encountered an error caused by corrupted or missing archives and and will now be forced to close. Please verify...
One of the .archive files in your folder is broken. To find out which one, try the bisect approach, starting with the first two folders.
There are various non-mod-related reasons why the game couldn't be starting. If you have followed these steps and they haven't gotten you anywhere, check the errors in this section:
Other than that, there are general troubleshooting steps, because missing Windows stuff can make Cyberpunk go brr. Make sure that
- your graphics driver is up-to-date
Also, try starting the game without Reshade to rule it out as a source of crashes (this happened after the DLSS patch) and temporarily disable your antivirus.
There is such a thing as too many mods which are making the game crash. This number seems pretty random, but generally doesn't start below ~460.
To fix this, you need to disable analysis in the settings:
This is not a Cyberpunk error!
Message: Failed to initialize scripts data!
File: E:\R6.Release\dev\src\common\engine\src\baseEngineInit.cpp(1019)
Check your NVidia Control Panel panel. If power saving options are enabled, turn them off:
If you don't, check for other power config options in your operating system.
The error below is partial to Steam:
Cyberpunk 2077 encountered an error caused by corrupted or incomplete game data
There are two potential fixes:
Before trying to implement any of the other solutions, configure the
REDprelauncher.exe in the Cyberpunk root directory to always run as administrator. - Right-click on the file and select
Properties - Switch to the
Compatibilitytab - Check the box
Run this program as an administrator
The second reason might be that your antivirus fucks with your game files in a way that the game can't cope with.
Try the following steps:
- Turn off your antivirus and your firewall - anything that counts as "System Protection".
- Yes, that includes Windows Defender
- Yes, all of it. That includes your computer's bodyguard if it has one.
- Now, start the game.
- If the error persists, verify game files through your client (you won't catch any viruses doing that)
- Start the game again
If it works now, you need to find out how to keep your antivir away from your game directory. If it doesn't, then you can turn the stuff back on now.
There's a chance of >95% that we have already found the source of your problems — pirated copies just don't mod well. That's the first reason why things won't work.
The second reason is that CDPR needs to earn money to pay people to make games for us. If you can at all afford it, please buy the game. It's a good deal: how much are you willing to spend for a movie ticket? How long does a movie keep you entertained?
You are, of course, welcome to peruse the troubleshooting guide. It might even help you. But know that pirated copies will never be explicitly supported.
It doesn't have to be either of these. But if it is, you'll never find it with the rest of the list. Rule it out by deactivating them while you're debugging.
- Antivirus
- ReShade
These mods are not problem children – quite the opposite. But if they are outdated, either your game or your mods won't work. Make sure that you have them all up-to-date with the most recent game version.
Some mods go far beyond the ordinary, adding whole new features to the game (why no flying cars, CDPR?). Unfortunately, that means they're more prone to breaking than others. Here's a non-comprehensive list.
Being on this list does not mean that a mod is "bad" or that you shouldn't use it – they break much for the same reason as the frameworks do, and are fixed in the same way (the modder has to update). Until that happens, you will have to disable them.
Adds flying cars to Cyberpunk. While this is awesome, it will absolutely break whenever CDPR changes anything, and requires updating.
Displays in-world holographic arrows that direct you towards your quest objectives. Is very likely to break upon patches.
Adds car chases and a bunch of related features. While CP2077 needs more car chases and explosions, this usually breaks and will require an update.
Adds mod settings to the in-game menu – Redscript version. This needs to be updated after every game patch.
Adds mod settings to the in-game menu – CET version. The mod itself will be fine, but it's dependent on Cyber Engine Tweaks being up-to-date.
Most famous for edits of the female body that defy gravity and wreak havoc on V's spinal disks, this modder has been around since the early days, and the same is true for their mods.
However, modding has come a long way since then, and spawn0 never followed. For that reason, their mods are known to have compatibility issues with pretty much everything in the general vicinity.
On the bright side, their mods won't crash your game and are downwards compatible until the dawn of time. With Phantom Liberty, sp0 mods have been known to cause crashes to desktop near the dam.
Bad news: The game's logs are usually less helpful than the Swiss navy.
Good news: Mods are doing a far better job.
Bad news again: You have to find the right log file in the game directory.
Good news again: There's intel how (see below)
jackhumbert's mod ctdhelper will give you additional information. There is a chance that it shows you something helpful, most of the time it
If you don't want to download and run script files from the internet, you can go and Step 1: Temporarily disable all your mods by hand. Otherwise:
- 1.
- 2.Now, do either of the following things:
- 1.Move it to your Cyberpunk install folder and double-click it
- 2.Drag-and drop your Cyberpunk folder on the file that you downloaded
- 3.After running, the script will have created a folder
_LOGSin your Cyberpunk directory, which contains a file listing all the log files for you.
The list will give you useful information along with a list of files to check. Once you've found the broken mod, you can go here for instructions on how to troubleshoot further – they also tell you when you should ask for help!
You have hundreds of mods, and one of them is broken. How do you find out which one it is without wasting the entire day?
Don't worry! As long as you have less than 2048 mods, bisection lets you find the problem child with only 10 rounds. (Otherwise, it's 11)
Some mods install themselves to multiple directories, but that doesn't matter. Due to the fact how mod loading works, you can find the error like this.
If you are using Vortex, you should enable and disable mods through Vortex rather than directly on disk. The principle below still works, you're just selecting the halves inside Vortex instead of moving them between directories.
If you do opt to work directly on disk, do not save changes to files if Vortex prompts for it.
To find out the type of broken mod, take each
Directory from the following list and complete the steps in the next paragraph after the table.Kind of mod | Directory | explanation |
|---|---|---|
.archive | \ mods | Redmod directory: contains .archive mods (in subfolders) |
.archive | \ archive\pc\mod | Legacy directory: contains .archive mods |
.lua (cyber engine tweaks) | \ bin\x64\plugins | Cyber Engine Tweaks |
redscript | \r6\scripts | redscript mods |
red4ext | \r6\tweaks | red4ext tweaks |
- 1.Rename the game data folder (game folder for short – e.g.
archive/pc/mod) to a backup folder by appending an underscore (e.g. /mod_). Only do this with the last subfolder in the path, the result should be\archive\pc\mod_, notarchive_\pc_\mod_\. - 2.The folder is now hidden from the game. Since it doesn't know, it will try to look inside anyway - create a new empty folder with the original name for that (e.g.
/archive/pc/mod). - 3.Start the game. You will now run into one of these two scenarios:
- Your problem is gone: Jackpot. This is the correct folder for the next section: Go bisect Before you go there, you can restore all the other folders you moved, deleting the empty directories.
- Your problem is still there: This folder is innocent. Proceed with the next
directoryfrom the table above.
You can put the innocent folders back if you want: due to the way mods are loading, there won't be side-effects.
Congratulations, you have found which folder causes the problem — you're more than halfway there. All that's left is to find the broken mod. Here's how.
The process is the same every time, no matter if you are moving files or folders.
- 1.Switch on half of the mods from your backup folder by moving them back to the game folder.
- 2.Remember (roughly) which batch you moved (e.g. "everything after
E"or "the first half") - 3.Start the game. You will now run into one of two scenarios:
- The error is still there: Progress! Go to Step 5.
- The error is gone: Progress too! Go to step 4
- 4.The error is gone: You have identified which mods aren't the problem! Good! Do the following:
- 1.In your backup folder, find the last batch of mods that you touched
- 2.Half of these go into the game folder
- 3.Go back to step 2 – you should now definitely see the problem again.
- 5.The error is still there: You have narrowed it down, let's narrow it down further. Do the following:
- 1.In your game folder, find the last batch of mods that you touched
- 2.Half of these go back into the backup folder
- 3.Go back to step 2 for the next round – the problem might be there or not.
- 6.Repeat this process until you know which mod is causing the crash. Then, you can either try to update it, or do a full uninstall
If your CPU is too busy, the game will try to save resources by dropping audio, starting with dialogue audio. Disabling spatial audio from the main menu might help:
Missing footsteps had in the past been connected to a bug in Let There Be Flight, so it is worth debugging your script mods. However, if you're on the most recent version (check the github for previews), you might just have to bisect your mods at random.
If the mod in question is Cyber Engine Tweaks (CET), check the corresponding subpage. If it's anything else, read on.
Normally, a mod should just work, as long as all of their requirements are working. If you aren't certain what that means, you can check Requirements explained for detes, or just follow the checklist below.
If you've been using Mod Organizer 2 to install your mods, chances are high that it's been doing it incorrectly, at least for some of the more important mods. You'll need to do additional steps detailed here in order to get MO2 working with Cyberpunk.
If your mod is cyber engine tweaks itself or a dependent mod, you can check the sections below. Otherwise, follow the general troubleshooting steps.
Here's what you can do:
- 1.
- 2.Check the requirements on the mod's nexus page. Make sure that you have installed them all and that they are up-to-date.
- 3.Make sure that all of your core frameworks are up-to-date and starting up correctly (here's how you can check their log files)
- 4.
- 5.
You have installed Cyber Engine Tweaks, but it's not active / not letting you bind a key:
- Is CET in the right place? It has to be installed under
Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks
- Is there a
gamelog.loginside the directory? If not, move the folder out ofpluginsand reinstall from a fresh download.
You will find all the files mentioned below under
Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks
You almost never need to do this.
However, if you want to remove anything that Cyberpunk might have stored on your disk, you need to find and delete the following folders (as per CDPR's own troubleshooting guide:
%userprofile%\Saved Games\CD Projekt Red\Cyberpunk 2077%userprofile%\AppData\Local\REDEngine%userprofile%\AppData\Local\CD Projekt Red
You can quickly navigate to the folders by pasting the path into your Windows Explorer's path bar, or pressing Windows+R, pasting the path there, and
This is the last resort and you do not need to do this — run this script for the same result in less time. However, if you're still set on reinstalling, the instructions below will help you completing that in minimal time.
Unless you back them up, your mods will be lost. If you don't want that, make backups of the following folders:
-
/mods -
/archive/pc/mod -
/bin/x64/plugins/cyber_engine_tweaks -
/r6/scripts -
/r6/tweaks
Unless you back up your mods and scripts, all your settings and manually installed mods will be lost.
The instructions below tell you which folders not to delete. Delete everything else.
- 1.Go to the Cyberpunk 2077 install directory
- 2.Delete everything except for the folder
archive - 3.Inside
archive, delete everything but the folderspc - 4.Inside
pc, delete everything but the folderscontentandep1 - 5.Verify your files
Unless you back up your mods and scripts, all your settings and manually installed mods will be lost.
Will download < 1GB.
Rename or remove the following folders. If you do not have them, you don't need to do anything.
/mods
/plugins
/engine
/r6
/red4ext
/archive/pc/mod
/bin/x64/plugins
Afterwards, verify your files.
In case neither of these options is good enough for you, you can find a full reinstall guide on CDPR's support page.
You have completed either of the previous steps. Your game should start now. If it does not, you either have leftover files (check here for how to get rid of them), or you have a problem that is not related to Cyberpunk. Make sure to follow the hints in the red box at the very beginning of this guide.
Now it's time to systematically install mods. We'll start by installing the frameworks and making sure that the game starts up without any framework-dependent mods. Afterwards, you can add back all of your mods, and if the game stops working, find the offender via bisect.
Don't worry about your savegames — those are fine, even if they won't load right now. We're just laying the foundation here that you can later build upon.
Let's go about it step-by-step.
This step will tell you how to set up your Cyberpunk install with the necessary dependencies so that you can start modding.
- If you didn't have it in your previous install, skip it.
- Install it (manually or via Vortex, your choice)
- Start the game and load a savegame (you can also do this after installing all of them, but if you run into issues, that will make isolating the point of failure more difficult).
- Optional (for CET): Start the game and make sure that it asks you to bind a key. If not, check the corresponding section of this guide.
If you are using redmod (have any folders inside of
/mods), you probably have cybercmd installed. That is no longer necessary with RED4ext >= 1.13 and can lead to false positives. Uninstall it!Once you are done, start up your game and load a savegame. If you don't have one or the game still crashes, start a new game.
You need to complete this step before proceeding: if the core frameworks aren't working without mods, they won't work with mods – adding anything now will just make debugging more difficult.
Fortunately, this is not rocket science. Be methodical and install them one by one. If you need help, you can find us on Discord (
#mod-troubleshooting)If you don't (yet) have any mods, you can head over to Nexus and start installing. Make sure that you include all necessary dependencies!
This section assumes that
- your game is starting
- you can (without crashing) do either of these things:
- load a savegame
- start a new game
If you didn't make it that far, the steps below won't help you and will only obscure your problem. Please head back to Step 1: Temporarily disable all your modsand complete the process.
- 1.Put it back into its original place in your new/fresh install
- 2.Start up the game
- 3.Load a non-modded savegame or start a new game
If your crash(es) are back, you can now go to the bisect section and follow the steps for your folder.
Your error goes something like this:
- Access is denied
- Can't access file 'some/file'
- could not move file from 'Path\to\blabla.tmp' to 'Path\to\Cyberpunk 2077\subdir\some.file'
- Expression: EXCEPTION_ACCESS_VIOLATION
- The thread attempted to read inaccessible data at 0xsomething
- An exception occured while creating the logger
- Cyberpunk is trying to write to a file that doesn't exist
These are caused by access errors – Cyberpunk is trying to read or write a file, and for some reason, it can't.
Ignore this if you can't spot any file paths in the error message
If Cyberpunk is trying to move files to a subdirectory that it can't access, make sure that the directory actually exists (if it doesn't, create it). The most frequent candidate for this is /
r6/cache/modded.Sometimes, the game instance doesn't shut down properly and is still running in the background, althoguh you can't see a window. This problem goes away after rebooting.
- Open your task manager (Ctrl+Shift+Esc)
- Switch to the Details tab
- Sort by Name and scroll to C
- Check if you can see anything Cyberpunk in the list.
- If yes, right-click on it and select End Task
It is possible that your antivirus is causing this problem. Before you lose your mind, try temporarily disabling it.
Always a good idea to do that from time to time – in this case, it could make the error go away.
If it doesn't, check the next steps on the list.
Sometimes, files in your Cyberpunk game directory are set to read-only.
We've had confirmed reports of the following culprits:
- Steam
- mo2 mod manager
- various flavours of antivirus
- Press Windows+R
- type
cmdand press Return to open the command line - run the following command (replace the path with your actual game dir):attrib -r "C:\Path\To\Cyberpunk\*.*" /s
- Navigate to the Cyberpunk game directory and right-click on it
- Select Properties (the last entry in the drop-down menu)
- Uncheck the "Read-only" box:
Sometimes, file ownership got messed up, and not all files in the folder are accessible by your current Windows account. It is a mystery how this comes to be.
You can fix it via system console or via Windows Explorer; either of those will do. If in doubt, the commandline one is more thorough.
In any of the commands below, you need to substitute
C:/Path/to/Cyberpunk2077 with the path to your game directory.- Press Windows+R
- Type cmd and press return
- Run the following command (make sure to insert your real Cyberpunk path):
- takeown /R /A /F "C:/Path/to/Cyberpunk2077" /D N
- If that didn't help, run the command
whoamito see your current user name. You will need it for the next step. It should be identical to your Windows username, but if you have