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

FS2004 (Microsoft Flight Simulator 2004, also called FS9) can run on Windows 10 and Windows 11, but the original CD edition often will not start because modern Windows blocks its SafeDisc-era disc authentication. If the splash screen appears, suspect a damaged FS9.cfg, denied file writes or an incompatible add-on instead.

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

Yes, the FS2004 program itself can run on modern 64-bit Windows, but its original CD authentication and some old add-ons cannot. This distinction explains why one installation works while another apparently identical copy does nothing.

Windows compatibility mode may help with permissions, display initialisation and assumptions made by old installers. It cannot restore the obsolete SafeDisc driver required by an unmodified retail CD installation.

What does FS2004 do when you launch it?

The last thing visible before FS2004 stops is the most useful diagnostic clue.

Why does nothing happen at all? SafeDisc DRM on Windows 11 and 10

A pre-splash failure with the original FS2004 CDs is commonly the SafeDisc launch check rather than a graphics or configuration fault. Setup can copy every file successfully and still leave an installation that cannot authenticate Disc 4 on Windows 10 or Windows 11.

Descriptions such as 立ち上がらない (will not launch), 動かない (does not run) and まったく反応しない (nothing happens at all) need the same first distinction: did FS9 ever display its splash screen? If not, resetting graphics options and deleting add-ons are unlikely to address the cause.

SafeDisc depended on the old secdrv.sys kernel driver. Modern Windows does not provide a supported way for FS2004 to use that driver. The FS9.1 update improves the simulator but does not by itself remove the original disc check, and using a USB optical drive does not replace the missing Windows component.

Will a DRM reset repair SafeDisc?

No. A “DRM reset”, clearing an unrelated Windows DRM cache, reinstalling FS2004 or repeatedly inserting Disc 4 cannot make modern Windows support the blocked SafeDisc driver. Renaming FS9.cfg is a configuration reset, not a DRM reset.

Do not download an old secdrv.sys file, disable Windows security globally or use an unverified replacement fs9.exe. Those approaches introduce a serious security and malware risk. Use a publisher-authorised, lawfully supplied executable or distribution intended to work without the obsolete driver if your licensed package provides one; otherwise, the original disc release requires a compatible period Windows environment, preferably kept offline.

A dirty or damaged Disc 4 can still cause authentication failures on an older compatible PC. On Windows 11 or Windows 10, however, buying another optical drive will not solve the underlying SafeDisc incompatibility.

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

Work through the launch path in order, changing one thing at a time so that the result identifies the fault.

1. Classify the failure before editing files.

   Open Task Manager, launch FS2004 and watch for fs9.exe. If it never appears or disappears before the splash screen on a retail CD installation, investigate authentication, security quarantine or damaged core files. If the splash screen appears, continue with the configuration and add-on checks below.

2. Review 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 installation and its integrity is not in doubt. Do not create a blanket antivirus exclusion merely to make an unknown executable run.

3. Use a writable installation folder.

   FS2004 and many period add-ons expect to write inside the simulator directory. An installation under Program Files or Program Files (x86) can therefore encounter permission errors, redirected files and mismatched add-on paths.

   For a clean installation, a simple folder such as C:\FS2004 avoids many of these problems. Do not drag an existing installation to a new folder because registry data, scenery entries and add-on installers may retain the old location. Our step-by-step FS2004 installation sequence for modern Windows covers the folder choice, FS9.1 update and clean first-launch test.

4. Apply FS9.1 before installing add-ons.

   Update a clean, unmodified installation and then launch it before adding aircraft, scenery, gauges or modules. If the updater rejects unexpected files, restore the original program files rather than forcing the update over a modified executable. Remember that FS9.1 is a simulator update, not a SafeDisc cure.

5. Rebuild FS9.cfg.

   Press Windows+R, enter %APPDATA%\Microsoft\FS9, and rename FS9.cfg to FS9.cfg.old. At its next successful start, FS2004 should generate a fresh configuration with newly detected display settings.

   This resets graphics options and control assignments, so retain the old file until the simulator is stable. If no new FS9.cfg appears, FS9 is failing before configuration creation or cannot write to the user profile.

