🆘Troubleshooting

Summary

This 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.

Interactive guide

Open it in a new window

Navigation

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.

• I don't wanna debug, I just want mods!

• There was a game update and now your mods aren't working

• Your game is crashing

  • During a quest in a car chase

  • it's not even starting

    • Corrupt or missing script files

    • Corrupted archives

    • before the menu

    • when loading a save / starting a game

    • randomly during gameplay

• Redscript Compilation Failed (Popup message)

• Your quests are broken or you get LocKey# messages

• You're on Linux

• You have trouble with your pirated game

• Photomode screenshots are borked

• Press [none] to continue / can't skip loading screen

• You have audio issues

• You have trouble with CET (Cyber Engine Tweaks)

  • CET is not starting

  • You forgot your CET keybind

• XML Document parsed with errors

• You're naked

• Your eyes are black

• You installed a mod, but it's not doing anything

• A mod is causing problems, and you have no idea which:

  • Known problem children

  • Well-known outdated mods

  • Searching: Bisect

  • Searching: Log files

• Something with files or ACCESS_VIOLATION

• Deleting user settings

• This is a waste of time, I'm reinstalling

  • Modding a clean install

Your game is crashing

Randomly, and you have an Intel i7 or i9

Check this forum post. If that doesn't help, read on.

During car chases

If your game is crashing during certain car chase missions, try removing Eye Exposure Adaption.

If you can't play because the game is crashing, this section will help you find the right troubleshooting steps in the rest of the guide.

• If you're done with this shit and would rather reinstall, see The nuclear option: a clean install

Crash on startup

If you're trying to start your game, but it never even launches, this is the right section for you. Otherwise:

• If the game crashes before you make it to the menu, see Crash before menu

• If the game crashes when you're trying to load a save, see Crash on loading a save

Cyberpunk has flatlined

Check the section Cyberpunk has flatlined below.

ValidateScripts.cpp:42

Empty your cache, check the info box underredscript / RED4ext.

Red4ext.SDK: Failed to resolve address for hash 0x1817231d

You need to update the game and RED4ext

Red4ext: A dynamic link library (DLL) initialization routine failed

You need to install the VisualC Redistributables. Check the red box under Navigation for a download link.

Something about files or permissions

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.

Some other error

Your problem lies with either red4ext or redscript. You can find what to do under redscript / RED4ext

Crash before menu

If you're starting the game, but never make it to the in-game menu, this is the right section for you. Otherwise:

• If the game never even starts, see Crash on startup

• If the game crashes when you're trying to load a save, see Crash on loading a save

2.0 / PL: Missing tweakdb.bin or inaccessible memory

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 game directory and find the folderr6\cache.

2. Find the filetweakDB.bin and copy it (Ctrl+C)

