How do I fix the FSX 'out of date license' error on Windows 11?

To fix the FSX “out of date license” error on Windows 11, correct the PC’s date and time, remove compatibility mode, then identify your edition. Run boxed Microsoft Flight Simulator X once as administrator and activate it; launch FSX: Steam Edition through Steam and verify its files instead.

Is the error from boxed FSX or FSX: Steam Edition?

The correct repair depends on the edition because boxed FSX and FSX: Steam Edition use different licensing systems. Both run an executable named fsx.exe, so an old shortcut can easily open the wrong copy.

The boxed error may say that the software licensing system has reported the “license is out of date”, sometimes with a hexadecimal error code. Record the full wording and code before changing anything.

FSX: Steam Edition should not request a retail disc key. A boxed activation dialogue inside the Steam installation usually means an obsolete shortcut is opening boxed FSX, or boxed executables and DLLs have been copied into the Steam folder.

What should I try first on Windows 11 or Windows 10?

Correct the clock and remove inherited compatibility settings before repairing or reinstalling FSX.

1. Synchronise the Windows clock. Open the Date and time settings, select the correct time zone, enable automatic time where appropriate and synchronise it. Restart Windows afterwards. If FSX was installed while the clock was significantly wrong, a repair may still be required after correcting it.
2. Turn off compatibility mode. Check the properties of both the shortcut and the actual fsx.exe. On the Compatibility tab, clear “Run this program in compatibility mode for” and inspect the settings applied for all users as well. Old Windows XP, Vista or Windows 7 compatibility flags are a common cause of inconsistent legacy licence checks.
3. Use the correct launcher. Start Steam Edition from the Steam library during diagnosis. For boxed FSX, open fsx.exe from its real installation directory rather than trusting an old desktop or taskbar shortcut.
4. Use administrator rights carefully. Run boxed FSX once as administrator after installation or repair so that first-run data can be written. Do not permanently elevate only the Steam Edition executable while Steam remains at normal privilege; the Steam client and simulator should normally run at the same level.
5. Check Windows Security. Review Protection history for blocked FSX or Steam activity. If Controlled folder access has blocked the legitimate installed executable, allow that executable rather than disabling protection indefinitely.
6. Test an unmodified flight. Restart FSX and load a default aircraft at a default airport. Do not restore add-ons until the licence warning has disappeared and the base simulator starts reliably.

How do I repair the boxed FSX licence?

For boxed FSX, repair the original installation first and use a clean reinstall only when the base files or activation components remain damaged.

1. Back up personal content. Save third-party aircraft, scenery, flight plans and other material you need. Do not plan to restore the old fsx.exe, core DLLs, activation files or complete installation directory.
2. Run the original setup repair. Use the media that matches the installed edition and run its setup with administrator rights. Test the simulator before reinstalling service packs or Acceleration.
3. Remove expansions before a clean reinstall. If repair fails, uninstall Acceleration first when present, then uninstall the base simulator and restart Windows. Rename any remaining FSX installation folder so leftover add-on modules cannot contaminate the new copy.
4. Install the base simulator. If choosing a custom location, a simple folder such as C:\Games\FSX can avoid some permissions complications associated with protected Program Files directories. Do not create an installation by copying an FSX folder from another PC.
5. Launch and activate before updating. Run the untouched base FSX once as administrator, follow the activation choices presented by the legitimate installer and confirm that a default flight loads.
6. Apply the correct update path. For Standard or Deluxe without Acceleration, install Service Pack 1 and then Service Pack 2. For Gold Edition or another installation using Acceleration, install the base simulator and then Acceleration; do not install standalone Service Pack 2 over Acceleration.
7. Restore add-ons gradually. Add aircraft, scenery and modules in small groups, testing after each group. This prevents an obsolete replacement DLL or module from disguising the repaired licence state.

Gold and Acceleration packages can supply a different key from the base simulator. Entering an Acceleration key into the base FSX prompt, or trying a boxed key in Steam Edition, will not work. If the message specifically rejects a key rather than saying the licence is out of date, use our guide to distinguishing a wrong or mismatched product key from a damaged licence state.

If installing or activating Acceleration produces error 1-80004005, treat that as a separate, code-specific fault and follow our safe repair sequence for the Acceleration activation error. Do not apply storage-filter registry edits merely because another licence message looks similar.

Why does FSX: Steam Edition show a licence error?

A Steam Edition licence warning usually indicates the wrong executable, damaged core files, mismatched privilege levels or a mixed boxed-and-Steam installation.

1. Sign in to the owning Steam account. Allow Steam to connect for entitlement verification and start FSX from its library entry.
2. Match privilege levels. Close FSX and Steam, remove permanent administrator settings from fsx.exe, then restart Steam normally. If an elevated test is necessary, close both programs and run the Steam client as administrator so it launches FSX at the same level.
3. Verify the installed files. Run Steam’s file-integrity verification for FSX. Back up intentionally modified default files first because verification may replace them.
4. Remove obsolete shortcuts. If FSX works from the Steam library, delete shortcuts that point directly to another installation and create a fresh shortcut.
5. Separate boxed and Steam files. The two editions may be installed on one PC, but they must not share an installation directory. Never copy a boxed fsx.exe or boxed core DLLs into the Steam Edition folder.
6. Clean the installation directory if necessary. After uninstalling through Steam, inspect the former FSX directory and move remaining third-party files elsewhere before reinstalling. Add-on files can survive a normal uninstall and recreate the fault.

If Steam reports an initialisation failure rather than the boxed “out of date license” wording, follow our Steam Edition startup and file-verification checks.

Can a Windows update, drive clone or PC move trigger the error?

Yes, but a Windows update does not normally make a valid product key invalid. It can expose old compatibility flags, alter permissions or cause security software to block a legacy component.

If the warning appeared immediately after an operating-system update, work through our post-update FSX diagnostic sequence before rebuilding the simulator.

A cloned drive, restored system image or copied FSX folder is different. Boxed FSX depends on registry entries and machine-level licence data as well as the visible simulator files. Install it from the original media on the destination PC, establish a working base installation and restore only user content. Steam Edition should be installed and validated through Steam on that PC.

Does the same fix work on Windows 10?

Yes. The edition check, clock correction, compatibility-mode removal and boxed-versus-Steam repair sequence are the same on Windows 10. The appearance of Windows settings may differ, but Steam Edition still uses Steam entitlement and boxed FSX still uses its original activation system.

What if the out-of-date licence error remains?

A warning that survives on an untouched base installation must be diagnosed from the exact edition, message and error code rather than treated with a generic licence reset.

• Boxed FSX: confirm that the media and key belong to the same base edition, and that an Acceleration key has not been confused with the FSX key. Use only the activation options presented by the legitimate installer.
• FSX: Steam Edition: confirm ownership in the signed-in account, verify the files and ensure that no boxed executable remains in the Steam directory. Testing from a new Windows administrator account can reveal damaged per-user permissions.
• Either edition: do not restore backed-up executables, core DLLs, complete registry branches or activation folders. Doing so commonly restores the original fault as well.

A mistake we see repeatedly is applying an old registry or licence-reset procedure intended for one numeric error code to every FSX activation warning. Some of those changes affect storage-filter settings and can interfere with Windows or disk software. Preserve the exact error code and use a code-specific repair instead of an unofficial activation bypass.