Skip to content
FS2004 (FS9) 8 min read 289 views

Why won't FS2004 start on Windows 11 or Windows 10?

Ian Stephens
In short

Fix FS2004 on Windows 11 or Windows 10: SafeDisc, black screens, FS9.cfg, ntdll.dll errors, permissions and add-ons.

FS2004 (Microsoft Flight Simulator 2004: A Century of Flight, or FS9) can run on Windows 10 and Windows 11. The original CD release often will not start because modern Windows cannot use its SafeDisc disc-check driver. If a splash screen appears, suspect configuration, permissions, graphics or an add-on instead.

Can Microsoft Flight Simulator 2004 run on Windows 11 or Windows 10?

Yes, the FS2004 simulator itself can run on modern 64-bit Windows, but its original disc authentication and some period add-ons cannot.

FS2004 is also known as FS9 and is sometimes called MSFS 2004. It is the 2003 release titled Microsoft Flight Simulator 2004: A Century of Flight, not FSX or the newer Microsoft Flight Simulator releases.

A successful installation does not prove that the CD edition can start. Setup may copy every file correctly, only for the Disc 4 authentication check to fail when fs9.exe is launched.

Match the FS2004 symptom before trying a fix

The last visible stage tells you which part of FS2004 is failing.

What happensLikely causeFirst action
Nothing happens and no splash screen appearsSafeDisc authentication, security quarantine or damaged core filesCheck the CD edition and Windows Security
Disc 4 is repeatedly requested or rejectedUnsupported SafeDisc authentication or unreadable mediaEstablish whether the licensed edition has a supported launcher
The splash screen appears and disappearsDamaged FS9.cfg, startup module, scenery entry or modified fileReset the configuration and reverse recent changes
A black screen remains while fs9.exe is runningFull-screen initialisation, old display settings or an overlayReset FS9.cfg and test windowed mode
FS2004 stops while building sceneryMissing scenery folder, unavailable drive or damaged scenery entryUndo the latest scenery change
The menus open, but loading a flight crashesSaved flight, aircraft, panel, gauge, weather or local sceneryLoad a default aircraft at a stock airport

Why does nothing happen when FS2004 is launched?

If the original CD edition produces no FS2004 splash screen, SafeDisc is the leading suspect on Windows 10 and Windows 11.

The disc release relies on the old secdrv.sys SafeDisc driver. Modern Windows does not provide a supported way for FS2004 to use that driver. A different optical drive, repeated reinstalls and the FS9.1 update do not replace the missing Windows component.

Do not download a loose copy of secdrv.sys, disable Windows security globally or install an unknown replacement fs9.exe. These are common malware routes. Use only a publisher-authorised executable or distribution lawfully supplied for your licensed copy; otherwise, the original discs require a compatible period Windows installation, preferably kept offline.

A damaged Disc 4 can still be responsible on an older compatible computer. On Windows 10 or Windows 11, however, replacing the disc or drive will not cure the underlying SafeDisc incompatibility.

Will Windows XP compatibility mode make the original CDs work?

No, Windows XP compatibility mode cannot restore SafeDisc support because it is not an XP emulator and does not supply the missing kernel driver.

A licensed Windows XP virtual machine is a different approach, but 3D acceleration, joystick access and optical-disc pass-through depend on the virtualisation software. A suitable period computer is generally more predictable for the original CDs and should be isolated from the internet.

How do I fix FS2004 not opening after SafeDisc is ruled out?

