R.E.P.O. Crashing: How to Fix Crashes, Black Screens and Launch Failures
A R.E.P.O. that will not start is almost always one of a handful of problems, and they have a clear order of likelihood. This guide works through them from the fastest check to the last resort.
Quick Answer
If R.E.P.O. is crashing on startup, disable your mods first — move everything out of BepInEx/plugins and launch vanilla. Outdated mods after a game update are the most common cause by a wide margin. If you have never modded the game, verify integrity of game files in Steam, then update your graphics driver. Those three steps resolve most launch crashes and black screens. Only then move on to launch options, administrator mode and overlays.
Why R.E.P.O. Keeps Crashing
Four causes cover the overwhelming majority of R.E.P.O. crash reports. Recognising which one matches your symptoms saves you working through fixes that were never going to apply.
Outdated mods after a patch
The most common reason R.E.P.O. will not launch. Every major update changes the game code underneath BepInEx, so mods built against the old version fail on load. At the 0.3.0 update, modded installs hung on the static black startup screen with the BepInEx console full of errors.
Corrupted or incomplete game files
An interrupted download, a failed patch, or an antivirus that quarantined part of the install leaves R.E.P.O. missing files it needs at startup. The usual symptom is an instant drop back to the desktop with no error window. Steam repairs this on its own in a couple of minutes.
Old or broken GPU drivers
R.E.P.O. is a Unity game and leans on your graphics driver from the first frame. A driver several releases behind, or one installed badly over an older version, produces black screens, endless loading and crashes seconds after the logo. This resolves the most reports after mods.
Overlays and background software
Overlays inject themselves into the game process, and several at once is a common trigger for launch failures. Discord, Steam, GeForce Experience and hardware monitors are the usual suspects in community reports. Heavy background apps matter too, simply by taking memory the game needs during load.
How to Fix R.E.P.O. Crashing on Startup
Work down this list in order and test the game after each step. The order is deliberate — the cheapest and most frequently successful fixes come first, so most people never reach the bottom.
Restart Steam, then restart Windows
Quit Steam completely from the system tray rather than closing the window, then start it again. If the game still will not open, reboot the PC. A stale Steam process or a pending Windows update holding a file lock explains a surprising share of one-off launch failures.
Disable every mod
If you have ever installed a mod, do this before anything else. Open the R.E.P.O. install folder, go into BepInEx/plugins, and move everything inside it to a folder somewhere else on your drive. You can leave BepInEx itself in place. Launch the game vanilla — if it starts, you have your answer and you just need to wait for the mods to update.
Verify integrity of game files
In Steam, right-click R.E.P.O. in your Library, choose Properties, open Installed Files, and click Verify integrity of game files. Steam checks every file against its manifest and re-downloads anything damaged or missing. Let it finish completely — interrupting the scan leaves the install in the same broken state you started with.
Update your graphics driver
Get the current driver directly from NVIDIA, AMD or Intel rather than relying on Windows Update, which often lags well behind. If you are already on the newest driver and the crashing began right after you installed it, the reverse applies: roll back to the previous release. Use the clean install option where offered.
Run as administrator
Right-click REPO.exe in the install folder, open Properties, then the Compatibility tab, and tick "Run this program as an administrator". While you are there, ticking "Disable fullscreen optimizations" resolves a class of black-screen-on-launch problems on Windows 10 and 11. Apply, close, and launch through Steam as normal.
Close overlays and background apps
Turn off the Steam overlay in the game's properties, disable the Discord overlay in Discord settings, and shut down any hardware monitor or capture tool. Then close browsers and anything else eating memory. Add them back one at a time afterwards if you want to know which one was responsible.
Try a launch option
Forcing a specific renderer or starting in a window gets past a lot of display-related launch failures. Steam Library, right-click the game, Properties, General, Launch Options — enter one argument, test, then clear it before trying the next. The table further down lists the arguments worth trying and what each one does.
Back up your saves, then test a fresh one
A damaged save can hang the game when you load it, even though the menu works fine. Copy the whole save folder somewhere safe first — never delete without a backup — then start a brand new run. If the new run works and the old one does not, the save is the problem rather than the install.
Reinstall as the last resort
If nothing above works, uninstall through Steam, delete anything left in the install directory (mod folders in particular survive an uninstall), and download the game again. Your saves live elsewhere on the drive, so a reinstall does not touch progress, but take the backup anyway.
Black Screens, Freezes and Other Crash Symptoms
The exact way R.E.P.O. fails narrows the cause considerably. Find the row that matches what you are seeing and start there instead of at step one.
Crashing After an Update? Disable Mods First
If the game launched fine before a patch and refuses to open afterwards, mods are the prime suspect and you can confirm it in about a minute. You do not need to uninstall anything permanently.
- In Steam, right-click R.E.P.O. → Manage → Browse local files to open the install folder.
- Open the BepInEx folder, then the plugins folder inside it.
- Move everything in plugins to a temporary folder elsewhere on your drive — do not delete it.
- Launch the game. If it now reaches the menu, an outdated mod was the cause.
- Add mods back one at a time, launching between each, until the crash returns and identifies the culprit.
If you installed through Thunderstore Mod Manager, you can do the same thing from the My Mods tab by toggling mods off, and launch through the unmodded button to test. Either way, the mod has to be updated by its author before it will work on the new game version — there is no fix on your end beyond waiting.
Launch Options That Fix R.E.P.O. Startup Crashes
R.E.P.O. is built in Unity, so it accepts Unity's standard command-line arguments. Add one at a time in Steam under Properties → General → Launch Options, test it, and clear the box before trying the next — stacking untested flags only makes it harder to tell what helped.
-force-d3d11Forces the DirectX 11 renderer. The first thing to try on older GPUs or any card where DirectX 12 is unstable.-force-d3d12Forces DirectX 12 instead. Worth testing if DirectX 11 crashes on a modern card, since the failure sometimes runs the other direction.-force-vulkanUses Vulkan rather than DirectX. A useful third option when neither DirectX mode gets you to the menu.-screen-fullscreen 0Starts the game windowed. Fixes black screens caused by a bad saved resolution or a multi-monitor setup, and lets you correct the display settings from inside the game.-screen-width 1280 -screen-height 720Forces a safe resolution at startup. Pair it with the windowed flag if the game launched once at a resolution your monitor cannot display.One warning about advice you will find elsewhere: several sites recommend editing a config file under a path containing "Saved\Config\WindowsNoEditor". That folder belongs to Unreal Engine games and does not exist for R.E.P.O. Do not go looking for it — the game keeps its data under the semiwork folder described below.
Back Up Your Saves Before You Troubleshoot
A corrupted save can hang the game at the loading screen while the rest of the install is perfectly healthy. Testing for that means starting a new run — but copy your existing saves somewhere safe first, because R.E.P.O. deletes a save automatically when a whole team wipes and you do not want to lose progress to a diagnostic step.
Paste that path into the Run dialog (Win + R) or the File Explorer address bar. Each run is a folder named REPO_SAVE_XXXXXXX. Copy the whole saves folder to your desktop, then start a fresh game. If the new run loads and the old one still hangs, the save was the problem — and you still have the backup to try restoring later.
Related R.E.P.O. Guides
Frequently Asked Questions
Why does my R.E.P.O. game keep crashing?
In most reports the answer is mods that have not been updated for the current game version, followed by corrupted game files and outdated graphics drivers. Those three account for the bulk of launch failures. Crashes that happen mid-run rather than at startup point elsewhere: memory pressure from background applications, or a machine running hot under sustained load. Work out which of the two patterns you have first, because the fixes barely overlap.
R.E.P.O. worked yesterday and crashes after the update — what changed?
A major patch changes the game code that mods hook into, so every mod you have installed is built against a version that no longer exists, and the game fails where it tries to load them. This was visible at the 0.3.0 update, where modded installs stopped at the static startup screen. Move everything out of BepInEx/plugins and launch vanilla. The mods work again once their authors publish updated builds.
How do I fix the R.E.P.O. black screen on startup?
Check whether you can hear audio. If sound is playing, the game is running and only the display is wrong: add -screen-fullscreen 0 to the launch options to force a window, then fix the resolution in the settings menu. If there is no sound either and the screen shows static, mods are the likely cause. A silent black screen with no static usually clears after verifying game files and updating the graphics driver.
Does verifying game files delete my save?
No. Steam only checks the files in the install directory, and R.E.P.O. keeps saves separately at %USERPROFILE%\AppData\LocalLow\semiwork\Repo\saves. Verifying is one of the safest steps in this guide and there is no reason to skip it. It is also worth knowing that a full reinstall leaves that folder alone too — but back it up before either operation, because a backup you already have costs nothing.
Could my PC just be too weak to run R.E.P.O.?
Possible, but it rarely explains a crash at startup. Hardware that falls short of the requirements normally shows up as poor frame rates and stuttering in a game that does run, so a machine that cannot launch at all is more often a software problem. Check your specs against the requirements page, and if they clear the bar, keep working through the fixes here rather than blaming the PC.
The game only crashes when I join a friend — is that different?
Yes, and it points at mods again. Gameplay-altering mods have to match across the lobby: if the host runs a different set or version than you do, the join fails or the client drops out. Have everyone compare their mod list and versions, then test a lobby with mods disabled on every machine. If the vanilla lobby holds, the mismatch is confirmed.
Should I add R.E.P.O. to my antivirus exceptions?
Worth trying if Steam briefly shows the game as running and then returns to the Play button. Security software sometimes quarantines a game executable or a BepInEx file it does not recognise, which produces exactly that symptom. Add the R.E.P.O. install folder as an exclusion rather than switching protection off entirely, then verify game files afterwards to restore anything already removed.
Nothing worked — what now?
Reinstall after deleting any leftovers in the install directory, since mod folders survive a normal uninstall. If a clean install still crashes, gather details before asking for help: your GPU and driver version, whether you have ever installed mods, the exact point at which it fails, and whether audio plays. Post those on the Steam discussions or the R.E.P.O. subreddit, since that information is what makes a reply useful.