How do I fix 'Not enough available memory' in FS2004?

In FS2004 (FS9), “Not enough available memory” usually means the simulator has exhausted its 32-bit virtual address space, not that the PC lacks physical RAM. Install the FS9.1 update, keep a system-managed page file, reset FS9.cfg, then reduce scenery, texture and AI load and isolate faulty add-ons.

Why can FS2004 run out of memory on a modern PC?

FS2004 is a 32-bit application with a finite per-process address space, even when it runs on 64-bit Windows with plenty of installed RAM. A large allocation can fail before Windows Task Manager shows the computer’s physical memory as full, especially after FS9 loads detailed scenery, aircraft textures, gauges, clouds and AI models.

Installing more RAM can help Windows generally, but it does not make fs9.exe a 64-bit programme. Our explanation of FS2004’s 32-bit memory ceiling covers this distinction in more detail.

How do I fix the FS2004 memory error?

The fastest reliable fix is to return FS2004 to a low-load default state, then add complexity back one item at a time.

1. Back up the configuration files. Close FS2004 and make copies of FS9.cfg and scenery.cfg. Rename FS9.cfg to FS9.cfg.old; FS2004 will create a clean replacement when it starts. This resets display and other preferences, so do not delete the backup.
2. Confirm that FS9.1 is installed. The official update should be your troubleshooting baseline. Follow our steps for applying the official FS9.1 update. If the updater rejects a modified executable, restore the original FS2004 files rather than forcing the patch.
3. Check disk space and the Windows page file. Leave free space on the Windows system drive and the drive containing FS2004. Set virtual memory to system-managed unless another application requires a specific configuration, then restart Windows. A page file cannot remove FS9’s address-space ceiling, but disabling it or setting it too small can cause allocation failures sooner.
4. Run a default baseline flight. Create a new flight with the default Cessna, a simple default airport, fair weather, AI traffic disabled and low scenery settings. Do not begin by loading an old saved flight, because it can restore the aircraft, weather and location that caused the failure.
5. Reduce the largest memory loads. Lower maximum texture size, scenery complexity, autogen density, cloud detail or draw distance, and AI traffic. Change one category at a time. Our setting-by-setting FS2004 performance adjustments show which sliders provide useful reductions without stripping the simulator bare.
6. Disable add-ons in controlled batches. Untick scenery areas in the Scenery Library rather than deleting them, starting with recently installed packages. Test half the suspect layers at a time to narrow the search quickly. For an aircraft-related failure, use a default aircraft first, then test the add-on without optional repaints or replacement textures. Our method for installing and testing add-ons safely helps prevent shared gauges, effects and scenery files from being removed accidentally.
7. Restart between meaningful tests. Scenery and module changes are best tested after restarting FS2004. A mistake we see constantly is changing several sliders, deleting files and installing a patch together; that makes it impossible to identify which change solved the error.
8. Use a clean reinstall only as the final test. Back up personal aircraft and scenery first. After uninstalling, rename any remaining FS2004 folder so orphaned add-on files cannot contaminate the new installation. Test the base simulator with FS9.1 before copying any add-ons back.

How do I identify bad scenery or aircraft?

A controlled comparison tells you whether the failure belongs to the location, aircraft, traffic or saved flight.

• One airport only: load that airport with a default aircraft and AI traffic disabled. If it still fails, disable its local scenery layers in batches. If disabling AI fixes it, the combined number and texture size of nearby AI models is the likely load.
• One aircraft only: load a default aircraft at the same airport and in the same weather. A failure that follows the add-on aircraft points to its panel, gauges, virtual cockpit or texture set rather than the scenery.
• One repaint only: restore the aircraft’s original texture set. Very large or incorrectly formatted textures can consume substantially more address space than the base model.
• One saved flight only: create the flight again manually. A saved flight can restore a demanding aircraft, weather theme or add-on location and make a configuration problem look global.
• Only after long sessions: restart FS2004 between legs and repeat the route with lower scenery, clouds and AI. A predictable time-based failure that disappears with default content indicates address-space pressure rather than insufficient installed RAM.

Should I use a 4 GB patch for FS2004?

Use a large-address-aware, or “4 GB”, modification only after FS2004 is stable with default content and the error occurs predictably in otherwise working, high-detail situations.

On 64-bit Windows, marking fs9.exe as large-address-aware can make up to 4 GB of virtual address space available to the 32-bit process. It does not add physical memory, repair corrupt scenery or guarantee that every old gauge and module will handle higher addresses correctly. The change is unofficial and modifies the executable.

• Consider it when a clean FS9.1 installation works, no single add-on is faulty, and only complex combinations of aircraft, scenery and traffic trigger the error.
• Do not use it as a startup fix. An error before the menu, or one tied to a single aircraft or airport, should be diagnosed directly.
• Back up the original executable. Restore it if add-on installers, utilities or modules begin failing after the change. Never replace it with an unknown downloaded executable.
• Expect little benefit on 32-bit Windows. Changing the operating system’s address split introduces separate limitations and is not a sensible first-line FS2004 fix.