Fixing "Cannot locate the Microsoft Visual FoxPro support library"

Programs written in Visual FoxPro don’t run on their own. They depend on a set of runtime files, usually called the support library, which have to be present and registered on the PC. When Windows can’t find the right ones, the program stops before it opens and shows this message.

It usually appears after a new PC arrives, Windows is reinstalled or upgraded, someone runs a “clean-up” tool, or the program is copied to a new machine without its supporting files. The program itself is almost always fine. It just can’t find what it needs.

Before changing anything, take a copy of the program folder and its data. It costs nothing and it means every step below can be undone.

Step 1: work out which version you need

Each version of Visual FoxPro has its own runtime, and they aren’t interchangeable. The main files are named after the version: vfp6r.dll, vfp7r.dll, vfp8r.dll or vfp9r.dll.

Sometimes the error message names the file it’s looking for. If not, look in the program’s folder on an old PC where it still works, or check the program’s file properties for clues. Most business applications still in use were built with version 9.

Step 2: install or copy the matching runtime

The cleanest fix is to install the runtime package for that version. Microsoft no longer hosts these, so get them from a reputable FoxPro community source rather than a random download site. Unofficial “DLL download” sites are a common source of malware, and a business PC is the last place you want it.

Alternatively, copy the runtime files from a working PC into the program’s own folder. For version 9 that usually means vfp9r.dll, vfp9renu.dll, msvcr71.dll and gdiplus.dll. Programs look in their own folder first, so this often works without touching Windows at all.

Step 3: register the library if needed

If copying the files isn’t enough, the runtime may need registering. Visual FoxPro is 32-bit, so on 64-bit Windows the files belong in C:\Windows\SysWOW64 and must be registered with the 32-bit copy of regsvr32 that lives in that same folder, from a command prompt run as administrator.

Using the 64-bit regsvr32 by mistake is one of the most common reasons this fix appears not to work.

If it still won’t start

There are three other things worth checking:

• Network shares. Running the program directly from a mapped drive can be blocked by Windows security settings. Try running a local copy.
• Antivirus. Some security tools quarantine old runtime files. Check the quarantine list and add an exception if needed.
• Other components. Many applications also rely on ActiveX controls, report writers or database drivers, which produce similar “cannot find” symptoms.

The bigger picture

If this error has appeared, it’s a sign the system is running on borrowed time. Visual FoxPro has been out of Microsoft support since 2015, and every Windows update or PC replacement makes problems like this more likely. The next one might happen at month end, or after the one person who knows the fix has left.

That doesn’t mean you have to replace it tomorrow. It does mean it’s worth knowing your options. Our guide to Visual FoxPro end of life sets them out.