Fix the FSX: Steam Edition “Steam must be running” error by checking launch method, stuck processes, permissions, game files and licence validation.
FSX: Steam Edition shows “Steam must be running” when fsx.exe cannot initialise the Steam client or validate the game licence. The usual causes are a stale Steam process, launching the wrong executable, mismatched administrator privileges, blocked Steam API files, or using an account that is not authorised for the game.
How do I fix the FSX Steam must be running error?
The fastest reliable fix is to relaunch FSX through Steam, clear stuck processes, match the programs’ permissions and then verify the installation. We recommend testing FSX after each step so you know which change solved it.
- Launch FSX from the Steam Library. Sign into the account that owns or has access to FSX: Steam Edition, put Steam online temporarily and select Play from the game’s Library entry. If this works, remove the old Windows shortcut and create a fresh one through Steam.
- Exit Steam completely. Close FSX, use the Steam menu’s Exit command and wait for its processes to close. If Task Manager still shows FSX or Steam running, end the stuck process or restart Windows. Our steps for clearing stale FSX and Steam processes cover this situation in more detail.
- Match the administrator settings. Check the Compatibility properties of the Steam and FSX shortcuts. Normally, both should run without forced compatibility mode or Run this program as administrator. If an old add-on genuinely requires elevation, Steam and FSX must be started at the same privilege level for the test.
- Verify the FSX files. Open the game’s Properties in Steam and select Verify integrity of game files under the installed-files or local-files section. This restores missing or altered Steam API components. Verification can also replace deliberately modified default FSX files, so back up any such changes first.
- Check security-software history. Look for blocked FSX files or Steam API components such as
steam_api.dll. If a legitimate file from the Steam library was removed, permit that specific installation location and verify the game again. Do not disable protection globally or download a replacement DLL from an unrelated source. - Refresh Steam’s account validation. Sign out of Steam, restart the client and sign back into the authorised account while online. Offline Mode can work after a licence has been cached, but it is unsuitable for diagnosing this error. If Steam reports a separate entitlement message, follow our Steam licence and account-validation checks.
- Separate boxed and Steam installations. Boxed FSX and FSX: Steam Edition may coexist, but their core folders, executables and shortcuts must remain separate. Do not launch a copied
fsx.exe, merge the two installation directories or move a Steam library manually; use Steam’s storage tools instead.
What if Steam is already open?
A visible Steam window does not guarantee that FSX can reach a valid Steam API session. The pattern of the failure usually identifies the next step:
| What happens | Likely cause | First action |
|---|---|---|
| Steam’s Play button works, but an old shortcut fails | Wrong or outdated shortcut | Create a new shortcut through Steam |
| Play also produces the message | Stale session, permission mismatch or missing file | Restart Steam, match privileges and verify files |
| 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 then closes | A separate FSX or add-on startup fault | Use our FSX: Steam Edition startup-crash fixes |
Can I launch FSX directly from fsx.exe?
Use Steam’s Play button or a Steam-created shortcut rather than a copied shortcut to fsx.exe. Direct execution may work when the client session and installation are intact, but it is unreliable for troubleshooting and can target the wrong copy when boxed FSX is also installed.
External add-on launchers can also trigger the message if they start FSX before Steam or run with different administrator privileges. Open Steam first and keep the launcher, Steam and FSX at the same elevation level.
Should I reinstall FSX: Steam Edition?
Reinstall only after file verification and the Steam account checks fail. Steam’s uninstaller can leave third-party DLLs and add-on files behind, so reinstalling over the same residual folder may preserve the cause.
- Back up custom content, including manually installed aircraft, scenery and deliberate core-file edits.
- Uninstall FSX through Steam, then rename the remaining FSX installation folder rather than immediately deleting it.
- Install a clean copy into a valid Steam library and launch the stock simulator once before restoring add-ons.
- Restore add-ons gradually so an incompatible launcher or DLL can be identified if the error returns.
If a clean, stock installation still cannot communicate with Steam, the fault is more likely to involve Windows permissions, security software or the Steam client than FSX scenery or configuration. Continue with our broader Windows 10 and 11 FSX launch checks.