What is the safest first step for crashes?

Verify the integrity of the game files in Steam. This checks that files are installed correctly and replaces corrupted files if needed.

Are there official known issues?

Yes. The developers posted known issues for the Early Access launch build (including a movement lock related to certain movement keybinding changes).

My character can’t move after changing keybinds—what do I do?

Restore default movement keybindings. An official note suggests using arrow keys for AZERTY instead of remapping movement keys.

What if verifying files doesn’t help?

Try reducing conflicts (overlays, background apps), reboot, and use Windows Program Compatibility Troubleshooter if the game still won’t behave.

Where should I report bugs?

Use the official Steam discussions / bug-report channels referenced by the developers, and include steps to reproduce plus your PC specs.

Troubleshooting • PC/Steam

Crash Fixes & “Won’t Launch” Checklist (StarRupture)

This page prioritizes safe, low-risk fixes first (no sketchy downloads, no registry voodoo). StarRupture is in Early Access, so some crashes are simply “known issues” awaiting patches.

Start Here (Safest)

Verify game files in Steam (fixes missing/corrupt files).

Known Issues

Check official launch notes first. Some “bugs” have specific workarounds.

Still broken?

Use Windows compatibility tools, reduce conflicts, and then report with repro steps.

Step 1: Verify integrity of game files (Steam)

Steam has a built-in “verify integrity” feature that checks whether the game’s files are installed correctly and reacquires missing/corrupt files if needed.

Steam Library → right-click StarRupture → Properties.

Open Installed Files (or Local Files) → click Verify integrity of game files.

Let it finish, then relaunch the game.

Step 2: Check official known issues (Early Access launch build)

Important: if your problem matches a known issue, don’t waste an hour “fixing Windows.” Use the dev workaround and move on.

Movement locked after keybind changes

Official notes warn that changing movement keybindings may result in being unable to move.

Fix: restore default movement binds.
Workaround mentioned: for AZERTY, use arrow keys rather than remapping movement keys.

If your issue isn’t listed

Still do Step 1 first, then continue to Step 3 and Step 4 below (conflict reduction + Windows tools).

Step 3: Reduce common conflicts (low-risk)

The goal is to remove variables. Do one change at a time so you know what worked.

Reboot PC (simple, but it clears stuck drivers and background hooks).
Close background overlays/capture tools (if you use them) and try again.
Temporarily disable aggressive antivirus “game mode” blocking (if applicable), then retry.

Step 4: Windows Program Compatibility Troubleshooter

Windows includes a built-in Program Compatibility Troubleshooter path in Settings. Use it if the game launches but behaves strangely or fails immediately.

Windows Settings → System → Troubleshoot → Other troubleshooters → Program Compatibility Troubleshooter.
Follow prompts, test, and revert if it makes things worse.

Bug report template (copy/paste)

Title: [Crash / Freeze / Black Screen] + when it happens

Build/Date: Steam Early Access + today’s date

Repro steps: 1) … 2) … 3) …

Expected: …

Actual: …

PC specs: CPU / GPU / RAM / OS / Driver version

Logs: (attach if available) • Did you verify files? Yes/No

FAQ

Should I reinstall immediately?

Try verify-files first. Reinstall is usually a “last resort” when verification and conflict reduction fail.

My keyboard controls broke after rebinding—am I cooked?

Not necessarily. Official notes specifically mention restoring default movement binds; start there.

Will this page be updated?

Yes—known issues and fixes change fast in Early Access. Keep a “last updated” stamp visible.