Fix the FSX 24-bit color error by selecting 32-bit colour, removing compatibility flags, checking Remote Desktop and resetting display settings.
Microsoft Flight Simulator X (FSX) and FSX: Steam Edition display “Flight Simulator does not support 24-bit color” when Windows or FSX reports a 24-bit display mode rather than the 32-bit mode FSX expects. Select True Colour (32-bit), clear reduced-colour compatibility, avoid 24-bit remote sessions, then reset FSX's saved display mode if needed.
Why does FSX report 24-bit colour?
The warning means FSX is receiving an unsupported pixel-format report; it does not necessarily mean the monitor itself is limited to 24-bit colour. Remote sessions, old compatibility flags, a damaged FSX configuration or an unsuitable graphics driver can all cause the wrong value.
| When the error appears | Likely cause | Best first action |
|---|---|---|
| Only through Remote Desktop | The remote session is using 24-bit colour | Use a local session or select 32-bit colour in the remote client |
| After changing compatibility settings | Reduced-colour mode is enabled for fsx.exe | Remove the compatibility flag |
| After changing monitor or resolution | FSX has retained an invalid display mode | Reset its configuration file |
| Windows offers no 32-bit mode | Missing, generic or virtual display driver | Install the correct graphics driver |
How do I change FSX to 32-bit colour?
Work through these fixes in order, testing FSX after each one.
- Launch from the local Windows desktop. If you are using Remote Desktop, disconnect and sign in directly at the computer. Alternatively, open the remote client's display settings and select its highest-quality 32-bit colour option. A host policy may still limit remote sessions, in which case local access is the reliable test.
- Remove reduced-colour compatibility. Find the actual
fsx.exe, right-click it and open Properties, then Compatibility. Clear Reduced colour mode. Check Change settings for all users as well, because a second compatibility flag can be stored there. Do not enable Windows 95 or Windows 98 compatibility merely to address this error. - Select a 32-bit Windows display mode. In Windows 10 or 11, open Settings, System, Display, then Advanced display. Open the display adapter properties and choose List All Modes. Select the monitor's native resolution, a supported refresh rate and True Color (32 bit). Restart Windows after changing the mode.
- Reset FSX's saved display configuration. Close the simulator and open
%APPDATA%\Microsoft\FSX\. A Steam Edition installation alongside boxed FSX may instead use%APPDATA%\Microsoft\FSX-SE\. Back up and rename the activefsx*.cfgfile, then start FSX so it creates a clean one. If preserving manual tweaks matters, inspect the file for aMode=entry ending inx24and change only that final value tox32.
Renaming the configuration file does not uninstall aircraft or scenery, but it resets FSX preferences and manual configuration edits. Once the simulator opens, use our safe windowed and full-screen switching steps before experimenting with other resolutions.
What if Windows does not offer a 32-bit mode?
A missing 32-bit option usually indicates a graphics-driver or virtual-display problem rather than a damaged FSX installation. Check Device Manager for a generic display adapter, install the correct supported driver for the computer or graphics card, and reboot.
Temporarily disconnect USB display adapters, virtual monitors and capture or remote-display software. Test with one physical monitor connected directly to the primary graphics adapter. Our broader Windows 10 and 11 FSX troubleshooting checks cover driver, DirectX and compatibility problems that may remain after the colour mode is corrected.
Does an 8-bit display readout mean Windows is in reduced colour?
No. Windows may report 8-bit because that means eight bits per red, green and blue channel; it is not the old 8-bit, 256-colour desktop mode. Do not try to find a 32-bits-per-channel setting. What matters to FSX is that Windows presents the desktop mode as 32 bits per pixel.
What if FSX stops showing the warning but still will not start?
That means the colour-depth check has been fixed and a separate startup fault remains. If FSX reaches the splash screen and then closes, follow our graphics-layer and add-on crash checks rather than continuing to change colour settings.