Begin crash recovery by protecting progress. PATCH 1.0 (1558) fixed save corruption and failure to enter missions after a crash, so update before applying community workarounds. Do not delete a profile or copy a Demo executable path as a first step.
2950790, Windows public 1.0, checked 2026-08-09. Steps are reversible and conservative; device-specific fixes require matching evidence.Classify the symptom
Record whether the game fails before a window appears, shows a black screen, crashes at menu, crashes entering a named mission, freezes during a station interaction, or closes after a shot/newspaper. Note whether audio continues and whether Windows reports the application as unresponsive.
One exact transition is more useful than “random crash.” Include the last interaction and whether a prior crash already occurred in the same session.
Update and verify the public build
Restart Steam, install all queued IRON NEST updates, and compare the latest official announcement. Verify game files through Steam. Restart Windows and launch with ordinary Store settings.
Remove custom launch options, compatibility flags, mods, injectors, and unsupported overlays during diagnosis. The checked public game has no established Workshop implementation.
Preserve save state
Let Steam Cloud settle before repeated launches on another device. Record last good mission and newspaper. If the game now enters missions after PATCH 1.0 (1558), finish a safe transition and exit normally.
Do not publish or delete an unverified save directory. The Save Support guide explains Cloud conflicts and evidence preservation.
Black screen checks
Wait briefly for first shader/content loading, then test a normal window/display transition using current settings if reachable. Disconnect unusual external displays, update a stable GPU driver, and return resolution/preset to defaults. Check whether the Store minimum requirements are met.
Avoid registry edits or downloaded DLL replacements. If audio plays behind black video, report display mode, monitor/GPU, driver, and whether a screenshot captures content.
Frozen mouse or controls
Release any focused station and open/close pause normally. PATCH 1.0 (1558) improved mouse movement after loading the menu or a mission. Test with one controller/input device and remove competing virtual devices.
A mechanically locked lever is not a crash. Verify loading, breech, arming, and objective prerequisites before filing an input failure.
Driver and resource isolation
Install a stable vendor GPU driver, close capture/overlay tools, and ensure adequate free storage. Monitor memory and temperatures without bypassing safety limits. Test the same scene at official low settings.
If the crash begins only with one overlay or peripheral removed/restored, document that correlation. Do not claim causation from one attempt.
Produce a reproducible report
Include AppID, patch, Windows version, CPU/GPU/RAM, driver, display setup, input device, exact mission/station, last five actions, frequency, file-verification result, and whether a crash affected later mission entry. Attach logs only through a trusted official channel after reviewing their contents.
For Deck, include SteamOS and Proton and use Steam Deck Support. Do not mix a forced Proton symptom with native Windows reports.
Confirm recovery rather than one launch
After the game opens, enter a known mission, interact with one station, exit through normal flow, relaunch, and confirm progress. A successful menu launch alone does not prove the crash or post-crash save issue is resolved. Keep the original reproduction notes until this short recovery cycle passes twice.
If the crash disappears, restore optional overlays, peripherals, or custom settings one at a time. The first reintroduced state that reliably restores the fault is useful evidence, but test it twice before blaming the component. Leave unsupported file replacements and broad system changes out of this process; they make rollback and attribution harder.
Keep the stable configuration written down so later driver or game updates can be compared against a known working baseline.
If Windows creates a crash timestamp or event entry, note the time and module name without pasting unrelated system records. That identifier helps correlate repeated failures while keeping the public report focused and privacy-safe.