Sandustry Error 0xc0000142 Fix: Won't Launch, Step-by-Step

Confirm the Symptom

After double-clicking to launch Sandustry, Windows pops up "The application was unable to start correctly (0xc0000142)." — the game window never appears. 0xc0000142 is a Windows application-init failure code: the process dies during the load stage, usually unrelated to the game's own design and instead an issue with the runtime environment (corrupt files, an incompatible mod, drivers, or missing runtimes).

Fix Steps (Ordered by Probability)

① Verify Game File Integrity (Steam first choice)

Generic fix, but highest hit-rate for this code: in Steam, right-click Sandustry → Properties → Installed Files → Verify integrity of game files. File corruption from interrupted downloads/updates is the top cause of 0xc0000142; verification auto-restores corrupt files, far faster than a reinstall. GOG Galaxy has a "Verify/Repair" function.

② Remove / Check All Mods

The most-reported community trigger COMMUNITY: a Fluxloader-style mod loader mismatched to the game version crashes at init with this code. Official confirms physics-engine updates break old mods VERIFIED — especially after the v0.5.x hotfixes. Empty the mods folder for a clean vanilla launch; once in, restore only version-compatible mods per the Mod Install Guide.

③ Update GPU Drivers

Generic fix. An outdated GPU driver can trigger this code during DirectX init. Sandustry's floor is DirectX 11 (GTX 550 Ti / HD 7750 class) VERIFIED — a very low bar, so "driver too old" is more likely the culprit than "GPU too weak." Update via NVIDIA / AMD / Intel or their official tools.

④ Reinstall DirectX 11 Runtime & VC++ Redistributable

Generic fix. Corrupt DirectX end-user runtime and Visual C++ Redistributable (install both x64 and x86) are classic causes of 0xc0000142. Reinstall from official Microsoft channels, then reboot. This step "reinstalls the runtime, not the game" — many get the order backwards.

⑤ Try the GPU-Overlay Launch Option (new in v0.5.3)

From v0.5.3, the dev added a GPU-overlay launch option specifically to bypass overlay-related launch crashes COMMUNITY (community-sourced patch notes; details in v0.5.3 Notes). Pick that launch mode in Steam launch options and retry. Also temporarily disable Discord / GeForce Experience / MSI Afterburner overlays to rule out conflicts.

⑥ Antivirus / Firewall Allowlist

Generic fix. Some security software blocks the game during process init, matching this code. Add Sandustry's install folder and executable to your antivirus and Windows Firewall allowlists, then retry.

⑦ Xbox App (Game Pass) Repair & Reset

Game Pass has no Steam "verify integrity"; the equivalent is: Windows Settings → Apps → Installed Apps → Sandustry → Advanced options → Repair; if that fails, Reset (reset clears local config but not cloud saves). Game Pass inclusion and version differences in the Game Pass Guide.

FAQ

What does this code mean?

"Application init failed" — the program crashed during Windows load, before reaching the game's own code. So it's almost always an environment problem (files, drivers, runtimes, mods, security software), not a save or settings problem.

Do these steps apply to Game Pass?

Yes. ②③④⑤⑥ are identical; ① becomes Xbox App "Repair/Reset" (step ⑦). Game Pass and Steam run the same EA build VERIFIED.

Does reinstalling the game help?

It helps but inefficiently. Steam's file verification (①) already covers ~90% of "reinstall fixes it" cases. What's worth reinstalling is the DirectX / VC++ runtime (④), not the game itself.

Everything failed — now what?

From v0.5.3 the game writes a more detailed crash log COMMUNITY — bring the log and your spec to the official Discord or official Reddit. EA launch-compat issues usually get fixed in later hotfixes.

Baseline 2026-08-17 · data changes with EA builds