Can I run FS2004 on a modern Mac?

Yes, but Microsoft Flight Simulator 2004 (FS2004/FS9) does not run natively on macOS. An Intel Mac works best by booting Windows through Boot Camp; a virtual machine can also work. On Apple silicon, use Windows on Arm in a virtual machine or a Wine-based layer, but expect less predictable graphics, controller and add-on compatibility.

Which method works on Intel and Apple silicon Macs?

Intel Macs can run FS2004 most reliably in native Windows, while Apple silicon Macs require virtualisation and processor translation.

Boot Camp is available only on Intel Macs. It cannot install or boot Windows on an M-series Apple silicon Mac. Rosetta 2 alone is not enough either: it translates Intel Mac applications, not Windows programs such as fs9.exe.

FS2004's hardware demands are modest, so processor speed is rarely the main obstacle. The difficult parts are its old DirectX renderer, disc authentication and reliance on Windows-era utilities. You can compare FS2004's original requirements with the resources assigned to your virtual machine. Our earlier background on Boot Camp and virtual-machine setups for Intel Macs also explains the underlying platform choices.

How do I install FS2004 on a modern Mac?

Install FS2004 inside a complete Windows environment rather than copying its program folder or fs9.exe directly into macOS.

1. Identify the processor: Open the Mac's system information and look for either an Intel processor or an Apple M-series chip. This determines whether Boot Camp is possible.
2. Create the Windows environment: On Intel, choose Boot Camp for maximum compatibility or a virtual machine for convenience. On Apple silicon, install a supported Windows on Arm virtual machine and use a valid Windows licence.
3. Install the platform drivers: Boot Camp needs Apple's Windows drivers. A virtual machine needs its integration tools, virtual display driver and 3D acceleration enabled before FS2004 is installed.
4. Connect the installation media to Windows: Pass a USB optical drive through to Windows, or mount a lawful image made from your own discs where permitted. The installer must see the media inside Windows, not merely in Finder.
5. Use a simple local folder: A path such as C:\FS2004 avoids many permission and file-redirection problems associated with Program Files. In a virtual machine, install on its Windows disk rather than a shared macOS folder.
6. Test the stock simulator first: Launch a default aircraft at a default airport in windowed mode. Confirm sound, graphics and controls before applying updates or installing scenery, aircraft and utilities.
7. Add extras individually: Restart FS2004 after each major add-on. If it then stops loading, the most recently installed gauge, module or scenery package is the first item to remove.

Why does FS2004 fail after installation?

The usual launch blockers are obsolete disc authentication, an unconfigured virtual GPU, protected installation folders and incompatible add-ons.

• The simulator requests a disc or does nothing: Modern Windows may refuse to load FS2004's legacy disc-checking component. For a legally owned copy, see our FS2004 no-CD patch information and download. Back up fs9.exe, and ensure the replacement matches the installed simulator version; a 9.0 executable should not replace a 9.1 executable.
• The screen is black, white or badly stretched: Install the virtual machine's display tools, enable its supported 3D acceleration and begin with a fixed Windows resolution. Windowed mode is often easier to stabilise than full-screen mode under Retina scaling.
• FS2004 crashes after the splash screen: Start without third-party aircraft, gauges or modules. A clean configuration can also isolate a corrupt graphics setting. Once FS2004 is running inside Windows, the same FS2004 launch fixes for Windows 10 and 11 apply to the guest system.
• Settings will not save: Avoid running the simulator from a read-only disc image, a shared macOS directory or a protected Windows folder. Confirm that the Windows user can write to the FS2004 and configuration directories.
• The installer cannot find the CD: Attach the optical drive directly to the Windows guest. Seeing the disc in macOS does not guarantee that the virtual machine can access it.

Will FS2004 add-ons and joysticks work on a Mac?

Most file-based aircraft, textures and scenery can work inside Windows, but hardware utilities and older executable installers are less certain.

Basic USB joysticks and yokes using standard human-interface drivers have the best chance. In a virtual machine, assign the controller to Windows rather than macOS. Vendor control panels, force-feedback drivers and other low-level software may lack Windows on Arm support even when the basic axes and buttons are recognised.

Aircraft with compiled gauges, external weather programs, AI utilities and add-ons that install system drivers need individual testing. Very old installers can also fail even when their underlying FS2004 files remain usable. Keeping a clean backup of the working FS2004 folder makes experimentation far easier.

For an Intel Mac, Boot Camp remains the closest equivalent to running FS2004 on a conventional PC. On Apple silicon, a Windows on Arm virtual machine is the most practical first choice, but it cannot guarantee compatibility with every disc edition, graphics feature or legacy add-on.