mfc90.dll Missing: The Right Visual C++ Fix for Windows

mfc90.dll errors usually mean that an older program cannot find the Microsoft Visual C++ 2008 MFC runtime it was built to use. The safest fix is to identify the affected application, install or repair the matching official Visual C++ 2008 package, and then repair the application if the error remains.

Do not begin by downloading a loose DLL from a random website. A single file may have the wrong architecture, servicing level, companion files, or manifest, and it may be unsafe.

As an Amazon Associate I earn from qualifying purchases.

Start with this diagnostic checklist

Before changing anything, record four details:

• Which program, game, installer, or startup component displays the error
• Whether the message appears when launching that program or immediately after signing in
• Whether the affected program is 32-bit or 64-bit
• The exact wording of the error

The application’s architecture matters more than the architecture of Windows. A 32-bit application needs the x86 runtime even when it is running on 64-bit Windows. A 64-bit application needs the x64 runtime.

If you are unsure, install both official Visual C++ 2008 packages on 64-bit Windows. They can coexist and support different applications.

What mfc90.dll is

mfc90.dll is part of the Microsoft Foundation Classes runtime from Microsoft Visual C++ 2008, also known as Visual C++ 9.0. MFC is a C++ framework that wraps many Windows and COM programming interfaces. Applications built with the dynamically linked MFC library need the matching runtime files installed before they can start.

Microsoft lists mfc90.dll among the files in the Visual C++ 2008 SP1 redistributable. Related files include:

• mfc90u.dll, the Unicode MFC runtime
• mfcm90.dll and mfcm90u.dll, additional MFC runtime components
• msvcr90.dll, the Visual C++ C runtime
• msvcp90.dll, the Visual C++ C++ standard library runtime
• msvcm90.dll, a managed C++ runtime component
• atl90.dll, the ATL runtime
• vcomp90.dll, the OpenMP runtime

The 90 identifies the Visual C++ 2008 generation. Other Visual C++ generations use different names:

Visual C++ generation	Typical MFC filename
Visual C++ 2008	mfc90.dll
Visual C++ 2010	mfc100.dll
Visual C++ 2012	mfc110.dll
Visual C++ 2013	mfc120.dll
Visual C++ 2015 and later	commonly mfc140.dll

This is not a general Windows component that every installation is guaranteed to contain. It is normally installed by the Visual C++ redistributable, an application installer, or an application’s private runtime files.

It is also not a .NET file, DirectX file, or hardware driver. A game or utility may use all of those technologies, but they are separate dependencies.

Fix 1: Install or repair Visual C++ 2008 SP1

This is the most likely solution for a genuine missing-runtime error.

Use Microsoft’s official Visual C++ 2008 SP1 Redistributable download page. The page provides separate packages for x86, x64, and legacy Itanium systems.

Choose the correct package

• Install vcredist_x86.exe for a 32-bit application.
• Install vcredist_x64.exe for a 64-bit application.
• Install both x86 and x64 on 64-bit Windows if you use older software with mixed architectures.
• Ignore the IA64 package unless you are maintaining a legacy Itanium system.

A 64-bit Windows installation can run 32-bit applications through its compatibility subsystem, but that does not make those applications use the x64 Visual C++ runtime. The application and redistributable architectures must match.

Repair an existing installation

1. Press Windows + I to open Settings.
2. Select Apps.
3. Select Installed apps.
4. Search for Microsoft Visual C++ 2008.
5. Select the three-dot menu beside the matching redistributable.
6. Choose Change, Repair, or the equivalent maintenance option.
7. Follow the installer prompts.
8. Restart Windows.
9. Launch the program again.

On some Windows installations, the older package is easier to manage through Control Panel:

1. Press Windows + R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Find the Microsoft Visual C++ 2008 redistributable entry.
5. Select it and choose Change.
6. Select Repair if available.
7. Restart Windows.

If no Visual C++ 2008 entry exists, download the package from Microsoft and run the installer as an administrator.

How to tell whether this worked

