Install FSX Deluxe from DVD on Linux Mint with Bottles, with disc-swapping steps, Wine settings, update order and fixes for common errors.
Install the boxed FSX Deluxe DVDs inside one Bottles Gaming bottle: run Disc 1’s setup program through that bottle, map the mounted DVD to a stable Wine drive letter, and swap to Disc 2 when prompted. Launch FSX once before updates, and expect possible DVD-access, graphics and activation problems under Wine.
These instructions are for the boxed Microsoft Flight Simulator X Deluxe edition, not FSX: Steam Edition. FSX was never supported on Linux, so Bottles can make it work through Wine but cannot guarantee compatibility with the installer, activation system or every add-on.
What Bottles settings should I use for FSX Deluxe?
Use a fresh Gaming bottle and keep FSX, its service packs and all later add-on installers inside that same bottle. Installing an update in a different bottle gives it a separate Windows registry and virtual drive, so it will not find FSX.
Leave the bottle architecture at the default offered by your Bottles runner. FSX is a 32-bit application, which means a 64-bit Linux Mint installation still needs working 32-bit Wine and graphics libraries. Never start Bottles or the FSX installer with sudo; that creates root-owned files and causes permission failures later.
Start with the Gaming bottle’s normal DXVK configuration if the graphics driver supports Vulkan. If FSX later opens to a black window or DXVK will not initialise, test WineD3D instead. Change one graphics option at a time and leave FSX’s Preview DirectX 10 setting disabled while establishing a working installation.
How do I install the two FSX Deluxe DVDs?
Keep the installer running in one bottle and make both discs appear under the same Wine drive letter.
- Create the bottle. Add a new Gaming bottle for FSX Deluxe, allow Bottles to finish installing its runner and then open that bottle.
- Mount Disc 1 in Linux Mint. Confirm that its files are visible in the file manager before opening the installer. A physical disc is commonly mounted below
/media/<user>/. If Bottles was installed as a Flatpak and cannot see that directory, grant it read access through the Flatpak permissions or copy the source to a user-accessible folder. Our guidance on making the FSX DVDs accessible from a mounted or copied source also covers systems without a usable optical drive. - Assign a stable drive letter. Open the bottle’s Wine configuration tool, find the Drives tab and map a letter such as
D:to the mounted Disc 1 directory. This avoids the installer losing its source when Linux Mint gives Disc 2 a different mount path. - Run Disc 1 setup. Use Bottles’ Run Executable command and select the setup executable in the root of Disc 1. Accept the normal virtual
C:installation location and enter the genuine product key supplied with your edition. Do not direct FSX into a normal Linux system directory. - Present Disc 2 when requested. Leave the installer open, unmount or eject Disc 1 and mount Disc 2. If its Linux path changed, update the existing
D:mapping to point at Disc 2, then return to the installer and retry. Do not start a separate setup programme from Disc 2. - Complete and test the base simulator. Launch FSX from the bottle’s detected Programs list. If no shortcut appears, locate
fsx.exeunder the bottle’s virtual Program Files directory and add it manually. Let FSX create its user folders and configuration, start one simple free flight, close it normally and stop any remaining Wine processes before installing updates.
Do not merge files from Standard, Deluxe, Gold or another regional release to satisfy a disc prompt. The installer checks its expected media and mismatched sources commonly produce repeated prompts, CAB errors or an incomplete installation.
What if Bottles cannot see or swap the DVD?
Disc swapping normally fails because the Flatpak sandbox blocks the mount directory or Wine’s drive letter still points to Disc 1.
| Symptom | Likely cause and fix |
|---|---|
| DVD is absent from the file picker | Mount it in Linux Mint first, then grant Bottles read access to its mount directory or use a local copy made from your own disc. |
| Setup keeps requesting Disc 2 | Keep the installer open and remap the same Wine drive letter to Disc 2. Restarting setup from Disc 2 will not continue the original installation. |
| Error 1305 or a CAB file cannot be read | The source is unreadable, incomplete or losing access through the sandbox. Clean and recopy the disc rather than repeatedly retrying; use our checks for FSX DVD and CAB read failures to isolate the damaged file. |
| Error 1607 or 1628 | Stop all processes for the bottle, reopen it and run setup again from a clean source. For Error 1607 specifically, follow the relevant InstallShield runtime and permissions checks; avoid downloading loose installer DLLs. |
| Installer window is hidden or unresponsive | Check for a modal product-key or disc prompt behind the main window. A temporary Wine virtual desktop can also prevent old installer dialogues from opening off-screen. |
Which FSX updates should I install afterwards?
For standalone FSX Deluxe, install Service Pack 1 first and Service Pack 2 second, running both installers inside the existing FSX bottle. Test the simulator after each stage so that a failed update is easy to identify.
If the Deluxe DVDs came as part of FSX Gold with Acceleration, finish and launch the Deluxe base installation before adding the expansion. Acceleration supplies updated simulator components, so do not layer standalone service packs and Acceleration in an arbitrary order; follow the correct Deluxe and Acceleration installation sequence.
Can boxed FSX be activated through Bottles?
Activation is the least predictable part because the boxed edition uses Microsoft’s legacy licensing system. Enter a valid key and allow the first launch to complete, but be aware that an old activation component or unavailable activation route may fail even when the simulator itself runs under Wine.
Bottles cannot replace or bypass product activation. Once FSX is successfully installed and activated, preserve that bottle rather than repeatedly recreating it; the registry, licensing data, simulator files and configuration all live inside the Wine prefix.
Why does FSX install but fail to start?
A post-install launch failure is usually caused by missing 32-bit graphics support, the selected Direct3D backend or an add-on installed outside the FSX bottle. Confirm that unmodified FSX starts before adding aircraft, scenery or utilities.
- If DXVK reports missing Vulkan support, install the appropriate 32-bit graphics components for the active Linux Mint driver or switch the bottle to WineD3D.
- If a log identifies a missing DirectX 9 helper DLL, add the corresponding dependency through Bottles rather than downloading an individual DLL from an unknown source.
- Keep Preview DirectX 10 disabled until the DirectX 9 installation works reliably.
- Run legacy add-on installers through the same bottle so they can read FSX’s registry entries. Manual add-ons must go into the FSX folders inside the bottle’s virtual
C:drive. - Expect add-ons that rely on obsolete copy-protection drivers, low-level Windows services or proprietary launchers to remain incompatible with Wine even when the base simulator works.