Fix FS2004 hanging on the splash screen by resetting FS9.cfg, isolating modules and scenery, and checking modern Windows installation issues.
FS2004 usually hangs on the splash screen because FS9.cfg is corrupt, a third-party module cannot initialise, an add-on scenery path is unavailable, or the saved default flight is damaged. First regenerate FS9.cfg; if that fails, isolate recently installed modules, scenery and aircraft until FS2004 starts normally.
Is FS2004 really frozen at the splash screen?
FS2004 may remain on its splash screen while rebuilding the scenery database, especially after scenery has been added, removed or moved. Check Task Manager for continuing CPU or disk activity and allow that first rebuild to finish.
Treat it as a genuine hang when the same pause happens on every launch, there is no meaningful disk activity and the menus never appear. If fs9.exe disappears from Task Manager instead, that is a crash rather than a hang; use our startup-crash diagnosis and repair steps.
| What happens | Likely cause | Best first test |
|---|---|---|
| The first launch after changing scenery takes a long time | Scenery database rebuild | Wait while disk activity continues |
| Every launch stops before the menus | Damaged FS9.cfg or startup situation | Regenerate FS9.cfg |
| The problem began after installing a utility | Incompatible module or DLL | Remove that third-party module temporarily |
| Scenery is stored on a disconnected drive | Unavailable scenery path | Reconnect the drive or deactivate its scenery entries |
| The menus appear, but loading a flight freezes | Aircraft, panel, gauge or flight problem | Load a stock aircraft and airport |
How do I fix an FS2004 splash-screen hang?
Work through these fixes in order, launching FS2004 after each change so that the result identifies the faulty component.
- Close the stalled process. End
fs9.exethrough Task Manager before moving or renaming any files. Do not repeatedly start additional copies while the original process remains open. - Regenerate FS9.cfg. Open
%APPDATA%\Microsoft\FS9and renameFS9.cfgtoFS9.cfg.old. FS2004 creates a clean configuration on its next launch. This resets display, control and startup-flight settings but does not delete installed aircraft or scenery. If this fixes the hang, reapply necessary settings manually instead of copying the entire old file back. Our guide to backing up and editing FS9.cfg safely explains the file location and regeneration process. - Isolate third-party modules. Open the
Modulesfolder inside the FS2004 installation and move only known third-party DLLs to a temporary folder outside the simulator. Leave the original Microsoft files in place. Common candidates include older versions of FSUIPC and modules supplied with weather, traffic, hardware or aircraft packages. Restore them one at a time after FS2004 launches successfully. - Check add-on scenery paths. Reconnect any external or network drive containing scenery. If the location is no longer available, back up
scenery.cfgand deactivate the affected add-on areas rather than deleting default scenery folders. A recently installed airport or malformed scenery entry can also hold up the database scan, so disable the newest areas first. - Remove the saved-flight variable. Regenerating FS9.cfg normally resets the startup situation. If the menus now appear but a flight still freezes, select a default FS2004 aircraft at a default airport. Move only recently installed aircraft folders out of the simulator and test again; a panel or gauge may be loading with the saved aircraft.
- Test a clean, correctly updated baseline. Confirm that stock FS2004 starts before returning add-ons. Apply the official FS9.1 update in the correct order and avoid mixing patched files with an older or modified executable; our FS2004 patch and repair sequence covers that process.
Why does the hang return when add-ons are restored?
If FS2004 starts cleanly but hangs after add-ons return, one restored component is incompatible, damaged or installed in the wrong folder. Add packages back in small groups, then split the failing group until the exact file is identified.
- Restore modules before aircraft only if a dependent aircraft requires them.
- Keep FS2004 and FSX or Prepar3D versions of DLLs and gauges separate.
- Do not overwrite a working shared gauge merely because an older aircraft package includes another copy.
- Retest after every scenery-library change and keep external scenery drives connected during startup.
- Do not restore the old FS9.cfg wholesale; copy only settings you understand.
What if a clean FS2004 installation still hangs?
A completely stock installation that still hangs points to Windows permissions, damaged programme files, security software interference or an installation incompatible with modern Windows.
Installing under a protected folder can also split files between the real FS2004 directory and Windows VirtualStore. Do not reinstall directly over an add-on-filled directory, because leftover modules and scenery can immediately recreate the fault. Use our modern-Windows launch and installation checks for permissions, compatibility and clean-install guidance.