The repair succeeded if the original program opens without the mfc90.dll message. The DLL may not appear in one obvious folder because Visual C++ 2008 can use shared runtime files, side-by-side assemblies, manifests, or application-local deployment.

Do not judge success only by whether you can find a file in System32 or SysWOW64. The loader may be using a side-by-side assembly or a copy installed with the application.

The installer package version and the file version are not necessarily identical. Microsoft’s legacy tables list Visual C++ 2008 SP1 redistributable package version 9.0.30729.5677 for x86 and x64, while the later security update lists mfc90.dll as version 9.0.30729.6161. Seeing a different compatible file version does not automatically prove that installation failed.

Fix 2: Repair or reinstall the affected application

If reinstalling the runtime does not help, the application itself may be incomplete or damaged.

This is common when:

• An installer was interrupted
• A game update failed
• Antivirus software removed an application-local runtime file
• The program was copied from another computer
• The application expects a private manifest or a particular VC90 assembly
• A folder contains an incorrect DLL copied from another release

Repair a normal Windows application

1. Press Windows + I.
2. Select Apps.
3. Select Installed apps.
4. Find the affected program.
5. Open its three-dot menu.
6. Select Advanced options if available.
7. Select Repair.
8. Start the program again.

If Repair is unavailable or does not help, uninstall and reinstall the application from its original vendor, installer, or launcher. Microsoft documents the standard Windows app repair and removal process.

For an older program, run the original installer after installing the correct Visual C++ 2008 package. Some installers create the required manifest and application-local files in addition to installing the main executable.

Verify a game through its launcher

If the error belongs to a game, use the launcher’s file verification or repair feature before manually replacing anything.

For a Steam game, the usual path is:

1. Open Steam.
2. Select Library.
3. Right-click the game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the scan to finish.
8. Launch the game again.

A launcher can restore the exact files and manifests expected by that release. A global runtime reinstall cannot repair a missing game executable, damaged manifest, or incomplete game update.

Fix 3: Check antivirus quarantine

Antivirus software can quarantine an application-local copy of mfc90.dll, block a redistributable installer, or interrupt an application update.

Do not immediately disable protection or restore a file simply because the program needs it. First establish that the application came from a legitimate source.

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review recent detections.
5. Look for the exact program name, DLL path, installer, or update involved.
6. If the detection concerns a legitimate application, obtain a fresh installer from the original vendor.
7. Reinstall the application or runtime rather than downloading a replacement DLL.
8. Restore a quarantined file only after verifying its origin and authenticity.
9. Re-enable protection immediately after any temporary diagnostic change.

Microsoft’s Windows Security Protection History guidance explains how quarantined items are handled.

If the same DLL is repeatedly quarantined, run a full security scan before restoring it. A missing file is not proof of malware, but an unfamiliar executable or unsigned replacement deserves investigation.

Fix 4: Confirm the program’s architecture

An architecture mismatch can look like a missing DLL problem even when a file is present.

Use these approaches to identify the application type.

Check the application documentation

The program’s vendor may list x86 or x64 requirements in its system requirements, installer name, or support documentation.

Check Task Manager

1. Start the affected application if it opens far enough to appear.
2. Press Ctrl + Shift + Esc.
3. Select Details.
4. Find the program’s executable.
5. On some Windows versions, 32-bit processes are marked with (32 bit).

If the application will not start, look at its installation folder and installer name. A folder named Program Files (x86) commonly contains 32-bit applications, while Program Files commonly contains 64-bit applications. This is a useful clue, not an absolute rule.

Install both packages when uncertain

On a 64-bit PC, installing both official Visual C++ 2008 SP1 packages is usually the most practical choice when several old programs are involved:

• x86 for 32-bit software
• x64 for 64-bit software

Do not copy an x86 DLL into a 64-bit application folder or an x64 DLL into a 32-bit application folder. A wrong-bitness file can produce invalid-image errors, “not designed to run on Windows” messages, or error 0xc000007b.

Installing Visual C++ 2010, 2013, or the current 2015-and-later redistributable does not guarantee that an application linked to Visual C++ 2008 will work. These runtime families are version-specific and can be installed side by side.

