Cyberpunk Won’t Launch | Start-Up Fix Playbook

If the game refuses to start, don’t panic. Most cases trace back to corrupt files, outdated drivers, launchers stuck in the background, or a mod that no longer matches the current build. This guide gives you clean, step-by-step fixes for Windows PCs, Steam Deck, and consoles, with quick checks first and deeper repairs after. Work through the steps in order; you’ll save time and avoid reinstalling when a simpler tweak would do.

Game Fails To Launch On PC: Fast Checks

Start with the items that solve the widest slice of start-up issues. These take minutes and won’t risk your saves.

Symptom	Likely Cause	Quick Fix
Play button flickers, no window opens	Corrupt install or stale launcher cache	Run a file integrity check in your store launcher
Black screen, audio never starts	Overlay hook or capture tool conflict	Turn off Steam/Discord overlays; close capture apps
Crash at splash logo	Old GPU driver or mismatched mods	Update GPU driver; start the game with mods disabled
“Game already running” message	Hung background process	End cyberpunk*.exe in Task Manager; reboot if needed
Launcher opens then vanishes	Missing DirectX/VCRedist files or antivirus block	Repair redistributables; add an AV exception for the game

Verify And Repair The Installation

Corrupted assets stop the executable before a window appears. A file scan restores the original data without touching saves. On Steam, use the “Verify integrity of game files” action in the game’s Properties → Installed Files. CDPR’s guide confirms this resolves issues like launch failures and glitched assets. Link: verify files on Steam. CDPR’s own page: verify integrity page.

Kill Background Hooks And Overlays

Game overlays and injectors can block the renderer at launch. Disable the Steam overlay for this title, exit Discord’s in-game overlay, close GeForce Experience in-game overlay, Rivatuner/MSI Afterburner, ReShade, and any FPS counters. Then try a clean launch. Discord has documented reliability issues with its overlay in some games; turning it off is a quick win. Link: Discord overlay note.

Start Clean: No Mods, No REDmod

Large updates change the scripting backend. Old mods can keep the app from reaching the main menu. Launch straight from the platform library, not through a mod manager. Remove or move all mod files from the game folders and disable REDmod packs until the game boots. Once you’re in, re-enable packs one by one to spot the offender.

Update GPU Drivers And Windows

Cyberpunk 2077 leans on DirectX 12 and recent shader compilers. Install the newest WHQL driver from NVIDIA, AMD, or Intel Arc. Run Windows Update, reboot, and try again. If you use laptop switchable graphics, force the high-performance GPU in vendor control panels for the cyberpunk executable.

Check Minimum Specs And API Requirements

Since Update 2.0, the game’s baseline moved up. The PC build requires DirectX 12, and older cards without full DX12 support won’t launch. CDPR publishes the current spec table here: system requirements. If you sit near the minimum, close browsers and heavy background apps before pressing Play.

Clear Launchers And Cached Data

Stuck launchers look like instant quits after the Play button. Fully exit Steam/Epic/GOG in the tray, relaunch the store client, then run the game again. If the store client still misbehaves, reboot the PC to clear any ghost processes and shader cache locks.

Repair Redistributables

Failure to load Visual C++ or DirectX components can block start-up. In the Cyberpunk 2077\_CommonRedist or redist folders, rerun installers for VC++ and DirectX. Reboot afterward.

Try A Safe Boot

Boot Windows with non-Microsoft services disabled. If the game runs in that state, a third-party overlay, RGB tool, or capture app is the culprit. Re-enable services in small batches until the break reappears.

Launch Options That Help With Troubleshooting

Use the platform’s “Set launch options” box to test a cleaner start:

• -windowed or -noborder to avoid resolution hand-offs that hang at boot.
• -skipStartScreen to shave a step while testing.
• Remove any leftover custom flags from old guides.

When The Game Opens Then Crashes At Logo

This pattern often points to driver shader cache or broken config files. Steps:

1. Delete the shadercache for your GPU in its control app if available, then reboot.
2. Back up and delete the game’s local config in %userprofile%\Saved Games\CD Projekt Red\Cyberpunk 2077 (keep saves). The game will rebuild configs on next launch.
3. Run another file integrity check in your store launcher.

Store-Specific Repair Paths

Steam

Run the file scan again after any crash or driver change. Steam’s help page documents the exact path: Properties → Installed Files → Verify. Link: Steam verify steps.

GOG

In the GOG Galaxy client, open the game page → Manage Installation → Verify / Repair. Close Galaxy from the tray and relaunch if the scan won’t start.

Epic Games

Click the three dots next to the title → Manage → Verify. If the Play button does nothing, sign out of the launcher, sign back in, and try again.

Console: PS5 And Xbox Fixes That Work

