Fix FS2004 install and launch failures on Windows 8.1, including ATC.dll errors, FS9.1 mismatches, permissions and legacy disc checks.
FS2004 can install and run on Windows 8.1, but protected folders, legacy disc copy protection, a damaged installation or a mismatched ATC.dll often stop it. Install outside Program Files as administrator, test the unmodified simulator, restore the original ATC.dll, then apply the FS9.1 update before adding any modifications.
What does an ATC.dll error mean in FS2004?
An ATC.dll startup error usually means that FS2004's core files belong to different builds, rather than there being a fault with an ATC setting. The most common combination is an FS9.0 fs9.exe with an FS9.1 ATC.dll, or the reverse.
This can happen when an old executable is restored after updating, when the FS9.1 patch is applied over modified files, or when a reinstall is placed over a dirty FS2004 directory. A replacement or no-CD executable can create the same mismatch. Do not download an individual ATC.dll or executable from an unverified source; the two core files need to come from the same legitimate installation and update level.
| Symptom | Likely cause | Correct action |
|---|---|---|
| The installer will not open or cannot write files | Permissions, protected folder or damaged disc | Run the installer as administrator and use a folder outside Program Files |
| “Error loading ATC.dll” appears at launch | Mixed or damaged FS9.0 and FS9.1 files | Restore a complete matching file set, then update cleanly |
| The FS9.1 updater rejects ATC.dll | The base file has already been changed | Restore the original file or perform a clean reinstall before patching |
| FS2004 installs but fails the CD check | Legacy disc protection is blocked | Treat this as a SecDrv compatibility issue, not an ATC.dll fault |
What is the safest repair order?
- Back up user content only. Save your aircraft, scenery, gauges, effects and flight files. Do not carry an old
fs9.exeorATC.dllinto the repaired installation. - Remove the dirty installation. Uninstall FS2004 through Windows, then rename any folder left behind. Reinstalling into the same folder can preserve the mismatched DLL that caused the error.
- Install the base simulator as administrator. Run the main installer from the first disc and choose a simple location such as
C:\Games\FS2004. AvoidProgram Files, where Windows permissions and file virtualisation can split files between the real directory and VirtualStore. For copy or permission failures, use our FS2004 installer write-error checks. - Launch the unmodified FS9.0 installation once. Use the correct disc and test a default aircraft before installing the update or any add-on. If the base simulator will not start, patching it will obscure the original problem.
- Apply FS9.1 to pristine files. Run the updater as administrator and use the package matching the installation language. Our correct FS9.1 patching sequence covers the file checks and update order; the official FS2004 9.1 updater is available in our library.
- Stop if the updater rejects ATC.dll. Do not force the patch or replace only that DLL. Restore a known-original file from the same base installation, or repeat the clean installation if no untouched backup exists.
- Test FS9.1 before restoring add-ons. Add aircraft, scenery and utilities in small groups. This identifies the package responsible if a core file is changed again.
Why does FS2004 install but still not launch on Windows 8.1?
A successful installation followed by no launch can be caused by permissions, compatibility settings, a corrupt configuration or the original disc check. Our Windows 8 and 8.1 compatibility notes for FS2004 cover the broader operating-system issues.
Does Windows XP compatibility mode help?
Run setup.exe, the FS9.1 updater and fs9.exe as administrator first. If FS2004 still fails, apply Windows XP Service Pack 3 compatibility mode to fs9.exe. Change one setting at a time; stacking several compatibility options makes it harder to identify the actual fix.
If there is no ATC.dll message, rename %APPDATA%\Microsoft\FS9\FS9.cfg to FS9.cfg.old. FS2004 will create a clean configuration at its next launch. Also remove only known third-party modules while testing and check whether security software has quarantined a core file.
What if Windows 8.1 blocks the FS2004 disc check?
Some FS2004 disc releases rely on the obsolete SecDrv service, which security updates may disable. This normally presents as a CD authentication failure or a launch that stops immediately; it does not produce a genuine ATC.dll version error.
On a dedicated legacy system, the service can be started temporarily from an elevated Command Prompt if it still exists. Run sc config secdrv start= demand followed by sc start secdrv. The space after start= is required. When finished, run sc stop secdrv and sc config secdrv start= disabled.
SecDrv was disabled because of a security vulnerability, and Windows 8.1 itself is out of support. A dedicated offline legacy installation is safer than leaving the service enabled. If Windows says the service does not exist, do not download a replacement driver or modified FS9 executable.
What if FS2004 starts but default ATC is silent?
Silent or unresponsive ATC is a different fault from an ATC.dll launch error. Test with a default aircraft and airport, confirm the avionics and radio are powered, open the ATC window, check voice and communications sound levels, and remove voicepack or ATC modifications temporarily.
If the simulator runs after the clean FS9.1 update but ATC fails only after restoring an add-on, remove that add-on rather than replacing ATC.dll. Keeping the matching FS9.1 executable and core DLL set intact prevents the startup error from returning.