Fix Microsoft Train Simulator crashes: install update 1.2, use Windows compatibility settings, test stock content and isolate faulty add-ons.
Microsoft Train Simulator usually crashes because its 2001-era executable conflicts with modern Windows, its saved display settings are invalid, an add-on is missing or corrupt, or a heavy route exceeds the game's practical limits. Install the official update, test default content, apply compatibility settings, then isolate add-ons in that order.
What does the crash point tell you?
When Microsoft Train Simulator crashes is often the best clue to the cause. MSTS is distinct from Train Simulator Classic, so fixes and add-ons intended for the newer simulator should not be applied to it.
| When it crashes | Likely cause | Best first test |
|---|---|---|
| Before the main menu | Compatibility, permissions, display configuration or damaged core files | Patch the game and check train.exe compatibility settings |
| While selecting a train or consist | Broken consist or missing .eng/.wag file | Select an original locomotive and consist |
| While loading an activity | Missing rolling stock, service, path, traffic or route asset | Try Explore Route with default stock |
| When the cab or sound loads | Invalid cab-view or sound alias | Test the same route with an original MSTS locomotive |
| At one location on a route | Damaged tile, shape, texture or overloaded scene | Lower detail and test another activity on that route |
| After changing the installation | Faulty add-on, overwritten shared file or obsolete saved activity | Undo the latest change and start the activity again |
How do I fix Microsoft Train Simulator crashes?
Work through these fixes in order, testing the same default route and train after each change. Applying several unrelated tweaks at once makes the real fault much harder to identify.
- Back up the installation. Preserve the MSTS folder and any add-on installers before patching, removing content or editing the registry. A backup is particularly important if routes have modified shared files.
- Install the official update. Apply the official Microsoft Train Simulator 1.2 update to the actual game directory. Run the base simulator once after updating and before installing more content.
- Establish a stock-content baseline. Load an original route with an original locomotive, preferably through Explore Route or a simple default activity. If that works, Windows and the core installation are probably usable; the fault is more likely to be a route, consist, activity, cab or sound package.
- Set compatibility on the real executable. Open the properties for
train.exe, not merely the desktop shortcut. Try Windows XP compatibility, disabling full-screen optimisations and running as administrator, testing after each change. Our MSTS setup checklist for Windows 11 covers protected folders, display problems and other modern-Windows issues in more detail. - Reduce the display load. Select a standard resolution offered by MSTS, lower scenery and object detail, and disable overlays or recording utilities while testing. If the crash started after changing monitor, graphics card or resolution, the stored display configuration may no longer match the hardware.
- Test without recent add-ons. Undo the most recently installed route, train, consist or activity using its original backup or installer. Do not randomly delete shared files from
GLOBAL; several routes may depend on them. - Check security software. Review whether an MSTS executable or add-on file was quarantined. Restore only files from a source you trust, and do not install miscellaneous DLL packs from the web as a substitute for diagnosing the missing component.
- Reset the MSTS configuration only if needed. A crash before the menu, especially after a graphics change, can come from obsolete registry values. Export a backup first and follow our step-by-step MSTS registry repair procedure; never delete unrelated registry branches.
Why does MSTS crash only on one route or activity?
A crash limited to one route or activity almost always points to content rather than Windows. MSTS activities reference consists, services, traffic, paths and rolling stock by name, so one missing dependency can stop the load even when the route itself is sound.
- Route works in Explore Route: inspect the failing activity and its required consists, services and traffic.
- Route never loads: suspect missing route assets, an incorrect installation order or damage to shared route files.
- One locomotive fails: check its cab and sound aliases as well as the referenced
.engand.wagfiles underTRAINS\TRAINSET. - Crash began after editing content: start a fresh activity rather than resuming an old save. Saved states can retain references that no longer match the revised consist or route.
- Only a dense activity fails: lower display settings or try a lighter activity. Extra physical RAM does not remove every limitation of the old MSTS executable.
A common mistake is to remove a train folder without removing or repairing the consists that reference it. This leaves files in TRAINS\CONSISTS pointing to rolling stock that no longer exists.
Should I use Open Rails instead of the original MSTS program?
Use Open Rails when running compatible MSTS routes and trains reliably on a modern computer matters more than reproducing the original executable exactly. It can avoid many legacy display and operating-system problems, and our Open Rails installation and MSTS content guide explains how to point it at an existing installation.
Open Rails is not an invisible patch for train.exe. Physics, signalling, activities and add-on behaviour can differ, and defective content may still fail. Keep the original simulator when an activity or utility specifically requires original MSTS behaviour.
When is a clean reinstall necessary?
A clean reinstall is justified when default routes also crash after patching and compatibility checks, or when shared folders have been overwritten beyond reliable repair. Uninstalling alone may leave add-on files behind, so rename the old game directory before installing a fresh copy.
Install to a simple writable location such as C:\MSTS rather than a protected system folder, apply update 1.2, and test untouched default content. Restore routes and trains in small batches, testing between each batch; copying the entire old installation back at once usually restores the original fault as well.