How do I fix “Steam must be running” in FSX: Steam Edition?
Fix “Steam must be running to play this game” in FSX: Steam Edition, including stuck launches, permissions, files and licence checks.
FSX: Steam Edition shows “Steam must be running to play this game” when fsx.exe cannot establish a valid session with the Steam client. Start FSX from Steam while signed in online, close stale processes, remove mismatched administrator settings, then verify the game files. Those four checks fix most legitimate installations.
This advice applies to Microsoft Flight Simulator X: Steam Edition on Windows. Boxed FSX does not require Steam, so seeing this message with a boxed installation usually means the wrong executable or a modified launcher is being used.
How do I fix the FSX “Steam must be running” error?
A complete client restart followed by a Steam Library launch is the quickest reliable starting point. Test FSX after each step; changing everything at once makes the original cause harder to identify.
- Close FSX and Steam completely. Exit FSX, use Steam’s Exit command and check Task Manager for a remaining
fsx.exeor stuck Steam process. End the stale task, or restart Windows if several Steam components refuse to close. - Start Steam online and use its Play button. Sign into the account that owns FSX: Steam Edition or has authorised access to it. Leave Offline Mode while diagnosing the problem, open the Steam Library and select Play from the FSX entry.
- Remove old shortcuts and launch options. Clear any custom FSX launch command in the game’s Steam properties. If Steam’s Play button works but a desktop shortcut does not, delete that shortcut and create a fresh one through Steam. Do not launch a copied
fsx.exestored outside the FSX installation directory. - Match the administrator and compatibility settings. Check the Compatibility properties for Steam and the installed
fsx.exe. Normally, Run this program as administrator and forced Windows compatibility mode should be disabled for both. If a trusted legacy add-on genuinely requires elevation, run Steam and FSX at the same privilege level for the test rather than elevating only one of them. - Verify the installed files. Open FSX’s Properties in Steam and use Verify integrity of game files under Installed Files; older Steam clients may place it under Local Files. This restores missing or altered files, including legitimate Steam API components. Back up intentional edits to default files first, or follow our FSX file-verification and repair procedure for the relevant cautions.
- Inspect security-software quarantine. Check whether
fsx.exe,steam_api.dllor another file inside the Steam library was blocked. Have Steam verify and redownload the original file, then permit it only after confirming that it belongs to the genuine installation. Do not disable protection for the whole drive or download a replacement DLL from an unrelated source. - Refresh the Steam account session. Sign out, restart Steam, allow any client update to finish and sign back in while online. If other owned Steam games also fail their licence checks, the fault is with the client session, account or connection rather than FSX itself.
Offline Mode may work once Steam has cached a valid entitlement, but it is a poor test for this error. Establish one successful online launch before trying FSX offline.
What if Steam is already running?
A visible Steam window does not prove that FSX can communicate with a valid client session. “Steam client must be running to play this game” is the same basic failure, and the launch pattern points to the next check.
| What happens | Likely cause | Best next action |
|---|---|---|
| Steam’s Play button works, but an old shortcut fails | The shortcut targets the wrong executable or contains obsolete options | Replace it with a Steam-created shortcut |
| Both the shortcut and Play button show the error | Stale processes, mismatched privileges or altered files | Restart both programs, remove compatibility settings and verify FSX |
| Only an add-on launcher produces the error | The launcher starts FSX before Steam or runs at a different privilege level | Open Steam first and match the launcher’s elevation to Steam and FSX |
| Other Steam games also fail validation | Steam client, account or connectivity problem | Restart and update Steam, then sign in online |
| The message disappears but FSX immediately closes | A separate simulator, configuration or add-on crash | Use our checks for an FSX: Steam Edition startup crash |
Why is Steam stuck on “Launching executable”?
When Steam remains on “Launching executable”, first determine whether Windows actually started fsx.exe. Repeatedly pressing Play will not clear a hung process.
| What you find | What it means | What to do |
|---|---|---|
| A Windows installer, prerequisite or User Account Control prompt is open | Steam is waiting for that process | Complete or cancel the visible prompt, then try once more |
fsx.exe appears in Task Manager but no simulator window opens | FSX started but is hanging during initialisation | End the task and launch the stock simulator without an add-on launcher. If it eventually opens, investigate FSX startup delays caused by add-ons, scanning or unavailable drives |
| Steam quickly changes back from Launching to Play | The executable started and then terminated | Treat it as an FSX startup crash rather than a Steam-running error |
No fsx.exe process appears | The executable is blocked, missing or replaced by a custom launch target | Clear Steam launch options, inspect security history and verify the files |
| Old FSX or Steam processes remain after closing | A stale process is blocking the next launch | Exit Steam fully and restart Windows |
Can I launch FSX directly from fsx.exe?
For diagnosis, launch FSX: Steam Edition through Steam rather than opening fsx.exe directly. Direct execution can work when the client session and installation are healthy, but it can also use the wrong copy or bypass the launch context needed by an add-on.
The Steam installation normally sits in a library path ending with steamapps\common\FSX; the drive and parent folders vary. Never move only fsx.exe, merge boxed and Steam folders, or copy Steam API files between installations.
A mistake we see constantly is an old shortcut or add-on installer still pointing to boxed FSX. If the two editions coexist and Windows keeps selecting the wrong path, use our guidance for checking and repairing FSX installation-path registration.
What does “Steam is not launched” or “Online Fix” mean?
“Steam is not launched” is not the usual wording from an unmodified English installation of FSX: Steam Edition. It often comes from a third-party launcher, replaced executable or altered Steam API file rather than the stock simulator.
If the copy is legitimate, remove the custom launcher and verify FSX through Steam to restore the original files. Aircraft and scenery add-ons should not require you to replace fsx.exe or steam_api.dll.
Search results describing an “Online Fix” may refer to unofficial tools intended to imitate Steam services or bypass licence checks. We do not recommend those files: they can cause this exact error, prevent verification and introduce an obvious security risk. Use an authorised, unmodified Steam installation instead.
Should I reinstall FSX: Steam Edition?
Reinstall FSX only after the restart, privilege, account and file-verification checks have failed. Reinstalling over a folder that still contains third-party DLLs may preserve the problem.
- Back up custom content. Save manually installed aircraft, scenery and deliberate file edits, but do not carry old executables or Steam API DLLs into the clean installation.
- Uninstall FSX through Steam. Once removal finishes, rename any remaining FSX installation folder so Steam cannot reuse residual add-on files.
- Install into a valid Steam library. Let Steam complete the download and any prerequisite installation without manually moving the files.
- Launch the stock simulator once. Sign in online and start FSX from its Library entry before restoring any add-ons.
- Restore add-ons in small groups. If the error returns, the last launcher, DLL or executable modification added is the likely cause.
If a clean stock copy still reports that Steam must be running while other Steam games work normally, concentrate on FSX’s executable permissions and security-software history. If several games fail, repairing FSX again will not help; the Steam client, account session or connection needs attention.