Users: Troubleshooting

If your mods are causing trouble, here's what you can do
This page contains troubleshooting information for end users (people who are not modders). You will find step-by-step guides what to do if your game isn't starting or if your mods aren't working as you expect them to.
Before you start debugging, make sure that
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 (1) (2)
Redmod isn't doing anything: Install cybercmd
To enable REDmods, check here.

Your game isn't starting / Crashes to Desktop

Failed to initialize script data

Message: Failed to initialize scripts data!
File: E:\R6.Release\dev\src\common\engine\src\baseEngineInit.cpp(1019)
Check your NVidia panel. If power saving options are enabled, turn them off.

Other problems

Before following these steps, you might want to take a look at your log files. You can usually ignore Warnings, but maybe you'll stumble on an error message that helps you to narrow down the suspect.

Step 1: Temporarily disable all your mods

If you're running a mod manager (such as Vortex), disable them.
Otherwise, find the following folders:
Cyberpunk 2077\archive\pc\mod
Cyberpunk 2077\mods
and rename them to
Cyberpunk 2077\archive\pc\mod_
Cyberpunk 2077\mods_
The purpose of renaming them is that the game won't find them anymore, but you still have a back-up of the files inside. Feel free to achieve this goal however.
You can optionally create a new, empty folder with the same name.
Check if the problem is gone

Step 2: disable CET

Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks
and rename it to cyber_engine_tweaks_.
If you'd rather delete it, make sure that you retain a copy of your plugins directory, as it contains your mod settings (AMM decorations etc.)
Check if the problem is gone.
If it is, put the folder back and apply the bisection method to cyber_engine_tweaks\mods and cyber_engine_tweaks\scripts until you have found the culprit.

Step 3: Remove scripts and tweaks

First, remove (or rename) the cache:
Check if the problem is gone
If that didn't do the trick, find the following folders:
Cyberpunk 2077\red4ext
Cyberpunk 2077\r6\scripts
Cyberpunk 2077\r6\tweaks
Cyberpunk 2077\engine\tools
and rename them, you know the drill.
Check if the problem is gone

Step 4: Remove RedScript

