Fix FS2004 not detecting your graphics card by resetting FS9.cfg, choosing the correct GPU, checking Direct3D drivers and removing overrides.
FS2004 usually fails to identify a graphics card because FS9.cfg contains a stale display profile, Windows has assigned fs9.exe to the wrong GPU, or the proper graphics driver is missing. Reset FS9.cfg, force the high-performance GPU, verify Direct3D in DxDiag, then remove compatibility or wrapper overrides.
Why does FS2004 show the wrong graphics card?
FS2004 stores device-specific display settings, so a hardware or driver change can leave it using an obsolete adapter profile. The simulator does not require a card-specific database entry, but it does rely on Windows and Direct3D presenting a working display device.
| Symptom | Likely cause | First action |
|---|---|---|
| The previous card is still listed | Cached FS9.cfg display profile | Rebuild FS9.cfg |
| Only Intel or AMD integrated graphics appears | Hybrid-graphics laptop or incorrect Windows GPU assignment | Assign fs9.exe to the high-performance GPU |
| Microsoft Basic Display Adapter appears | The proper graphics driver is missing | Install the supported driver for the card |
| Only basic resolutions or software rendering are available | Driver, Remote Desktop, virtual-machine or compatibility override | Test locally and check Direct3D in DxDiag |
How do I make FS2004 detect the correct GPU?
The reliable fix is to verify the Windows driver, assign the actual FS2004 executable to the desired GPU, and force the simulator to build a fresh display profile. Work through these steps in order rather than reinstalling FS2004 immediately.
- Check the graphics driver. Open Device Manager and confirm that the card is shown by its proper name rather than as Microsoft Basic Display Adapter. Run
dxdiagfrom the Windows Run box and check the Display tabs for the expected device, driver and working Direct3D acceleration. If Windows cannot see the card correctly, FS2004 cannot see it either. - Find the fs9.exe you actually launch. Multiple FS2004 installations are common, and Windows graphics preferences may point to the wrong copy. Check the target of your shortcut or open its file location before adding the executable to Windows Graphics settings.
- Assign the high-performance GPU. In Windows Settings, open the per-application Graphics options, add
fs9.exeas a desktop application and select the high-performance device. Menu wording varies between Windows releases. Restart FS2004 after changing the preference; on a desktop PC, also make sure the monitor is connected to the dedicated card rather than the motherboard video output. - Rebuild FS9.cfg. Close FS2004, enter
%APPDATA%\Microsoft\FS9in the Run box, and renameFS9.CFGtoFS9.CFG.bak. Launch the simulator so it creates a clean file and enumerates the available display devices again. This resets many personal settings but does not remove installed aircraft or scenery; our notes on backing up and rebuilding FS9.cfg safely cover the file in more detail. - Remove conflicting overrides. Open the Compatibility tab for
fs9.exeand clear old Windows compatibility modes, reduced-colour mode and forced 640 × 480 operation. Running as administrator does not select a graphics card. If an add-on deliberately placed a Direct3D wrapper such asd3d9.dllbesidefs9.exe, move that local add-on file out temporarily; never remove the Windows system copy. - Test the hardware display settings. Start FS2004, open Settings, then Display and the Hardware tab. Select an available resolution and test in windowed mode before restoring anti-aliasing, filtering or other demanding options.
What if the dedicated card still does not appear?
A missing card name does not always mean the dedicated GPU is unused, especially on laptops with hybrid graphics. The internal display may remain attached to the integrated adapter while the dedicated GPU performs the rendering, so FS2004 can report the integrated device even after Windows has enabled GPU offloading.
- Check actual GPU activity: add the GPU engine column in Windows Task Manager and watch
fs9.exewhile flying. If it is using the dedicated GPU engine, the adapter label inside this older simulator can be ignored. - Avoid remote sessions: Remote Desktop and some virtual machines expose a virtual or software display adapter. Test FS2004 from a local Windows session; a virtual machine also needs working 3D acceleration.
- Confirm the new configuration was created: if
FS9.CFGwas not regenerated, check that you used the same Windows account that runs FS2004 and that the FS9 configuration folder is writable. - Do not download loose DLL files: if DxDiag reports a DirectX problem or FS2004 names a missing component, repair the official legacy DirectX components instead of placing an unverified DLL beside the simulator.
If FS2004 detects the adapter in windowed mode but produces a black screen or loses the display only when switching modes, use our specific fixes for FS2004 full-screen failures. Broader crashes, overlays and driver overrides are covered in our modern-Windows troubleshooting checks for FS2004.
How do I know FS2004 is using hardware acceleration?
FS2004 is using a hardware device when its Hardware display options and normal resolutions are available, Direct3D is working in DxDiag, and Windows shows fs9.exe on a GPU engine. A low GPU percentage alone is not evidence of a fault: FS2004 is an old, heavily CPU-limited simulator and may leave much of a modern graphics card idle.
Once detection is stable, reapply options gradually rather than copying an old FS9.cfg back over the new one. Our recommended FS2004 display settings for image quality and frame rate explain which hardware options are useful and which can cause unnecessary trouble.