Fix 5: Diagnose a side-by-side configuration error

Some programs do not report a simple missing file. Instead, Windows may display:

The application has failed to start because its side-by-side configuration is incorrect.

×Worth Installing

PC Slower Than It Used to Be?

Outbyte PC Repair · freeA free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Run a Free PC Scan →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Visual C++ 2008 applications can request a particular Microsoft.VC90.MFC assembly through an application manifest. A missing runtime, wrong architecture, incompatible assembly version, or damaged component store can prevent Windows from creating the application’s activation context.

Check Event Viewer

1. Press Windows + R.
2. Enter eventvwr.msc.
3. Press Enter.
4. Expand Windows Logs.
5. Select Application.
6. Look for events whose source is SideBySide.
7. Read the event details and note the executable, assembly name, and requested version.

If the event mentions Microsoft.VC90.MFC, install or repair the matching Visual C++ 2008 architecture and then repair the affected application.

Use sxstrace

Microsoft provides sxstrace.exe for detailed side-by-side diagnostics.

1. Open Start.
2. Search for Command Prompt.
3. Select Run as administrator.
4. Start tracing:

sxstrace trace -logfile:sxstrace.etl

1. Reproduce the application launch failure.
2. Return to the administrator Command Prompt.
3. Stop tracing with Ctrl + C.
4. Parse the trace:

sxstrace parse -logfile:sxstrace.etl -outfile:sxstrace.txt

1. Open the resulting sxstrace.txt file in Notepad.

The trace can show whether Windows found the requested assembly, rejected its architecture, or could not locate a dependent file. Microsoft documents the command in its sxstrace reference.

Fix 6: Check for a leftover startup program

An mfc90.dll error that appears immediately after sign-in may come from a stale updater, hardware utility, launcher, or assistant. It does not necessarily mean Windows itself needs this runtime.

Check startup apps

1. Press Windows + I.
2. Select Apps.
3. Select Startup.
4. Review entries that start automatically.
5. Turn off the entry associated with the error if the software is no longer needed.
6. Restart Windows.

You can also use Task Manager:

1. Press Ctrl + Shift + Esc.
2. Select Startup apps.
3. Right-click a suspicious entry.
4. Select Disable.
5. Restart and check whether the message returns.

If you need to identify the owner, right-click the startup entry and choose Open file location when available. Record the executable path before disabling or removing anything.

For more difficult cases, Microsoft’s Autoruns utility can show startup entries from registry locations, scheduled tasks, services, and other auto-start locations.

Once the responsible executable is identified, repair or uninstall its parent application. Disabling the startup entry only prevents the error from appearing; it does not repair the application.

Fix 7: Repair Windows components with DISM and SFC

System File Checker and DISM are useful when the problem began after a failed Windows update, storage problem, or broader Windows corruption. They are not the first-line repair for a third-party Visual C++ runtime that was never installed.

Run DISM first, then SFC.

1. Open Start.
2. Search for Command Prompt.
3. Select Run as administrator.
4. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to complete successfully.
2. Run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Test the affected program.

Microsoft provides additional detail in its System File Checker and DISM instructions.

Success means DISM completes without an error and SFC reports that it repaired files or found no integrity violations. If both commands complete but the same application still reports mfc90.dll, return to the Visual C++ architecture, application repair, manifest, and startup checks. Repeating SFC indefinitely will not install a missing Visual C++ 2008 runtime.

If manually hunting through Windows components, installer versions, and repeated SFC/DISM results is taking too long, Outbyte PC Repair can scan for issues and show what it finds; repairs are completed by the full version, and it is not required for this fix.

Fix 8: Update or reinstall the owning application’s drivers and utilities

mfc90.dll is not a driver. However, an older graphics control panel, printer utility, hardware monitor, updater, or driver installer may be an MFC application that depends on it.

Identify the actual executable first. Reinstalling a display or chipset driver alone will not normally provide the Visual C++ 2008 runtime.

Check Device Manager