Delete the following files and folders:
Cyberpunk 2077\bin\x64\d3d11.dll
Cyberpunk 2077\bin\x64\global.ini
Cyberpunk 2077\bin\x64\powrprof.dll
Cyberpunk 2077\bin\x64\winmm.dll
Cyberpunk 2077\bin\x64\version.dll
Cyberpunk 2077\engine\config
Cyberpunk 2077\engine\tools
Cyberpunk 2077\r6\cache\modded
Cyberpunk 2077\r6\config
Cyberpunk 2077\r6\inputs
Cyberpunk 2077\V2077
@Auska has compiled a handy script for unix people:
rm ./bin/x64/d3d11.dll
rm ./bin/x64/global.ini
rm ./bin/x64/powrprof.dll
rm ./bin/x64/winmm.dll
rm ./bin/x64/version.dll
rm ./engine/config
rm ./engine/tools/*
rm ./red4ext
rm ./r6/cache/modded
rm ./r6/config
rm ./r6/inputs
rm ./V2077
mv ./r6/cache/final.redscripts.bk ./r6/cache/final.redscripts

Step 5: Repair game files

Exact procedure as documented by @ArsenicTouch


Go to Games -> Installed, right-click on your game and select the following menu entry:


  1. 1.
    Open your library
  2. 2.
    Right-click on "Cyberpunk 2077" and select "Properties"
  3. 3.
    Select "Local Files"
  4. 4.
    Click "Verify integrity of game files…"


  1. 1.
    Open your "Library"
  2. 2.
    On the "Cyberpunk 2077" tile, find the "…"
  3. 3.
    Select "Manage"
  4. 4.
    Click "Verify"

Launch the game

The game should launch now — all files you deleted have been re-acquired.
You can now re-enable your mods. Do it in chunks and check that the game keeps working so that you can narrow down where the problem is, in case it isn't gone for good.

Finding the broken mod (log files)

Open your Cyberpunk game folder and use the windows search to search for *.log
Make sure to include the asterisk and the dot: *.log
You should see something like this
Now, delete all those files. Don't worry, they will be re-created on next launch.
Don't delete anything that isn't a text document ending in .log, this might break your game.
Start your game again. Now do whatever causes your problem to occur.
Search the Cyberpunk directory for *.log again.
Tip: Sort the files by size by clicking on the Windows Explorer column header.
You can ignore all files that have a size of 0, as they will be empty.
One of these files should contain an error message. You can use it to try and isolate your problem.

Finding the broken mod (bisecting)

There are two directories with mods: Cyberpunk 2077\mods holds REDMods Cyberpunk 2077\archive\pc\mod holds mods that predate the REDMod format.
The procedure below applies to both directories, but you should start with \archive\pc\mod. If your problem is caused by a script, do the same with the CET folder.
First, go to your mod directory under
Cyberpunk 2077\archive\pc\mod
and re-name the entire directory to mod_. Then, create a new empty folder named mod.
Start the game. If the problem isn't gone now, you have at least ruled out vanilla mods as a source of problems. Repeat the procedure with the RedMod directory Cyberpunk 2077\mods.
If you have renamed both directories and the problem isn't gone, you have a different problem. Check your CET scripts or follow these steps.
Now, we need to roughly narrow down which mod has the error.
Move over half of the mods from your backup folder mod_, then start the game.
You will now run into one of two scenarios:
  1. 1.
    The error is gone: swap out the content of your mod folder with the last chunk you moved to the backup folder. Validate that the error persists, go to 2.
  2. 2.
    The error is still there: Move half of the files from your mod folder into your backup folder and start the game and check your problem.
Repeat this process until you have identified the problem child!

Mod(s) aren't loading/triggering

Make sure that all dependencies for your mod are both installed and up-to-date.

A RedMod

Check that you've enabled the feature (see Deploying Mods and Starting Game). Does that solve it? If not, proceed to the section about Log Files and try to find an error message here.


You have installed Cyber Engine Tweaks, but it's not active / not letting you bind a key:
  • Check that mods are enabled
  • Check the install path: Cyber Engine Tweaks has to be installed under Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks

You forgot your CET keybind

Delete the file Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\bindings.json. The game should let you bind a new key at the next startup.

A CET script

Find the CET log at Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\cyber_engine_tweaks.log and check if it contains any errors. If not, navigate to the CET folder and search for log files. (Do not change folders, and do not delete anything - just use the instructions below how to find the files.)

An ArchiveXL/TweakXL mod

Go to Cyberpunk 2077\red4ext and check the log files. (Do not change folders, and do not delete anything - just use the instructions below how to find the files.)

The nuclear option: a clean install

If none of the troubleshooting steps above helped and your game won't start, you'll want to reset it to a clean install. Fortunately, you don't have to redownload the entire game for that.
Unless you back them up, your mods will be lost. If you don't want that, make backups of the following folders:
  • /mods (manually installed redmods, unnecessary if you use Vortex)
  • /archive/pc/mod (manually installed mods, unnecessary if you use Vortex)
  • /bin/x64/plugins/cyber_engine_tweaks (CET settings and AMM)
  • /r6/scripts
  • /r6/tweaks

Quick (download <4GB)

Unless you back up your mods and scripts, all your settings and manually installed mods will be lost.
Do not delete archive/pc/content unless you want to reinstall your entire game.
Inside the Cyberpunk 2077 install folder, delete every folder but archive/pc/content.
Afterwards, verify your files.

Modular / minimal download (download <1GB

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.
Afterwards, verify your files.

Starting from scratch

You have completed either of the previous steps. Your game should start now. If it does not, 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.

Installing the frameworks

Check the framework page. For each of the frameworks, complete the following steps:
  • If you didn't have it in your previous install, skip it.
  • Install it (manually or via Vortex, your choice)
  • Install all of its dependencies
  • Optional: 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.
Once you are done, start up your game and load a savegame. This should work.

Troubleshooting the frameworks

  • If your game crashes when loading a save, try an older, un-modded save. If you do not have one, start a new game, save as soon as you can, and load that one instead. (Don't panic, your savegame is most likely fine)
  • If you add a framework and your game starts crashing before loading a save, you need to check the log files or peruse the rest of this guide and follow the steps there.
You need to complete this step before proceeding. There are no shortcuts to carry you past it, nothing you can install, no one to save you. Fortunately, this is not rocket science. Just be diligent, follow the steps, and consult the rest of this guide.

Adding back your mods

Now it's time to restore your mods. If you have multiple folders backed up, put them back one by one – you can find a list at the start of this section.
If you do not have multiple folders and instead used Vortex, head directly to the bisecting section and pretend you have just removed all your mods.
Do not add all mods at once. Install them in chunks and verify that your game starts correctly. (see "Finding the broken mod (bisecting)" for further intel).

Corrupted archives

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.

Corrupted scripts

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. Try the following steps:
  • 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
  • you removed a RED4ext mod, but your scripts aren't recompiled and still refer something from removed mod, you have to fix redscript
  • you're missing scripts cache file (only possible if you manually delete it) it can't be anything else
If that doesn't solve your problems or you run into an error with script files, check Redscript Compilation Failed.

XML Document parsed with errors

XML document parsed with errors: C:\Path\toCyberpunk 2077\r6/config/inputUserMappings.xml Error description: Error parsing element attribute
According to InputLoader's documentation, you can ignore this. Keep searching! (You can also try reinstalling InputLoader and hope that the error goes away)

Redscript Compilation Failed

REDScript compilation failed. The game will start, but none of the scripts will take effect. This is caused by errors in...
If the error goes away at any point during this guide, abort.

1. Make sure that you have the latest versions

Actually check this. Do not rely on memory or common sense. If in doubt, re-download.
  1. 1.
    Check Redscript
  2. 2.
    Check Cybercmd
These links go to github. This site is legit, it's where they are before being uploaded to Nexus.
Check that you have the latest versions of all troublesome Redmods.

2. Check redscript.log

It is in r6/log/redscript.log. See if you have any ideas to resolve the error.

3. Reset Redscript

If you rename or delete any directories, make sure to create a new, empty directory.

Disable your mods

Vortex: Disable them
Manual: Remove the contents of r6/scripts/.
You can zip the directory from the windows context menu, then delete its contents.

Revert changes in r6/cache

This is the script dir for non-REDmods
Delete everything inside r6/cache/modded/, leave the empty dir.
If the file r6/cache/final.redscripts.bk exists, delete final.redscripts and remove the .bk extension.
Check if your game starts.
If that did not work:
It's possible that final.redscripts.bk was corrupted as well. Delete final.redscripts again and verify your game files.
Make sure your game starts up without error.
After the missing files have been recovered, you will now have what amounts to a clean install!

4. Reinstall your mods

Hopefully, your problem should be gone now.
It's time to put your mods back and see if you can start the game - see Starting from Scratch.

Dealing with a broken mod

You have followed all the steps and your game is launching, but you now have a mod on your hands that just doesn't work, and you want it to. What do you do now?
If you join a modding discord to ask for help, people will walk you through this list, so you might as well do it first. Nobody will unbundle someone else's mod and just fix it for free unless they want to use it themselves.

1. Make sure you have the correct dependencies

Many mods require frameworks or other mods to work. Check the mod's page and description for those, and install them.
Repeat the process by installing the dependencies' dependencies, until you have everything necessary.

2. Check the mod's description

Often, the description contains detailed installation instructions, known incompatibilities and/or workarounds. Sometimes, mods worked on past versions of Cyberpunk, but the author stopped updating. In that case, proceed to point 5 of this list.
Before you get upset, please keep in mind that modders don't do this for a living (these are called "game developers" and they get paid for it). Somebody made this in their spare time, for their own use, and then decided to share it with you for free. Do you know the easiest way to avoid toxic users? It's not publishing your mods. No reward system, credit points or reputation will ever make up for online abuse.
As a mod author, I can tell you that I will ignore assholes, but gladly spend an extra hour after work to help out someone who politely asks me for help.

3. Check the mod's comment section

You're unlikely to be the first person to run into this problem. There is a good chance that the comment section on the download page has helpful information. Look for either a pinned post by the mod's author or a user discussion about your problem — these often contain a solution.

4. If you are using a mod manager: Try installing it manually

While mod managers are very reliable and get better with every new release, you should rule out that they are the cause of the problem by installing the mod from hand.
If everything else works and installing the mod by hand still breaks compilation, then it is broken. See "Dealing with a broken mod" below. start your game client's file verification.

5. Contact the mod's author

Describe your problem as clearly as you can, and add all useful data.
Bad bug report: "Your mod doesn't work lol pls help"
Good bug report (example): "Hi, installing your mod (manually and Vortex) causes a Redscript compilation error on startup (possible screenshot of error popup). xxx.log says <citation of error message>. All my dependencies are up-to-date, and I've ruled out that it's any other mod. Can you help me out?"
Good bug report (example 2): "Hi, when I try to equip Item <item name and colour>, it doesn't show up and I only get glitches. I'm using Hyst's boob mod and <specific version and variant> of your mod. I hope you can help me? Thank you for making this."
As per the last red box, do keep in mind that you're asking a favour. The modder doesn't have your problem, and if they do, they know exactly how to fix it. The most time-efficient response for them is to ghost you, so any kind of response is either them being nice or them losing their temper about yet another entitled idiot who can't read. Don't be the entitled asshole who can't read.

5. Hands-on troubleshooting

At this point, you have exhausted all easily accessible solutions. If you still want the mod to work, you will have to get involved yourself. A commendable attitude! (Not sarcasm, it really is.)
This is the point where you might want to join a modding discord, because now you're entering the territory where other modders can actually help you.
Usually, there will be a log file that will point you towards the source of your problem. If there isn't (the game loads and the mod just fails silently), that means that the error is inside the archive and you have to become a modder.

Fixing scripts

But sometimes, you're lucky. Sometimes, the error is in a script file. You can tell this by a log entry pointing towards a file in your Cyberpunk folder (e.g. r6\scripts\my_broken_script.reds).
Open up that file in a text editor like Notepad++ and try to find and fix the problem. Sometimes, the log file has more information. Sometimes, an online syntax check can help you — there isn't one for redscript, but it's fairly close to lua.
Sometimes, such mistakes are trivial — a forgotten , or incorrect file encoding. Often, they are not.

Ascending from user to modder

If the error isn't in any script files, you will have to unbundle the .archive, load it in WolvenKit, and get your hands dirty. We'll be seeing each other, choomba!