6. Remove only identifiable recent add-ons.

   A third-party DLL in the Modules folder can terminate FS9 during the splash screen. Aircraft panels and gauges tend to fail when a flight loads, while a bad scenery entry can stop database initialisation.

   Move the most recently installed third-party files to a temporary folder and retest. Do not empty default folders or delete DLLs at random. If the installation contains years of mixed files with no clean backup, reinstalling is safer than trying to guess which files belong to FS2004.

7. Test compatibility settings separately.

   Begin with all compatibility options cleared. If FS9 reaches the splash screen but still fails, test Windows XP Service Pack 3 compatibility mode, then test one launch as administrator separately. If administrator mode alone fixes the problem, installing in a writable folder is cleaner than permanently running the simulator with elevated rights.

   For a black screen, reset FS9.cfg, test Disable fullscreen optimisations and press Alt+Enter if FS9 remains active long enough to change to windowed mode. Our guide to choosing compatibility settings for older simulators explains which options can help and which cannot repair missing components.

Why does the FS2004 splash screen appear and disappear?

A disappearing splash screen means FS9 has passed the earliest launch stage but crashed while reading its configuration, startup modules or scenery data. Reset FS9.cfg first, then undo the latest module or scenery installation.

Windows Event Viewer can provide a useful lead. Open Windows Logs, select Application and inspect the error recorded at the launch time. A named third-party DLL points towards that add-on; ntdll.dll is a generic crash location and does not prove that Windows itself is damaged.

If FS9 stops while building its scenery database, check that every enabled add-on scenery folder still exists at its recorded location. External disks, network folders and renamed directories commonly leave scenery entries pointing to files that are no longer available. For faults that survive a clean configuration, follow our deeper startup-crash checks for modules, gauges, flights and scenery.

What else should I check before reinstalling?

A few targeted tests can separate a damaged simulator from a Windows-profile or add-on problem.

• Try a new local Windows user profile. If FS2004 starts there, the existing profile's configuration, permissions or redirected folders are the likely cause.
• Read any missing-DLL message exactly. Install the appropriate official Microsoft legacy DirectX or Visual C++ runtime only when the error or a trusted add-on specification identifies it. Never download a loose DLL from an archive.
• Check unavailable scenery paths. Reconnect the relevant drive or remove the broken scenery entry rather than repeatedly rebuilding the entire simulator.
• Return to a default flight. If the menus open, test a stock aircraft at a stock airport with no complex weather or third-party panel. Success there rules out a general launch failure.

When should I reinstall FS2004?

Reinstall only when core files have been overwritten, the FS9.1 updater cannot recognise the installation, or third-party files can no longer be separated reliably from the defaults. Reinstallation will not fix unsupported SafeDisc authentication, so settle that issue first.

Back up personal flights and original add-on packages, uninstall FS2004, and rename any simulator folder left behind. Install a clean copy outside protected Windows directories, update it, and verify a default flight before restoring anything. Add aircraft and scenery in small groups; copying the entire old directory back at once also restores the original fault.

Will Windows XP compatibility mode or a Windows XP simulator make FS2004 work?

Windows XP compatibility mode is not an XP emulator and cannot restore SafeDisc support. It applies selected behaviour and permission adjustments to the program while FS2004 still runs under Windows 10 or Windows 11.

A properly licensed Windows XP virtual machine is a different approach, but it is often a poor FS2004 platform because 3D acceleration, joystick access and optical-disc pass-through depend on the virtualisation setup. A period PC running a compatible Windows version is more predictable for the original CDs, but an unsupported operating system should be isolated from the internet.

What if FS2004 opens but crashes during a flight?

A simulator that reaches the menus and runs for a while has moved beyond the startup problem. Aircraft gauges, scenery boundaries, AI traffic, memory use and system stability become more likely causes; use our separate diagnostic checklist for random in-flight FS2004 crashes instead of repeatedly reinstalling the base simulator.