Run FS2004 on Windows 10 or 11 with the right install path, 9.1 update and compatibility settings, plus fixes for SafeDisc and crashes.
FS2004 can run on Windows 10 and 11, but the original disc edition may be stopped by its obsolete SafeDisc copy protection. Install it outside Program Files, apply the official 9.1 update, test it in windowed mode, and change compatibility settings only when needed; administrator mode alone cannot repair the blocked disc check.
Install FS2004 for modern Windows
- Choose a writable installation folder. Use a simple location such as
C:\FS2004orC:\Games\FS2004, rather thanProgram Files. This prevents many UAC-related problems with configuration files, scenery and older add-on installers. - Run the installer from the original media. Start normally, then use Run as administrator only if setup reports a permission or write error. Follow the prompts to change discs and keep the same destination folder throughout.
- Apply the official FS2004 9.1 update. Install it before adding aircraft, scenery, gauges or modules. The updater needs an unmodified installation and must point to the correct FS2004 folder.
- Make the first flight with default content. Use a default aircraft and airport so an incompatible add-on cannot be mistaken for a Windows problem. The standard four-CD edition normally asks for Disc 4 when starting.
- Test windowed mode. Press
Alt+Enterafter FS2004 opens. Once the simulator works reliably, set the desired resolution and test full-screen operation. - Add extras gradually. Install one aircraft, scenery package or module at a time and launch FS2004 after each change.
Our step-by-step Windows 11 installation procedure covers disc installation, folder selection and the 9.1 update in more detail.
Does FS2004 need compatibility mode on Windows 11?
FS2004 often runs without compatibility mode, so begin with every compatibility option disabled. Applying several fixes at once can introduce new path, permission or display problems and makes the real cause harder to identify.
| Setting | When to use it |
|---|---|
| No compatibility mode | Use this for the first clean launch. |
| Run as administrator | Use temporarily for a confirmed write or permissions error. It does not fix SafeDisc. |
| Windows XP compatibility | Try this only when a clean FS2004 installation or a specific old add-on will not behave normally. |
| Disable full-screen optimisations | Try it for black screens, broken mode switching or full-screen display faults. |
| High-DPI override | Use application-controlled scaling only if menus or panels are blurred, cropped or incorrectly sized. |
For black screens or failed mode changes, follow our targeted FS2004 full-screen troubleshooting steps rather than changing unrelated settings.
Why does FS2004 say to log on as administrator?
On an original CD installation, an administrator warning can actually mean that Windows has blocked the old SafeDisc driver. Windows 10 and 11 do not support the obsolete secdrv.sys mechanism used by many period disc releases, and the FS2004 9.1 update does not remove that disc check.
Running fs9.exe as administrator or selecting Windows XP compatibility cannot restore a blocked kernel driver. There is no Windows checkbox that converts the original protected executable into a modern one.
Use only a lawfully supplied release or executable that does not depend on the blocked driver. Otherwise, the dependable option is a dedicated legacy Windows installation kept offline; a virtual machine may work, but its 3D acceleration and joystick support can be inadequate. Do not install random copies of secdrv.sys, patched executables or individual DLL files from untrusted archives.
If the failure is not clearly the disc check, our modern-Windows launch diagnosis separates SafeDisc errors from damaged configuration files, permissions and incompatible add-ons.
Where should FS2004 add-ons be installed?
Add-ons should go into the actual FS2004 installation tree, not merely the folder suggested by an old installer. Aircraft normally belong under Aircraft, while scenery packages are commonly placed under Addon Scenery and then activated inside the simulator.
A mistake we see constantly is accepting an installer path left over from an older computer or previous FS2004 installation. Confirm the destination manually, and do not merge an entire old installation into a clean one until the unmodified simulator has launched successfully.
What should I do if FS2004 opens but then crashes?
First rename FS9.cfg so FS2004 generates a clean configuration file at the next launch. The normal per-user location is beneath %APPDATA%\Microsoft\FS9; renaming preserves the old file if settings later need to be recovered.
Then test a default aircraft at a default airport in windowed mode. If that works, restore add-ons in small groups, concentrating on old gauges, modules, AI traffic and dense scenery. FS2004 is a 32-bit application, so installing more system RAM does not remove its limited process address space.
Persistent in-flight failures need a different process from installation faults; our FS2004 crash-isolation procedure covers configuration resets, add-on testing, graphics settings and memory pressure.