Console launch failures are usually cache or database issues. Power cycling and a database refresh clear most cases. Sony documents Safe Mode steps, which include “Clear Cache and Rebuild Database.” Link: PS5 Safe Mode steps. On Xbox, a full power cycle clears stale cache and often restores normal launches. Link: Xbox power cycle.

PS5 Checklist

• Close the game, highlight the tile, press Options → Check for Update.
• Settings → Storage → Rebuild database via Safe Mode if stutters or launch stalls persist.
• Restore licenses if the Play button is locked behind a license error.

Xbox Series X|S Checklist

• Press and hold the front power button until the unit turns off, unplug for 60 seconds, then start again.
• Check for title updates in “Manage game and add-ons.”
• Move the title to internal storage if it lives on a slow external drive.

Deep Fixes When The Basics Don’t Stick

If quick fixes don’t lift the game to a clean start, take these deeper steps.

Clean Out Old Mods Fully

Remove all files under archive\pc\mod, any REDmod packs, and script edits under r6\scripts. Delete any leftover x64 binaries you added manually and let the platform repair them through a verify pass. Then launch from the platform library without a mod manager.

Reset Graphics Settings To Defaults

Edits to user settings can break on a new patch. Delete or rename the user.settings file inside the Cyberpunk folder in Saved Games. The title will recreate a fresh file on launch.

Run As Administrator And Disable Fullscreen Optimizations

Right-click the executable in ...Steam\steamapps\common\Cyberpunk 2077\bin\x64, open Properties → Compatibility, tick “Run this program as an administrator” and disable fullscreen optimizations. This removes a few Windows hand-offs that can hang on older builds.

Free Space And Check Drive Health

Keep 20–30 GB free on the game drive so shader caches and updates can write. If your SSD is near full or throwing I/O errors, move the title to a faster or healthier drive.

Reinstall The Store Client

When launcher files break, the game can’t start even if the install is fine. Uninstall and reinstall the store app, then verify the title again. Keep your library folders pointed to the same disk so you don’t redownload everything.

Performance Headroom To Avoid Near-Boot Crashes

Being right at the minimum spec can cause timeouts during shader compilation. Lower the desktop resolution before launch, close web browsers, and cap background updaters. On laptops, plug into AC power and set the system to a high-performance power plan so clocks don’t droop at the splash screen.

Known Conflicts To Watch

• Game overlays and injectors (Steam overlay, Discord overlay, FPS counters, capture hooks).
• Obsolete mod scripts after a major patch.
• Old GPU drivers, especially across big Windows updates.
• Antivirus blocking the executable on first run; add the game folder to the allow-list.

PC Launch Troubleshooting Matrix

Work through the grid top-to-bottom; each line addresses a common stall right before the menu.

What You See	Do This Next	Why It Works
Play button does nothing	Exit the store app fully, relaunch, then verify files	Clears hung launchers and restores missing assets
Black screen then desktop	Disable overlays; update GPU driver; reboot	Removes hooking conflicts and shader crashes
Crash at RED splash	Remove mods; rebuild configs; run file check	Aligns scripts and config with the current build
Only runs as admin	Keep admin on; disable fullscreen optimizations	Bypasses a few Windows window-manager hand-offs
Title runs once, then fails	Reboot; clear GPU shader cache; verify again	Removes stale caches created on first boot

When A Patch Changes The Ground Rules

Major updates can raise CPU/GPU baselines, retire old APIs, or reshuffle shaders. CDPR has an updated PC spec note tied to the expansion cycle that spells out the DX12 requirement and upgraded targets; if your hardware is well below those lines, launch success will be inconsistent even after repairs. Link: PC requirements update.

Steam Deck And Portable PCs

On Deck, toggle between Proton versions if the app stalls at the logo. Clearing shader cache and verifying files from the desktop mode clears many misses. Keep enough free space on the internal SSD; shader data grows after patches.

Clean Reinstall As A Last Step

If none of the steps above push the game to the menu, back up saves from the Saved Games folder, uninstall the title, delete any leftover install folders, then install fresh. After the initial boot, add mods back one at a time with fresh versions that match your current patch.

Quick Reference Checklist

• Run a file integrity scan in your launcher.
• Disable overlays and close capture apps.
• Update GPU drivers and Windows; reboot.
• Start without mods or REDmod packs.
• Repair VC++/DirectX redistributables.
• Reset configs; test windowed launch flags.
• Power cycle consoles; rebuild database on PS5; clear cache on Xbox.

You Got To The Menu—Now Make It Stick

Once the title opens cleanly, keep it that way. Leave overlays off, update drivers monthly, and add new mods only when you can confirm patch parity. Keep 20 GB free on your game SSD so shaders and updates can write without stalls at the next boot.