The most reliable method is to test the launch path in order, making one change at a time.

  1. Identify exactly where FS9 stops.

    Open Task Manager, select the Details view and launch FS2004. If fs9.exe never appears, check the shortcut and installation. If it appears briefly but closes before the splash screen, investigate authentication, quarantine and core files. If the splash screen appears, continue with the configuration and add-on checks.

  2. Check Windows Security Protection History.

    Look for an entry involving fs9.exe or a third-party DLL. Restore a file only when it came from a known, legitimate package and its integrity is not in doubt. Do not create a blanket exclusion for the whole simulator merely to run an unverified executable.

  3. Use a writable installation folder.

    FS2004 and many old add-on installers expect to write inside the simulator directory. Installation under Program Files or Program Files (x86) can produce permission failures or split files between the real folder and Windows VirtualStore.

    For a clean installation, a simple location such as C:\FS2004 avoids much of that trouble. Do not drag an existing installation there because registry entries and add-ons may retain the previous path. Our clean FS2004 installation procedure for Windows 11 covers the installation folder, Disc 4, FS9.1 and the first test flight.

  4. Apply FS9.1 before adding modifications.

    Update a clean installation, start it and test a default flight before installing aircraft, scenery, gauges or modules. If the updater rejects unexpected files, restore the original files rather than forcing it over a modified executable. FS9.1 improves the simulator but does not remove SafeDisc authentication.

  5. Rebuild FS9.cfg.

    Press Windows+R, enter %APPDATA%\Microsoft\FS9, and rename FS9.cfg to FS9.cfg.old. FS2004 should create a fresh file on its next successful start.

    This resets graphics settings and control assignments, so keep the old file until the simulator is stable. If the folder or file does not exist, FS9 may never have reached configuration creation. If no replacement appears after launching, the failure is occurring earlier or Windows is denying access to the user profile.

  6. Remove only identifiable third-party add-ons.

    Start with the most recently installed module, scenery area, aircraft or gauge. A DLL in Modules can close FS9 during the splash screen, while an aircraft panel or gauge often fails when the saved flight is loaded.

    Move known third-party files to a temporary folder and retest; do not empty default folders or delete DLLs at random. For an installation with many mixed add-ons, use our startup-crash isolation sequence for modules, gauges, flights and scenery.

  7. Test compatibility settings separately.

    Begin with all compatibility options cleared. Next, test Windows XP Service Pack 3 compatibility mode by itself, followed by one test using Run this program as administrator. If administrator mode alone works, a writable installation folder is safer than permanently running FS2004 with elevated rights.

    A mistake we see constantly is enabling every compatibility option at once. That hides which setting helped and can introduce display or permission problems of its own.

  8. Inspect the Windows application error.

    Open Event Viewer, go to Windows Logs and then Application, and find the error recorded at the launch time. Record the faulting module before changing anything else. A named third-party DLL is useful evidence; a Windows DLL alone is usually not the root cause.

What if resetting FS9.cfg does not work?

If a fresh configuration changes nothing, the fault lies earlier in authentication or later in an add-on, saved flight, scenery entry or Windows profile.

  • No splash screen: stop repeating the configuration reset and return to the SafeDisc, security and core-file checks.
  • Splash screen still disappears: reverse the most recent module or scenery change, then test with all identifiable third-party startup modules removed.
  • Menus open: load a default Cessna at a stock airport with simple weather rather than the previous saved flight.
  • FS2004 starts in a new local Windows account: the original profile contains a configuration, permission or redirected-folder problem.
  • The error names PANEL.DLL: suspect the aircraft loaded by the default flight, its panel configuration or an associated gauge. Follow our targeted PANEL.DLL checks for aircraft and gauges.
  • The failure began after FS2004 had worked normally: reverse the latest add-on, graphics driver, Windows setting or configuration change before considering a complete reinstall.

How do I fix an FS2004 black screen?

A black screen with fs9.exe still running is usually a display or full-screen initialisation problem rather than SafeDisc.

  1. Rename FS9.cfg. This removes an unsupported resolution, stale graphics-device entry or troublesome full-screen setting.
  2. Press Alt+Enter. If FS2004 is responsive, this switches between full-screen and windowed operation.
  3. Test Disable fullscreen optimisations. Enable this option by itself in the compatibility properties for fs9.exe.
  4. Disable overlays temporarily. Recording, monitoring and graphics overlays can interfere with old full-screen applications.
  5. Confirm that the process is still alive. If fs9.exe has closed, treat the incident as a startup crash rather than a display fault.

Persistent cases are covered in our focused FS2004 black-screen and full-screen troubleshooting.

What does an ntdll.dll error mean in FS2004?

An ntdll.dll entry identifies the Windows library in which the crash surfaced, but it rarely identifies the component that caused it.

Corrupt add-on code, a bad gauge, damaged configuration data or another module can pass invalid data into Windows and leave ntdll.dll recorded as the faulting module. Do not download a replacement copy of that file.

Start by resetting FS9.cfg, reversing recent add-ons and testing a new Windows profile. If Event Viewer names a third-party DLL elsewhere in the event, investigate that component first. Windows system repair is justified only when other unrelated applications also report system-DLL faults.

When should I reinstall FS2004?

Reinstall FS2004 only when core files have been overwritten, the FS9.1 updater no longer recognises the installation, or third-party files cannot be separated reliably from the defaults.

Reinstallation cannot fix unsupported SafeDisc authentication, so settle that issue first. Back up personal flights and original add-on packages, uninstall FS2004, and rename any simulator directory left behind. Install into a writable folder, apply FS9.1 and verify a default flight before restoring add-ons in small groups.

Do not copy the entire old FS2004 directory back over the clean installation. That restores the same damaged modules, configuration conflicts and scenery files the reinstall was meant to remove.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members