1. Press Windows + X.
2. Select Device Manager.
3. Expand the category related to the affected hardware.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Note the provider, date, and version.
8. Select Update Driver if an update is available.
9. If the problem began after an update, consider Roll Back Driver when that option is available.
10. Restart Windows.

For vendor utilities, download the complete current software package from the hardware manufacturer rather than searching for mfc90.dll separately. If the utility is obsolete, uninstalling its startup component may be safer than forcing an old control panel to run.

If comparing hardware models, driver dates, and package versions manually is becoming guesswork, Outbyte Driver Updater can scan for outdated drivers and identify what needs attention; driver installation is completed by the full version, and it is not required to repair mfc90.dll.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 9: Use Windows Features only for a separate .NET requirement

Windows Features is not where the Visual C++ 2008 runtime is installed. Do not enable random features in the hope that one will add mfc90.dll.

If the same application separately reports a .NET Framework error, you can check the legacy .NET feature:

1. Press Windows + R.
2. Enter optionalfeatures.
3. Press Enter.
4. Review .NET Framework 3.5, which includes .NET 2.0 and 3.0 components.
5. Enable it only if the application requires it.
6. Select OK.
7. Allow Windows to download or install the required components.
8. Restart if prompted.

.NET and Visual C++ are separate runtime families. Enabling .NET Framework 3.5 will not normally install mfc90.dll.

DirectX is also usually unrelated. The DirectX End-User Runtime supplies legacy DirectX components such as D3DX, XInput, XAudio, and XACT. A game installer may require both DirectX and Visual C++, but reinstalling DirectX alone is not a fix for a missing MFC runtime.

Fix 10: Try System Restore after a recent change

System Restore is appropriate when the error began immediately after installing software, a driver, or an update and a suitable restore point exists.

1. Press Windows + R.
2. Enter rstrui.exe.
3. Press Enter.
4. Select Next.
5. Choose a restore point dated before the problem began.
6. Select Scan for affected programs if available.
7. Review the programs and drivers that will be changed.
8. Select Next, then Finish.
9. Allow Windows to restart.

System Restore normally rolls back system files, settings, and installed programs without changing personal documents. It does not replace the need to reinstall the correct Visual C++ package if the runtime was never installed.

Why regsvr32 usually does not help

Do not run this as a general repair:

regsvr32 mfc90.dll

regsvr32.exe is intended for self-registering DLLs and ActiveX or COM controls that export a registration entry point such as DllRegisterServer. mfc90.dll is a shared MFC runtime and side-by-side library, not an ordinary COM component that users should register manually.

If you run the command, Windows may report:

The module was loaded but the entry-point DllRegisterServer was not found.

×

Quick wins for a faster PC:

Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

That message does not mean the runtime needs registration. It means this particular command does not apply.

Microsoft explains the requirements in its Regsvr32 troubleshooting documentation. Microsoft also documents that side-by-side assemblies are not registered through the traditional COM registry model in its manifest documentation.

A separate ActiveX control may require registration, but that is an application-specific DLL and is not the same as registering mfc90.dll.

Why manually copying mfc90.dll is risky

Do not download mfc90.dll from a random DLL download website and place it in System32, SysWOW64, or the application directory.

That approach can fail because:

• The file has the wrong x86 or x64 architecture
• The file belongs to the wrong Visual C++ 2008 servicing level
• Companion files such as msvcr90.dll or msvcp90.dll are also missing
• The application requires a matching manifest
• The file is modified, unsigned, or malicious
• An incorrect application-local copy overrides the correct shared runtime
• Future servicing no longer applies to the manually copied file

Microsoft supports application-local deployment for developers who intentionally package a complete, matching runtime with their software. For normal users, Microsoft recommends the redistributable package because it can be serviced and repaired centrally. See Microsoft’s guidance on redistributing Visual C++ files.

The safe sources are:

• Microsoft’s official Visual C++ 2008 SP1 redistributable download page
• The original application or game installer
• The official launcher’s repair or file-verification function
• A known-good file restored from the application’s original installation media after its authenticity is established

