Why does FS2004 freeze in windowed mode?

FS2004 usually freezes in windowed mode because its saved display state is corrupt, a modern graphics-driver override or overlay conflicts with DirectX 9, or an add-on blocks the simulator’s main thread. Resetting FS9.cfg, testing default aircraft and scenery, and removing external graphics overrides fixes most cases.

What causes an FS2004 windowed-mode freeze?

The point at which FS2004 stops responding usually identifies the cause more reliably than the frozen picture itself.

How do I fix FS2004 freezing in windowed mode?

Work through these fixes in order, testing the same default flight after each change so that you know which action solved the problem.

1. Reset FS9.cfg. Close FS2004, press Win+R, enter %APPDATA%\Microsoft\FS9, and rename FS9.CFG to FS9.CFG.old. FS2004 will generate a clean configuration when it next starts. This resets display options, window information and many custom preferences, so keep the old file as a backup. Our safe FS9.cfg backup and reset guidance explains what to preserve and why copying the entire old file back can restore the fault.
2. Confirm that FS2004 is updated. A boxed installation should have the official FS2004 9.1 update. If the updater reports modified or unexpected files, repair the original installation before trying to force the update.
3. Remove external graphics overrides. Reset the driver profile for fs9.exe to its defaults and let the simulator control anti-aliasing and filtering during the test. Disable overlays, recording hooks, external frame limiters, post-processing injectors and third-party DirectX wrappers. Back up and remove only files that you know were added by those tools; never delete a Windows DirectX file.
4. Use conservative display settings. Select the correct display adaptor, use a finite frame-rate target rather than Unlimited, and temporarily reduce clouds, traffic and scenery complexity. If this turns the freeze into smooth operation, restore settings individually. Our recommended FS2004 graphics and frame-rate settings show which options are most likely to overload the simulator.
5. Test Windows scaling and monitor placement. Start FS2004 on the primary monitor and temporarily use matching display scaling across multiple screens. If scaling is above 100%, open the compatibility properties for fs9.exe, select the high-DPI settings option and test the application-controlled scaling override. Avoid combining several compatibility modes at once; they make diagnosis harder and can introduce a different fault.
6. Remove add-ons from the test. Load a default aircraft at a default airport in clear weather. Disable known third-party modules, custom scenery and AI packages one category at a time. Move only add-on files you can positively identify—renaming the whole Modules or Gauges folder will also remove files FS2004 needs.
7. Repair the graphics environment. If the problem began after a display-driver change, use a clean driver installation or return to the previous stable driver. Missing legacy DirectX components should be restored with the official Microsoft runtime package, not with individual DLL files obtained elsewhere.

Why does FS2004 freeze only when I press Alt+Enter?

An Alt+Enter freeze points towards a failed display transition rather than an aircraft or flight-model problem.

Allow the flight and scenery to finish loading before switching modes, press Alt+Enter once, and wait for the display to redraw. Repeated key presses can queue several mode changes while FS2004’s main thread is busy. If a restored window works but maximising it does not, reset FS9.cfg and check DPI scaling before changing any scenery settings.

If returning to full screen also produces a black screen or lock-up, follow our separate Windows full-screen compatibility checks for FS2004.

Why does one aircraft or airport trigger the freeze?

A repeatable freeze tied to one aircraft or location is normally an add-on fault, even when it appears only in windowed mode.

Aircraft panels contain gauges that execute inside fs9.exe; a stalled or incompatible gauge can freeze the whole simulator. Test the aircraft with a known-good panel, then check its panel and sound packages. A location-specific freeze instead points towards scenery, an AI model loaded near that airport, or duplicate scenery layers.

Do not assume the last scenery package installed is the only suspect. AI aircraft may appear only at certain times and airports, while a global module can remain active even after selecting a default aeroplane.

Is FS2004 frozen or still loading?

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

If disk activity continues and the simulator eventually recovers, reduce traffic or scenery complexity and test again. A genuine hang usually repeats at the same action, never recovers, and may leave audio looping. High use of one logical processor alone does not prove a fault because much of FS2004’s workload is single-threaded.

Should I reinstall FS2004?

Reinstallation should be the last step because it often leaves the per-user FS9.cfg—and therefore the windowed-mode fault—untouched.

Reinstall only if a clean FS9.cfg, default aircraft, default scenery, driver defaults and standard monitor scaling all fail. Use a simple installation folder outside the protected Program Files directories, apply the official update, test the untouched simulator, and then restore add-ons in small groups. A mistake we see constantly is copying every old configuration and module straight back, which also copies the original freeze back.