FS2004 reinstall issues after removing FSX: missing B737/B747 texture BMP files

FS2004 install stopping at 1% and “missing b737/b747 texture*.bmp”

Damo, when FS9 dies that early in the install and it keeps naming random default texture BMPs (first the 737, then the 747, etc.), it’s almost never “the sim is missing the file” in the real sense. It usually means the installer can’t reliably read the source media (disc/ISO), or something on the PC is interfering with the copy process.

Here’s how I’d tackle it, step-by-step.

1) First, confirm the installer source is actually readable
If you’re installing from an ISO, Windows can mount it fine, but the ISO itself might be incomplete/corrupt.

Quick test:

1. Mount the ISO.
2. Browse into it and locate the CAB files and aircraft folders (don’t run setup yet).
3. Try manually copying the entire contents of the mounted ISO to a folder on your hard drive, like:
   C:\FS9_Install_Files\

4. If Windows throws a “can’t read” / CRC / file in use / device error during the copy, that’s your smoking gun: the ISO/source is bad.

If the full copy completes with no errors, then run the installer from the copied files (not from the mounted ISO).

2) Eliminate “file in use” / AV interference
That message about the BMP being “in another program” can also be caused by security software grabbing files as the installer writes them.

1. Temporarily disable real-time antivirus protection (just for the install).
2. Make sure you’re not opening the aircraft texture folders while the installer is running.
3. Right-click the FS9 setup and choose “Run as administrator”.

3) Install to a simple folder (avoid permission weirdness)
Even though FS9 is older, Windows permissions can still get in the way.

I’d install to something simple like:
C:\FS2004\
(not under Program Files)

4) Don’t patch or “no-CD” anything until the base sim is installed
The no-CD patch won’t help the installer stage, and if it’s mixed into the install attempt it can muddy the water. Get a clean base install first, then worry about updates/patches after it runs.

5) The “empty b747 folder” during the failed install is normal
FS9 creates folders early, then populates them as it copies files. If the copy fails, you’ll see empty aircraft folders left behind. That’s consistent with a read/copy failure, not proof that the folder “should already contain files”.

A couple targeted questions so I don’t send you down the wrong path

1. Are you installing from original CD/DVD media, or only from the downloaded ISO right now?
2. When it fails, do you get any Windows error besides the missing BMP message (CRC error, cyclic redundancy check, “data error”, etc.)?
3. What version of Windows did you reinstall (Windows 10/11?), and is the install being run from an admin account?

If you can answer those, I can tell you whether you’re better off fixing the install source (most likely) or chasing a Windows permission/security issue.