Why does FS2004 freeze in windowed mode?

FS2004 (FS9) usually freezes in windowed mode because its saved display state in FS9.CFG is damaged, a modern overlay or graphics-driver override is interfering with its older DirectX renderer, or an add-on has stalled the main thread. Resetting FS9.CFG, testing a stock flight, then isolating display hooks and add-ons usually identifies the fault.

What causes an FS2004 windowed-mode freeze?

The action that triggers the freeze is the best clue to its cause.

How do I fix FS2004 freezing in windowed mode?

Change one thing at a time and repeat the same stock flight after every step; otherwise, you will not know which change fixed the freeze.

1. Reset FS9.CFG. Close FS2004, press Win+R and enter %APPDATA%\Microsoft\FS9. Rename FS9.CFG to FS9.CFG.old, then start FS2004 so it creates a clean file. This resets display settings, saved window information and some control preferences, so retain the old file as a backup. Do not copy the whole old configuration back after a successful test, because that can restore the fault.
2. Create a controlled stock flight. Use a default aircraft, a stock airport, clear weather and no saved flight. Set AI traffic to zero for the first test. A saved flight can reference missing aircraft, weather or scenery and make a display problem look more complicated than it is.
3. Confirm the official 9.1 update is installed. A base disc installation should be updated before add-ons are introduced. If the updater rejects modified core files, restore or repair the original installation rather than forcing the update over altered files.
4. Remove anything that hooks into the display. Disable recording tools, frame limiters, graphics overlays, monitoring displays, post-processing injectors and third-party DirectX wrappers. Reset the graphics-driver profile for fs9.exe to its defaults and allow FS2004 to control anti-aliasing during the test. Remove only wrapper files you positively recognise as third-party additions; never delete Windows DirectX files.
5. Test DPI scaling and monitor placement. Run FS2004 on the primary monitor and temporarily use the same scaling percentage on every connected display. If Windows scaling is above 100%, open the compatibility properties for fs9.exe, enter the high-DPI settings and test the scaling override with the application controlling scaling. Do not enable several compatibility modes together. Running as administrator is not a universal display fix, and disabling full-screen optimisations does little for a true windowed-mode fault.
6. Reduce the workload. Select a finite target frame rate instead of Unlimited, then lower clouds, autogen, scenery complexity and traffic. If FS2004 becomes stable, restore settings individually until the failing combination appears. Our modern-PC checks for FS2004 freezes and poor performance cover the settings that most often overload its largely single-threaded engine.
7. Isolate add-ons by category. Disable custom scenery through the Scenery Library, remove known third-party modules from the test and try stock aircraft. Do not rename the entire Modules or Gauges folder: both can contain files required by FS2004 or other working aircraft. Restore add-ons in small groups once the stock simulator is stable.
8. Repair the graphics environment last. If the fault began immediately after a graphics-driver change, perform a clean installation of that driver or return to the previous known-working release. Restore missing legacy DirectX components only from Microsoft’s official runtime package; individual DLL downloads are unsafe and can introduce a second problem.

Why does FS2004 freeze when I press Alt+Enter?

A freeze caused specifically by Alt+Enter points to the display transition, window coordinates or scaling rather than the aircraft flight model.

Wait until the cockpit and surrounding scenery have finished loading, press Alt+Enter once, and allow the display to redraw. Repeated presses can queue several mode changes while FS2004’s main thread is already busy. If a normal restored window works but maximising it freezes, reset FS9.CFG and test Windows DPI scaling before changing scenery or aircraft.

If audio continues and Windows still updates the taskbar preview, the FS2004 window may be off-screen rather than frozen. Move it back to the primary display using Windows’ move-window command, then close FS2004 normally so the corrected position can be saved.

A black screen or lock-up when returning to full screen needs a different branch of diagnosis; use our FS2004 full-screen fixes for Windows 10 and 11.

Why does one aircraft or airport trigger the freeze?

A freeze tied consistently to one aircraft or location is usually an add-on fault, even if windowed mode makes it easier to trigger.

Aircraft panels run gauges inside fs9.exe. A stalled gauge, damaged panel file, incompatible sound package or shared module can therefore stop the whole simulator. Test the same flight with a default aircraft; if that works, follow the panel, gauge and shared-file checks for add-on aircraft.

For a location-specific freeze, set airline and general-aviation traffic to zero before disabling scenery. AI aircraft may be loaded only at a particular airport and time, so the scenery is not always responsible. If traffic makes no difference, investigate damaged BGL files, duplicate airport files and scenery-library priority using our method for isolating FS2004 scenery conflicts.

Is FS2004 frozen or still loading?

Windows can label FS2004 as not responding while its main thread is still loading dense scenery, textures, gauges or AI traffic.

If storage activity continues and the simulator eventually recovers, reduce traffic and scenery complexity and repeat the test. High use of one logical processor is normal for FS2004 and does not prove that it has hung. A genuine freeze normally repeats at the same action, never recovers and may leave a short section of audio looping.

Avoid clicking repeatedly or pressing Alt+Enter while loading is in progress. Those extra requests can turn a slow load into an apparent display lock-up.

Nichts hat geholfen: what should I test next?

If nothing has helped — nichts hat geholfen — stop adding compatibility switches and use clean-control tests to separate a Windows profile fault from an FS2004 installation or graphics problem.

Keep a short record of each test and its result. Changing the driver, compatibility mode, configuration and add-ons together destroys the evidence needed to identify the cause.

Should I reinstall FS2004?

Reinstallation is the last step because uninstalling FS2004 may leave its per-user configuration and third-party files behind.

1. Back up personal content. Preserve saved flights and add-ons separately, but do not plan to restore them before the clean simulator has been tested.
2. Remove leftovers safely. After uninstalling, rename rather than delete the remaining FS2004 installation folder and the old %APPDATA%\Microsoft\FS9 folder. Installing over a modified directory is not a clean test.
3. Use an unprotected folder. Install into a simple location outside Program Files, such as C:\Games\FS2004. This avoids file-virtualisation and permission problems associated with older add-ons.
4. Test the untouched simulator. Apply the official 9.1 update, create a stock flight and confirm that windowed mode works before installing aircraft, scenery or utilities.
5. Restore add-ons gradually. Add one category or small group at a time. Restore the old FS9.CFG last, if at all; copying it back immediately is a common way to recreate the original freeze.

If a clean, updated installation still freezes with a stock aircraft, one monitor, default driver settings and no injected software, the remaining cause lies outside the add-on library. Concentrate on the graphics driver, Windows user profile and display configuration rather than reinstalling FS2004 again.