Download and install Orbiter Space Flight Simulator on Windows: get the right package, extract it correctly, configure video and fix launch errors.
Get the Windows Orbiter package from our Orbiter download page, extract the entire archive into its own writable folder, then run the launcher from that extracted folder. Do not run Orbiter inside the ZIP or place it inside Microsoft Flight Simulator; Orbiter is a standalone simulator and normally needs no conventional installation.
How to download and install Orbiter on Windows
- Download the complete package. Save the archive somewhere easy to find and let the download finish before opening it. Check the file information and system requirements shown on the download page.
- Scan the downloaded archive. Use your normal security software before extracting it. Do not disable antivirus protection merely because an executable is flagged; first confirm that the file came from the expected download page.
- Create a dedicated Orbiter folder. Suitable locations include
C:\Users\YourName\Games\OrbiterorD:\Games\Orbiter. AvoidProgram Files, cloud-synchronised folders and other protected locations because Orbiter and older add-ons may need to write configuration files inside the simulator folder. - Extract the whole archive. Use Windows' extraction command or your usual archive utility, selecting the folder created above. If archive handling is unfamiliar, follow our detailed ZIP extraction procedure.
- Check the extracted structure. The main Orbiter application should sit beside folders such as
Config,Meshes,Modules,ScenariosandTextures. A mistake we see constantly is extracting or copying only the executable, which leaves Orbiter unable to find its scenarios, meshes and textures. - Run the main launcher. Open
orbiter.exe, or the corresponding launcher identified by the package documentation. Configure the video options, select an included scenario and start the simulation.
An archive installation usually creates no Start menu entry. Once Orbiter works, you can create a Windows shortcut to its main launcher without moving the executable out of the Orbiter folder.
Where should Orbiter be installed?
Orbiter works best in a normal writable folder rather than a protected Windows application directory. Its portable folder structure also makes it easier to back up the clean installation or keep separate copies for different sets of add-ons.
Running the simulator permanently as an administrator is not a good substitute for choosing the right folder. It can hide permission problems and leave configuration files owned by a different account.
How do I configure Orbiter for the first launch?
Start with conservative video settings and one of the basic scenarios included in the package. Windowed mode at a resolution supported by your display is easier to troubleshoot than full-screen mode; increase the settings after confirming that the base simulator loads correctly.
If the folder contains both a regular launcher and an _ng launcher, use the regular one first. The _ng variant is intended for use with a separately configured graphics client and may not render a flight until that client is enabled.
Test Orbiter before adding vessels, textures or graphics modules. This separates a base-installation fault from an incompatible add-on.
Why won't Orbiter start after extraction?
Most Orbiter launch failures come from an incomplete extraction, a protected installation folder or a graphics configuration that the driver cannot open.
| Symptom | Likely cause | What to do |
|---|---|---|
| Missing mesh, texture or scenario errors | Only part of the archive was extracted, or the executable was moved | Delete the incomplete copy and extract the entire archive again while preserving its folders |
| Settings do not save | The Orbiter folder is read-only, protected or cloud-controlled | Move the complete folder to a writable local location |
| Black screen or immediate exit after launch | An unsuitable video mode or optional graphics client is active | Return to the supplied launcher, choose windowed mode and disable optional graphics modules while testing |
| Windows displays a protection warning | The executable has limited reputation or is unsigned | Verify the download source and scan the package before deciding whether to run it; do not bypass the warning blindly |
| A DLL or runtime error appears | A graphics or runtime component required by that Orbiter release is absent | Install only the component named in the included documentation from its official publisher; never download an individual DLL from an unknown source |
Older Orbiter releases use graphics technology that may behave differently across Windows versions and display drivers. Compatibility mode and administrator mode should be diagnostic measures, not the first fix; complete extraction, a writable folder and basic video settings solve more installation problems.
How are Orbiter add-ons installed afterwards?
Orbiter add-ons commonly contain folders that mirror the simulator's own directory structure. Extract an add-on to a temporary location first, inspect it, then merge those folders into the actual Orbiter root only when the add-on documentation says to do so.
Match every add-on to the Orbiter release it was designed for. Older vessels and graphics clients can overwrite shared files or depend on interfaces absent from another release, so keep a clean copy of the working base folder and install one add-on at a time.