Patch 2.02 killed the game, won't start even with mods disabled.

[Emperor Palpoutine]

Title. Tried to repair the game files via Steam's file validation button, still not working. This is

Edit : it seems the presence (even if disabled) of the mod "Mods Settings" wil cause this. Remove it and the game (and other mods) should launch fine.

[zpc]

Depends heavily on the mods - best way to get rid of them is to delete the whole game, clean all the other locations where mods nest themselves in and reinstall the game. Even a trace of an incompatible mod wreaks havoc in the game.

A vanilla 2.02 works without problems.

[Kingsleaze]

Patch 2.02 works fine, I think your borked system is the murder suspect.

[Khuanzi]

I have no mods and mine won't start.

[lackesis]

Yes, some mods broken, but I can still play the game. Try deleting the modded script folder or replacing the old script with 2.02 script.

[RaytheHunter]

anyone have common modds that are broken im just trying to figure witch one is crashing my game lol

[Balekai]

The problem is likely left over remains of mod frameworks in your Cyberpunk 2077 main directory, which validation/clean install will not fix by itself if you didn't delete the entire folder. Without removing every single mod plugin/DLL/script from the bin and mod folders, your game will crash.

The easiest way to start from scratch is to move any mods out of your mod folder into a backup and run a mod removal tool from Nexus Mods (which must be placed in your 2077 directly). They will remove anything that's not supposed to be there including mod framework dlls etc. Then all you have to do is validate for like 10-20 minutes to restore some deleted files. Launch the game to test and it will 99.99% work. :) :)

I just used one called Cybernuke but I can't find the link to it anymore. I downloaded it a long time ago, but used to fix my game just yesterday.

Then just move your mods back to the mod folder if not using an organisers (delete any old framework stuff) and install the latest mod framework versions thereafter.

[Rothgar57]

I am not running any mods. The game starts for me. Last patch it wouldn't. I had to do a full install. Having said that game 2.02 runs like crap now.

[EvilDonut]

Classic CDPR patch. Nothing useful, 100 bugs

[Muse]

It works.

I had similar issues with the prior patch; had to delete the game files in their entirety, reinstall, run an integrity check. Vanilla runs no problem now. Definitely recommend doing all you can before flaming discussions but, hey, maybe I'm just more of a problem solver.

It goes without saying that mods will bug out after an update for any game. If you don't do what you can to fix it, you shouldn't really bother to complain.

Catch ya on the flip side, choom.

[orcaa]

Originally posted by Emperor Palpoutine:

Title. Tried to repair the game files via Steam's file validation button, still not working. This is :♥♥♥♥: :repoop: :dip:

verifying game files do NOTHING / to or for any mods. if mods are the issue you need to make sure each one is compatible to the game version you are using.

[REYFOXHOUND]

After doing fresh install on 2.02, deleting all game files and folders, reinstalling nvidia driver, updating windows 11 to the latest, I can 100% confirm that REDLauncher is no longer working and you can't play the game by clicking the "PLAY" button on Steam. In order to play it I had to execute the Cyberpunk "EXE" files on the "bin" folder and don't forget to remove all mods. Game will run prefectly. My saves data from the previous 2.01 are fine. All my drop items from twitch are still there 100% but I probably won't be able to get any twitch drop item since REDLauncher is needed to sync between the game and twitch account.

EDIT: Just found a solution for my RED Launcher problem. I added "--launcher-skip" command inside game properties. Now everytime I click "PLAY", the game exe will launch directly skipping out RED Launcher. Every features on the Steam including save sync, play time sync, overlay, screenshots, all of them now is working normally.

[NJK]

Hey, just run vortex and check for mods. Orange icon on the mod version will send you to your default browser, there you can install the mods (hopefully mod author made vortex version) and it will auto-install.

If a file conflict appears, set lower mod version to 'before' or 'before all' and the new mod version to 'after' or 'after all' or 'any version'.

Vortex is better than it was in 2021, so game should launch now. All depending of course on whether or not the mod author updated the mod properly. If you have issues, create a default collection (name it default for ease of porting to new system, publishing to nexusmods) and make sure to have any new mods (from new > old) appear above it; this way, you can troubleshoot any errors when updating.

[No_One]

I was having this issue with my lightly modded game. I updated all of the usual script mods and extensions, yet it would still not launch from the launcher. Zero errors in logs & no crash message, just a blank fail to start.

The problem for me was the "Mod Settings" mod. It has yet to updated for 2.02 as of this post. Deleting the "mod_settings" folder within: Cyberpunk 2077>red4ext>plugins made it work for me

[Emperor Palpoutine]

Originally posted by No_One:

I was having this issue with my lightly modded game. I updated all of the usual script mods and extensions, yet it would still not launch from the launcher. Zero errors in logs & no crash message, just a blank fail to start.

The problem for me was the "Mod Settings" mod. It has yet to updated for 2.02 as of this post. Deleting the "mod_settings" folder within: Cyberpunk 2077>red4ext>plugins made it work for me

Yes, I found the same thing yesterday. Thank you tho!

[Yuki]

I find it curious. People keep complaining that the 2.02 patch makes the game run worse. For me, the game runs better. I have not crashed since the new patch. I have noticed that the game stutters when in areas usually it would crash before. To me, this is a great improvement.

As for mods, try deleting the r6/cache folder, then re-validating. That worked for me after removing any redscript mods that can cause issues.