If the error says “specified module could not be found”

This wording does not always mean that mfc90.dll itself is absent. Windows may have found the named DLL but failed to load one of its dependencies.

Check the following in order:

1. Repair or install the matching Visual C++ 2008 x86 or x64 package.
2. Repair or reinstall the affected application.
3. Check whether antivirus quarantined a companion runtime file.
4. Confirm that the application’s architecture matches the installed package.
5. Check Event Viewer for SideBySide events.
6. Use sxstrace.exe if the message mentions activation context or side-by-side configuration.
7. Look for a stale application-local copy in the program’s own folder.
8. Identify whether the error is actually coming from a startup entry.

Installing only mfc90.dll can leave the underlying dependency failure unchanged.

If the Microsoft installer will not run

When the redistributable installer fails:

1. Install pending Windows updates.
2. Restart Windows.
3. Download the package again from Microsoft’s official page.
4. Right-click the installer.
5. Select Run as administrator.
6. Check Windows Security Protection History for a blocked installer.
7. Record the architecture and any displayed error code.
8. Check %TEMP% for Visual C++ installer logs.
9. Repair or remove a damaged existing Visual C++ 2008 entry only through the matching official installer or Windows Apps settings.
10. Restart and run the installer again.

Do not use a newer Visual C++ redistributable as a substitute for the 2008 package. Microsoft’s Visual C++ redistributable installation troubleshooting guidance covers installer failures, permissions, logs, and antivirus interference.

Frequently asked questions

Is mfc90.dll a Windows system file?

It is a Microsoft runtime file, but it is not an in-box Windows component that every installation must contain. It belongs to the Visual C++ 2008 MFC redistributable and may be installed centrally or privately with an application.

Does the file belong to Visual C++ 2008?

Yes. The 90 in mfc90.dll identifies the Visual C++ 2008 generation, also called Visual C++ 9.0.

Should I install Visual C++ 2015, 2019, or the current package?

Not as a replacement for Visual C++ 2008. Newer runtime families are separate. An application linked against mfc90.dll generally needs the matching Visual C++ 2008 package.

Which package should I install on Windows 11 64-bit?

Use x86 for a 32-bit application and x64 for a 64-bit application. If you use several older programs and do not know their architectures, install both official packages.

Is mfc90.dll malware?

The filename itself is a legitimate Microsoft runtime name. A missing-file message does not prove malware. However, an unfamiliar copy in an unusual folder, a file restored from quarantine, or a program from an untrusted source should be scanned and verified.

Can I place the file in System32?

That is not the normal repair. It can create an architecture mismatch, bypass the correct manifest, or leave companion files missing. Install or repair the official redistributable instead.

Will regsvr32 fix it?

Normally no. mfc90.dll is not an ordinary COM or ActiveX DLL that should be registered with regsvr32.

Why does the error appear during startup?

A leftover updater, assistant, launcher, or hardware utility may still be configured to start with Windows even after its main application was removed or damaged. Check Startup apps, Task Manager, and Autoruns.

Why does reinstalling the runtime not help?

The application may need the other architecture, a private copy, a matching manifest, another dependency, or an application repair. The error may also be coming from a different startup executable than the one you expected.

Should I run SFC first?

Usually no. Start with the correct Visual C++ 2008 redistributable and application repair. Use DISM and SFC when there are signs of broader Windows corruption or when the problem began after a failed update or system error.

What if a new Windows user profile works?

That points toward a per-user startup entry, profile-specific application data, permissions issue, or stale path. Compare startup entries and application settings before reinstalling Windows.

What is the correct order for most users?

Use this order:

1. Identify the executable and exact error.
2. Install or repair the correct Visual C++ 2008 x86 or x64 package.
3. Restart Windows.
4. Repair or verify the affected application.
5. Check antivirus quarantine.
6. Investigate side-by-side errors with Event Viewer and sxstrace.
7. Check startup entries if the message appears at sign-in.
8. Run DISM and SFC when broader Windows corruption is suspected.
9. Use System Restore after a recent system change.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.