3. In r6\cache, browse to the folder modded (create it if it doesn't exist)

4. paste tweakDB.bin here (Ctrl+V)

5. If asked to overwrite, select Yes

6. If you have Phantom Liberty, repeat the process with tweakdb_ep1.bin

If that doesn't fix it

Your problem most likely related to Cyber Engine Tweaks. To find out how to troubleshoot it, check the "disable CET" section.

Cyberpunk has flatlined

See Crash before menu

Crash on loading a save

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:

• If the game never even starts, see Commands

• If the game crashes before you make it to the menu, see Crash before menu

• If you can start a new game without crashing, see Corrupt(ish) saves

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. Go to the bisect section and start with the first two entries on the list

If that doesn't solve your problem, or if the issue is save-game related, feel free to browse around some more.

Corrupt(ish) saves

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

Game.GetQuestsSystem():SetFactStr("bls_ina_se1_ripperdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("cct_dtn_ripdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("hey_spr_ripperdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("pac_wwd_ripdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("std_arr_ripperdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("std_rcr_ripperdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("wat_kab_ripperdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("wat_kab_ripperdoc_03_default_on", 0);
Game.GetQuestsSystem():SetFactStr("wat_nid_ripperdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("wbr_hil_ripdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("wbr_jpn_ripdoc_01_default_on", 0);
Game.GetQuestsSystem():SetFactStr("wbr_jpn_ripdoc_02_default_on", 0);

Game.GetQuestsSystem():SetFactStr("bls_ina_se1_ripperdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("cct_dtn_ripdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("hey_spr_ripperdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("pac_wwd_ripdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("std_arr_ripperdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("std_rcr_ripperdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("wat_kab_ripperdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("wat_kab_ripperdoc_03_default_on", 1);
Game.GetQuestsSystem():SetFactStr("wat_nid_ripperdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("wbr_hil_ripdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("wbr_jpn_ripdoc_01_default_on", 1);
Game.GetQuestsSystem():SetFactStr("wbr_jpn_ripdoc_02_default_on", 1);

Crash during the game

This section tells you how to deal with crashes during gameplay.

When editing the inventory

Kiroshi Crowd Scanner and Tooltip Fixer do not play together (source, discord). Uninstall one of them.

Somewhere in Japantown

Somewhere in Japantown is a mesh with a broken material. Material and Texture Override removes the cache, and thus forces the game to re-create this material, and causes the game to crash.

Many mods list MTO as a dependency, but it's usually optional and you only need it to force-apply changes to original game materials.

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

… 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

• resetting your game to a clean state (if the error persists, it's not mods)

• temporarily disabling certain types of mod to home in on the cause (see the bisect section for an overviev)

Best of luck!

Corrupt or missing script files

Cyberpunk 2077 encountered an error caused by a corrupt or missing script file and will now be forced to close. Please verify...

You have an error with redscript / RED4ext. Please see the next section.

redscript / RED4ext

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.

If you're sure that you don't have cybercmd, it's time for more detailed troubleshooting:

1. If you are on Linux, make sure to double-check the launch options, as Steam sometimes resets these between updates

2. If your game stops crashing when you disable red4ext, that points to an error with a dependent mod. Make sure that your error is related to red4ext before you proceed!

3. Find the folder Cyberpunk 2077/red4ext/log and check for a file named red4ext.log. Does it exist?

   • No: RED4Ext is not installed correctly. Make sure that you fix this before troubleshooting further.

   • Yes: look inside, it will tell you which mods aren't compatible with the current game patch and may be the cause of this issue

4. 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

• troubleshoot or reset redscript

• the faster variant: temporarily disable all mods and reinstall the core frameworks

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, starting with the first two folders.

The game isn't starting: other reasons

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:

• Too many mods

• Message: Failed to initialize scripts data!

• Steam file verification loop

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

• you have the most recent version of .NET Desktop Runtime installed

• you have Visual C++ Redistributable 2022 installed (direct download, Microsoft)

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.

If none of that helps, find us on Discord in #mod-troubleshooting.

Too many mods

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:

Failed to initialize script data

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.

Steam: verify file integrity loop

The error below is partial to Steam:

Cyberpunk 2077 encountered an error caused by corrupted or incomplete game data

There are three potential fixes:

• Run as admin

• Run without antivirus

Workaround suggested by CDPR:

• Set Power Limit (TJ max) for CPU to 150W

• Reduce Long and Short Duration Package Power Limit to 150 W (Intel default is 253)

• Set the maximum CPU Core Temperature to 98°

• Reduce the P-Core ratio of the processor

• Deactivate Turbo Boost of the CPU

• Disable CPU Hyper-Threading

Or check Reddit:

• Downclock your processor (via reddit, do so at own risk)

Run as admin

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 Compatibility tab

• Check the box Run this program as an administrator

Run without antivirus

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 antivirus away from your game directory. If it doesn't, then you can turn the stuff back on now.

You pirated the game

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.

Finding the broken mod: known problem children

Stuff that isn't mods

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

Frameworks / Core Mods

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.

Script mods

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.

In-World Navigation

Displays in-world holographic arrows that direct you towards your quest objectives. Is very likely to break upon patches.

Vehicle Combat

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.

Mod Settings

Adds mod settings to the in-game menu – Redscript version. This needs to be updated after every game patch.

Native Settings UI

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.

Well-known outdated mods

The below mods will no longer work on versions beyond 2.0/2.1 and in some cases can completely break your save. If you have any of these, remove them.

Let There Be Flight

Adds flying cars to Cyberpunk. While this is awesome, it will absolutely break whenever CDPR changes anything, and requires updating. It has been broken for a long time as of patch 2.02 and later and will not work.

CTD Helper

Replaces the default crash logs with actual usable logs instead. This needs to be updated after every game patch. It has been broken for a long time as of patch 2.02 and later and will not work.

Respector

Effectively an in-game save editor that can give you a lot of items and even create a new game plus method. This mod has stopped working since 2.0 and while it will be updated in the future, in the mean time mods like Simple Menu (CET) and Pseudo New Game Plus can be used.

NPCs Gone Wild (NSFW)

Makes multiple NPCs nude. In all versions since 2.0, this causes missing characters, missing body parts, exploding limbs, and other issues. Do not use the mod, there is a Naked NPCs collection by modder marnhorn that does the same thing and will work on current game versions.

Phone Messages Overhaul (PMO) and 8ug8ear Romance (standalone)

These mods change the game journal that controls all quests to add more romance options. This method only works on the patch it's made for and therefore they will not work on version 2.1 and later. Other mods that do the same thing, but in a compatible way, are Panam Romance Enhanced and Judy Romance Enhanced, which use ArchiveXL (the safe method).

Biosculpted Exotics

This mod adds furry, animal-like NPCs to the game and optionally replaces main characters. While lore accurate to a point, the mod is made in the same way as PMO and therefore breaks quests in 2.1 and later.

Eye Adaptation Auto Exposure Fix - Vanilla Native Weather Option - Complete Overhaul - No More Blinding Lighting and Slower Bloom Gamma Changes - Optional SHARPENING OFF and VIGNETTE OFF

This mod hasn't been updated since v1.63, and the game has made significant breaking changes that cause this mod to crash to desktop (CTD).

spawn0

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.

Finding the broken mod (log files)

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. Download this script (right-click -> save as) Link goes to Presto's github repository

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 _LOGS in your Cyberpunk game 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!

Finding the broken mod (bisecting)

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?

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.

Which kind of mod is 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.

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_, not archive_\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 directory from the table above.

Go bisect

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.

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

Bisect: Video demonstration

Audio problems

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:

It's not connected to CPU load

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.

Mod(s) aren't loading/triggering

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 Users: troubleshooting requirements for detes, or follow the checklist below ( Getting a mod to work).

• Make sure that you have enabled mods in your launcher.

• If items or hairs aren't changing, you need to install cookedapps nulled (why?)

• If materials aren't updating, you need to install material override (why?)

• If you already have all of that, check the next section.

Getting a mod to work

1. Check that you've enabled mods (see Deploying Mods and Starting Game).

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.

   • If the requirements list Cyber Engine Tweaks, check its log file under Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\cyber_engine_tweaks.log

   • For a more detailed guide, see Users: troubleshooting requirements

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. Check the other log files in the game directory (here's a guide how)

5. Optional: reach out to us on Discord in #mod-troubleshooting

Deleting user settings

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

The nuclear option: a clean install

Back it up, baby!

Quick (download <4GB)

1. Go to the Cyberpunk 2077 install directory

2. Delete everything except for the folder archive

3. Inside archive, delete everything but the folders pc

4. Inside pc, delete everything but the folders content and ep1

5. Verify your files

Modular / minimal download (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.

Nuke it from the orbit: The thorough version

In case neither of these options is good enough for you, you can find a full reinstall guide on CDPR's support page.

A fresh install: Starting from scratch

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.

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

• 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. If you don't have one or the game still crashes, start a new game.

This should now work. If it doesn't, you need to check your log files to see which framework is causing trouble, or find us on Discord in #mod-troubleshooting.

Adding (back) your mods

If you're using Vortex

Head directly to the bisecting section and pretend you have just removed all your mods.

If you made a manual backup:

For each folder that you have backed up (check link for a list), repeat the following steps:

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.

Something something files

Your error goes something like this:

• Copy

  Access is denied

• Copy

  Can't access file 'some/file'

• Copy

  could not move file from 'Path\to\blabla.tmp' to 'Path\to\Cyberpunk 2077\subdir\some.file'

• Copy

  Expression: EXCEPTION_ACCESS_VIOLATION

• Copy

  The thread attempted to read inaccessible data at 0xsomething

• Copy

  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.

Follow the steps in this section one by one, or find us on Discord in #mod-troubleshooting.

Make sure that the file path exists

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.

Make sure that no previous game instance is running

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

Reboot your PC

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.

Make sure that all files in the game directory are writable

Sometimes, files in your Cyberpunk game directory are set to read-only.

What kind of monster would do something like that???

We've had confirmed reports of the following culprits:

• Steam

• mo2 mod manager

• various flavours of antivirus

Via system console:

• Press Windows+R

• type cmd and press Return to open the command line

• run the following command (replace the path with your actual game dir):

  Copy

  attrib -r "C:\Path\To\Cyberpunk\*.*" /s

Via Windows Explorer:

• 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:

File Ownership

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.

Via commandline

• Press Windows+R

• Type cmd and press return

• Run the following command (make sure to insert your real Cyberpunk path):

• Copy

  takeown /R /A /F "C:/Path/to/Cyberpunk2077" /D N

• If that didn't help, run the command whoami to 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 spaces or special characters, Windows might get funny about the spelling.

• Run the following command (putting your actual game dir and the username from whoami):

• Copy

  icacls "C:/Path/to/Cyberpunk2077" /grant YourUserName:F /T /C

Via Windows Explorer

We haven't included the full instructions here, but you can check this guide.

Reboot your PC again

If none of these things has helped, reboot your computer.

The error should be gone now.

Not to say that your game will work now – but if you still have an error, it's hopefully a different one. Go back to the start of the guide and let's fix that one too!

Your quests are not working / You get LocKey# messages

This section tells you how to deal with

• quests that are not starting

• broken text messages

• broken journal entries

Quests not starting although you meet all prerequisites

When two mods hook into the same quest to do their thing, this can break the quest.

Known problem children:

• Phone Messages Overhaul

• Judy/Panam Romance Messages Extended

If it wasn't that, check any other mod that hooks into basegame quests, such as romance mods or "quest fixes".

Shards, text messages or journal quest just say LocKey#

If you are playing in a language other than English

This can be caused by mods not including translation files for your language. Check if there is a translated version, or change the game language to English.

If you are playing in English

Most likely caused by a mod conflict: two mods are trying to change the same text archive or journal entry. You can use the Archive Conflict Checker Tool to find conflicting mods, or check the list below.

Known problem children:

• Phone Messages Overhaul (you can resolve this by setting this mod to load first)

• Hot Fuzz

• Biosculpted Exotics

• Database Fixes

If none of the mods have suggestions about load order, swap them around and see if it fixes the issue.

Redscript Compilation Failed

You're running into the following error:

REDScript compilation failed. The game will start, but none of 
the scripts will take effect. This is caused by errors in:

0. Make sure that you don't have multiple versions of Codeware installed

In the past, Codeware wasn't a standalone mod, but was instead bundled inside of other mods. Since that is different now, the leftover versions can cause errors.

1. Search your Cyberpunk game directory for Codeware.

2. If you have exactly one folder, this is not your problem — proceed to the next step.

3. Delete everything you have found.

4. Reinstall the latest version of Codeware from Nexus.

5. Delete the folder r6/cache

6. Verify your game

1. Make sure that you have the latest versions

1. Check Redscript (github | Nexus) and update it

2. Uninstall cybercmd (github | Nexus), if you have it.

Optional, but recommended:

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 can find any errors – warnings may or may not be a problem, see here for context.

3. Reset Redscript

Redscript: Disable dependent mods

Vortex: Disable them

Manual: Remove the contents of r6/scripts/.

Resetting the redscript cache

• delete r6/cache

• verify game files

• Optional: create a new directory r6/cache/modded (this will prevent errors)

• Make sure that r6/scripts is empty

• Make sure that red4ext/plugins is empty (that the red4ext core frameworks aren't getting loaded)

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.

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)

CET isn't starting

CET needs at least VisualC 14.40.33810.0 . You can download it from the official Microsoft website (direct link)

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.

Photomode screenshots are blank

With 1.62, screenshots are now saved to Documents\CDPR\Cyberpunk\Screenshots , and the previous location will receive an empty file.

With 1.63, screenshots have now been moved back to \Pictures\Cyberpunk 2077

Press [none] to continue / can't skip loading screen

That is due to Input Loader requiring an update.

I'm not getting a metro ticket!

If you have passed the start of Act 2 and you aren't getting a text with a metro ticket because of an outdated mod, there is nothing you can do. Even removing the mod won't fix it. Remove the mod, then play from an earlier save.

[Kerry/Judy/Panam/River] isn't talking to me!

This is a new one with 2.1 — a reciprocal effect of CDPR's romance interactions with previous romance or phone message overhauls. The bad news is that the broken state is baked into your savegame and you can't get rid of it by removing your mods. The good news is that modders are already on top of the problem, and simply updating should fix your issue.

You can try running the following command (which has solved the issue for some people):

 Game.GetQuestsSystem():SetFactStr("judy_default_on",1)

Switch "judy" for the affected NPC's name. Then, save and reload.

Alternatively, you can use this mod for Judy (which is supposed to have helped as well).

I'm naked!

Here's how to fix your sudden indecent exposure.

1. Go to the vanilla wardrobe in your apartment

2. Create an outfit (anything will do)

3. Equip the outfit

4. Un-equip the outfit

5. Save and reload

6. If that doesn't work, check the next section:

I'm naked in first person perspective! (EquipmentEx)

There is a high change that you're using Equipment-EX, if this applies then try the steps below:

1. Remove all Equipment-EX outfits by typing EquipmentEx.DeleteAllOutfits() in CET's console.

2. Save and quit the game

3. Uninstall all files related to Equipment-EX, this can be done by searching for "EquipmentEx" in the game's main directory, then launch the game.

4. You should now no longer be naked.

5. Reinstall EquipmentEx and start creating outfits again.

V has black eyes!

You have an outdated or two different versions of Kala's Unique Eyes installed.

Make sure to uninstall all your eye mods, then open your Cyberpunk game directory and use the Windows Search for e.g. kala. Make sure to delete all leftover files!

I have another problem that isn't on this list

Here's the catch-all solution. After this, your game will work (or the problem you have is not Cyberpunk related).

1. (optional, as this might solve it): Reset the Redscript cache.

2. If your problem doesn't go away, follow the instructions in the next section.

I really just want to get this working, what do I do?

The bad news is, at this point you have little choice but to reset your Cyberpunk install and re-mod it from scratch. The good news is that the process is really streamlined. If you don't run into any hitches, you're <30 minutes away from a working game.

Now, how do we go about this?

Is there a shortcut?

Yes! There is a batch script that will automate steps 1-4 of the list below for you.

If you don't want to download and run script files from the internet, you can go here and complete the steps by hand. Otherwise:

1. Download the mod remover script by either

   • downloading it from Nexus and following the install instructions

   • grabbing it from github (right-click -> save as) and moving it to your Cyberpunk game directory Link goes to the github repository of the person who wrote most of this guide.

2. Optional: If you don't want the script to delete modded files for you (because you just want to disable mods), right-click on the file and select Edit, then find and delete line 6:

   Copy

   set DELETE_FILES=1

3. Make sure that the file is in your Cyberpunk game directory. If you downloaded from Nexus, you should have a cyberpunk2077_disable_all_mods.bat.

4. Double-click it

5. Follow the instructions and prompts

6. Verify your game files

7. Optional: You can now proceed to Step 5 and start modding your game again.

Step 1: Temporarily disable all your mods

Vortex

• Follow the instructions and prompts

Press the purge button — this will remove any and all installed mods.

If all your mods were managed via Vortex:

Start Cyberpunk however you want, as long as it's not via Vortex. If it starts now, you're done here and can proceed with bisecting – otherwise, go to Remove RedScript.

If you had a mixed install:

Complete the instructions in the section manual now.

Manual

Find the following folders:

Cyberpunk 2077\archive\pc\mod
Cyberpunk 2077\mods

and rename them to

Cyberpunk 2077\archive\pc\mod_
Cyberpunk 2077\mods_

You can optionally create a new, empty folder with the same name.

Step 2: disable CET

Find the folder

Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks

and move it out of plugins (e.g. put it on your desktop).

Step 3: Remove scripts and tweaks

First, remove (or rename) the cache:

 r6/cache/modded

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.

Step 4: Remove RedScript

Delete the following files and folders. You don't need a backup, as you can reinstall RedScript from Nexus. If any of them don't exist, that's okay — just means you don't have to delete them.

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
Cyberpunk 2077\r6\config
Cyberpunk 2077\r6\inputs
Cyberpunk 2077\V2077

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
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

GOG

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

Steam

1. Open your library

2. Right-click on "Cyberpunk 2077" and select "Properties"

3. Select "Local Files"

4. Click "Verify integrity of game files…"

Epic

1. Open your "Library"

2. On the "Cyberpunk 2077" tile, find the "…"

3. Select "Manage"

4. Click "Verify"

Step 6: Launch the game

All files you deleted have been re-acquired. If there are no left-over files from earlier modding attempts, your game should work now.

Step 7: Install the core frameworks

Now that your un-modded game is starting, it's time to install the core frameworks. Do this before you enable your other mods, as they won't work without their dependencies and can only add problems at this stage.

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?

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.

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."

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.)

Check the log files

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!