Fix the FS2004 MSVCR70.DLL error by restoring FS9.exe, matching version 9.0 or 9.1, checking legacy add-ons and avoiding unsafe DLL sites.
An MSVCR70.DLL error in Microsoft Flight Simulator 2004 (FS2004/FS9) usually comes from a replacement FS9.exe or legacy add-on built with the Visual C++ 7.0 runtime. Restore the original executable, then use only a replacement matching version 9.0 or 9.1. Never download a loose DLL from a DLL site.
Why does FS2004 ask for MSVCR70.DLL?
MSVCR70.DLL is the C runtime used by software compiled with Microsoft Visual C++ 7.0. Windows displays the error when the executable, module or gauge requesting that runtime cannot find a compatible copy.
If the message started immediately after replacing FS9.exe, that replacement is the prime suspect. If it began after installing an aircraft, panel or utility, a third-party module or gauge may be responsible instead.
| When the error appeared | Most likely cause |
|---|---|
After replacing FS9.exe | A version 9.0/9.1 mismatch or incomplete executable package |
| After installing an add-on | A legacy module or gauge requires the Visual C++ 7.0 runtime |
| Only when loading one aircraft | A panel gauge supplied with that aircraft |
| On an apparently stock installation | A damaged or previously modified executable, or a quarantined file |
How do I repair the error safely?
The reliable repair is to return FS2004 to a known-good executable before changing runtimes or Windows settings.
- Back up the existing files. Make a copy of
FS9.exeand any recently installed modules or gauges before removing or replacing them. - Restore the original FS9.exe. Use your backup or original installation media. If the original executable launches correctly, the replacement executable caused the error.
- Match the executable to the simulator version. For a version 9.1 installation, use a replacement FS9.exe intended specifically for FS2004 9.1. An original, unpatched installation requires the corresponding replacement for the base FS2004 release. Do not mix them.
- Restore the original executable before updating. The FS2004 9.1 updater expects the unmodified file and may reject or mishandle a previously replaced
FS9.exe. - Test recent add-ons separately. Temporarily remove only the third-party module, gauge or panel installed immediately before the error. Keep a backup and do not delete default files based solely on their names.
- Check antivirus quarantine history. If a file was removed, verify that its package came from a trusted source before restoring it. Do not disable protection merely to force an unknown executable to run.
How can I tell whether FS2004 is version 9.0 or 9.1?
Check the version information in the simulator's About window, if it starts, or open the Properties and Details tab for the original FS9.exe. Do not rely on the installation folder name or assume that 9.1 is installed because an updater was downloaded.
If the version is uncertain, restore the original executable first. Apply the official 9.1 update to that original installation, confirm that FS2004 launches, and only then install a replacement executable explicitly made for 9.1.
Should I download MSVCR70.DLL separately?
No. Loose DLL download sites provide no dependable way to verify the file's origin, architecture or exact build, and placing an arbitrary copy in the Windows system folders can create additional failures.
Installing a modern Visual C++ Redistributable is not a direct substitute either; later runtime releases do not replace every older major version. If a particular add-on needs MSVCR70.DLL, reinstall that add-on from its original trusted package so its required runtime is deployed as intended. Running regsvr32 will not help because this runtime DLL is not a COM component that needs registration.
What if FS2004 still fails with the original executable?
If the original FS9.exe produces the same error, isolate recently installed modules and gauges, then repair or reinstall FS2004 while preserving backups of your add-on folders. Test the simulator in stock form before putting third-party files back one group at a time.
If the DLL message disappears but FS2004 still closes while loading, use our FS2004 startup-crash troubleshooting sequence to check configuration files, compatibility settings and add-on conflicts.