Install the FSX SDK on Windows 10 or 11 in the right order, then fix missing tools, SimConnect errors, permissions and version mismatches.
To install the Microsoft Flight Simulator X (FSX) SDK on Windows 10 or 11, match it to the exact simulator edition and update level. Boxed Deluxe/Gold needs the base SDK and updates in order; FSX: Steam Edition supplies SDK content in its game folder. Most failures are version mismatches, permissions, x86 prerequisites or dll.xml configuration.
Which FSX SDK version do I need?
The SDK must match the installed FSX edition and service-pack level. FSX and its SDK are 32-bit applications, even on 64-bit Windows 10 or 11.
| FSX edition | Correct SDK source and order |
|---|---|
| Boxed Standard | The Standard media does not include the SDK. The original SDK was supplied with Deluxe and Gold editions. |
| Boxed Deluxe without Acceleration | Install the base SDK from the SDK folder on Deluxe Disc 1. After FSX SP1, install SDK SP1A; after FSX SP2, install the matching SDK SP2 package. |
| Gold or Deluxe with Acceleration | Install the Deluxe base SDK, bring it to SDK SP1A, install Acceleration, then run the SDK installer from the Acceleration media. Do not put the standalone SDK SP2 update over the Acceleration SDK. |
| FSX: Steam Edition | Use the SDK content under [FSX installation folder]\SDK. Do not apply boxed FSX, SP1A, SP2 or Acceleration SDK installers to Steam Edition. |
A mistake we see regularly is combining a boxed SDK update with FSX: Steam Edition because both products are called FSX. Their installation paths, registry entries and build levels differ, so a setup programme may fail to detect the simulator or install tools that cannot load.
How do I install the boxed FSX SDK?
- Identify the simulator build. Establish whether this is Standard, Deluxe, Gold, SP2 or Acceleration before running an SDK installer. If boxed and Steam editions coexist, record the installation path of the copy for which you are developing.
- Run FSX once. Complete boxed activation if required, load a flight, close FSX and let it create its configuration and registry data.
- Install the base SDK. Open the SDK folder on Deluxe Disc 1 and run its setup programme as administrator. Keep the default SDK destination unless a specific development workflow requires another location.
- Apply updates in sequence. Update the simulator and SDK as paired stages. Our explanation of the correct FSX SP1 installation order and edition restrictions covers the simulator side of this process. An SDK update cannot replace the base SDK.
- Install the final matching SDK. Use SDK SP2 for boxed FSX SP2, or the SDK on the Acceleration media for an Acceleration/Gold installation.
- Create a separate project folder. Store source XML, models, textures and compiler output somewhere writable, such as a folder under Documents. Do not build projects inside
Program Filesor overwrite SDK samples.
Run the legacy installer as administrator, but do not automatically force FSX and every SDK utility into Windows XP compatibility mode. Compatibility settings can create a second set of permission and path problems. If setup reports Error 1607 or cannot initialise InstallShield, use our steps for repairing the legacy installer and its permissions before changing SDK versions.
How do I install the FSX: Steam Edition SDK?
FSX: Steam Edition places its SDK content beneath the main FSX installation folder rather than following the boxed SDK update chain. Open FSX's installed files through Steam and look for SDK; if that folder is absent or incomplete, verify the installed game files through Steam.
Many SDK components are documentation, samples or command-line utilities rather than a single application with a launcher. Do not assume installation failed merely because there is no “FSX SDK” desktop shortcut. Boxed SDK update packages should not be used to fill perceived gaps in the Steam SDK.
How can I check that the FSX SDK works?
A working SDK should provide documentation, compiler files and the expected development subfolders. Check it in stages rather than using an add-on as the first test.
- Open the local SDK documentation and confirm that its pages display.
- Locate
BglComp.exebeneath the Environment Kit's BGL Compiler SDK folder. - Run a compiler from Command Prompt or a batch file using a valid sample project.
- Confirm that the compiler can write its output to your separate project folder.
BglComp.exe and similar utilities may flash briefly and disappear when double-clicked. That is normal for a command-line tool, not evidence of a crash. Run it from an open Command Prompt to see usage information and error messages.
Why is the FSX SDK not installing or compiling?
| Symptom | Likely cause and fix |
|---|---|
| Setup says FSX or the original SDK is missing | The wrong edition is registered, the base SDK was skipped, or boxed and Steam installations are mixed. Launch the intended FSX copy once, then reinstall the correct base SDK before its updates. |
| SDK SP1A or SP2 refuses to install | The preceding SDK level is absent. Follow the complete base, SP1A and final SDK sequence rather than installing only the newest package. |
| Compiler opens and immediately closes | It is probably a command-line utility. Start it from Command Prompt or a batch file and read the reported arguments or source-file errors. |
| Access denied or no output file appears | The project is under a protected folder, or its output path is invalid. Move the project to a writable user folder and quote paths containing spaces. |
| Help pages are blank | Copy the help file to a local folder and use its Windows file properties to unblock it if that option appears. Windows may restrict compiled help opened from downloaded or network locations. |
| “Side-by-side configuration is incorrect” appears | A required x86 runtime or legacy SimConnect assembly is damaged or absent. Follow the checks for repairing FSX side-by-side dependencies; installing a 64-bit runtime alone does not satisfy a 32-bit SDK tool. |
Why is the SDK Tools menu missing in FSX?
The SDK being present does not automatically guarantee that its in-simulator modules are loaded. Object Placement, Traffic Toolbox and similar tools depend on valid module entries in the active dll.xml.
- Find the active configuration folder. Boxed FSX normally uses
%APPDATA%\Microsoft\FSX. Steam Edition may use either that folder or%APPDATA%\Microsoft\FSX-SE, particularly when boxed FSX is also installed. - Back up
dll.xml. Open it in a plain-text editor and confirm that it remains well-formed XML with a single document root. - Check each module entry. Its path must point to the actual DLL in the matching SDK folder. Ensure the module is not marked disabled and that an old boxed path has not survived a move to Steam Edition.
- Start FSX and accept the trust prompt. Load a flight before checking for the Tools menu. If FSX crashes, disable the new module entry and verify its path and SDK version before trying again.
Do not copy SDK tool DLLs randomly into the FSX root directory. Correcting the module path is safer and makes it clear which SDK installation FSX is loading.
Does installing the SDK fix SimConnect add-ons?
No. The SDK contains development files, but an add-on that cannot connect usually needs the correct SimConnect runtime rather than the whole SDK. Different FSX-era SimConnect assemblies can coexist side by side, and replacing one with another is not the right repair.
Steam Edition keeps legacy SimConnect redistributable installers beneath its SDK tree. Install the version required by the add-on and check paths, process permissions and architecture using our FSX SimConnect installation and connection checks. Avoid downloading a loose SimConnect.dll and placing it in the FSX folder.
How do I recover from mixed or damaged SDK versions?
Remove only the mismatched SDK components first; reinstalling the entire simulator is rarely necessary. Back up projects and dll.xml, uninstall SDK updates in reverse order where possible, reinstall the base SDK, and then apply only the updates appropriate to that FSX edition.
For Steam Edition, remove boxed SDK references from development scripts and module configuration, verify the Steam files, and retest one tool at a time. This separates an SDK installation fault from a broken project, invalid XML source or third-party add-on problem.