msvcp90.dll Is Missing: Safe Fixes for Windows 11 and 10

msvcp90.dll is a Microsoft Visual C++ runtime file, and an application that cannot find it will often stop before its window opens. The safest fix for an msvcp90.dll error is to identify the program named in the message and install or repair the matching Microsoft Visual C++ 2008 Redistributable, using x86 for a 32-bit program and x64 for a 64-bit program.

Do not download an isolated copy of msvcp90.dll from a random DLL website. That file may contain malware, belong to the wrong Visual C++ generation, use the wrong architecture, or fail to fix the application’s manifest and related runtime files.

As an Amazon Associate I earn from qualifying purchases.

Fix 1: Install the official Visual C++ 2008 runtime

Time needed: 10 to 20 minutes

msvcp90.dll belongs to Visual C++ 9.0, also known as Visual Studio 2008. It is normally installed by the Microsoft Visual C++ 2008 Redistributable or bundled with the application that needs it.

The official Microsoft package is named Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update. Microsoft provides separate installers named vcredist_x86.exe, vcredist_x64.exe, and vcredist_ia64.exe on its official Download Center page.

Choose x86 or x64

The correct package depends on the application, not simply on the version of Windows installed on your computer.

• A 32-bit application needs vcredist_x86.exe.
• A 64-bit application needs vcredist_x64.exe.
• A 64-bit version of Windows can run 32-bit software, so it may still need the x86 package.
• If you use several older programs and do not know their architectures, installing both the x86 and x64 packages is reasonable.

The x86 and x64 runtimes are separate. A 64-bit Windows installation does not make the x64 runtime suitable for every program. Microsoft explains these architecture rules in its Visual C++ DLL redistribution guidance.

The IA-64 installer is for Itanium-based systems, not ordinary Intel or AMD desktop PCs.

Download and install the runtime

1. Open Microsoft’s Visual C++ 2008 SP1 Redistributable download page.
2. Select the download button.
3. Choose vcredist_x86.exe if the failing program is 32-bit.
4. Choose vcredist_x64.exe if the failing program is 64-bit.
5. If you are unsure and use several older programs, download both appropriate packages.
6. Open the downloaded installer from your Downloads folder.
7. Approve the Windows permission prompt.
8. Accept the license terms and complete the installation.
9. Restart Windows.
10. Launch the program that displayed the error.

If the installer reports that the runtime is already installed, look for a Repair option. If no repair option appears, uninstalling and reinstalling only the affected Visual C++ 2008 entry can help, but do not remove unrelated Visual C++ packages.

Visual C++ 2008 is a separate legacy runtime family. Installing the newer Visual C++ 2015–2022 or current supported package does not generally replace msvcp90.dll; newer packages provide files such as msvcp140.dll. Microsoft lists the older runtime families separately on its supported Visual C++ downloads page.

Check the installed runtime

To check whether the package is present:

1. Press Windows + R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Look for entries containing Microsoft Visual C++ 2008 Redistributable.
5. Check whether the x86 or x64 package matches the program that fails.
6. If both are installed, leave both in place unless you have a specific reason to repair one.

Do not remove every Visual C++ Redistributable entry. Applications can require several generations side by side.

How to identify the application’s architecture

The error dialog usually names the executable or application that failed. If the program offers only a 32-bit build, use x86. Other clues include:

• A program installed under C:\Program Files (x86) is commonly 32-bit.
• A program installed under C:\Program Files may be 64-bit, although the folder alone is not conclusive.
• In Task Manager, some 32-bit processes are marked with a suffix such as (32 bit).
• The software vendor’s system requirements may identify whether the program is 32-bit or 64-bit.

If the program is a game, launcher, plugin host, or older utility, installing both x86 and x64 Visual C++ 2008 packages is often the simplest way to cover separate components.

Fix 2: Repair or reinstall the affected application

Time needed: 10 to 30 minutes

If only one program reports the error, its own installation may be incomplete. This can happen after an interrupted update, failed uninstall, disk cleanup, modification, or security-software quarantine.

First try the application’s built-in repair option.

Repair an app through Windows Settings

On Windows 11:

1. Open Start.
2. Select Settings.
3. Open Apps.
4. Select Installed apps.
5. Find the affected application.
6. Select the three-dot menu beside it.
7. Choose Advanced options if available.
8. Select Repair.
9. Test the application.

On Windows 10, open Settings → Apps → Apps & features, select the program, choose Advanced options, and select Repair when available.

You can also use the traditional repair path:

1. Press Windows + R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Select the affected application.
5. Choose Repair, Change, or Modify.
6. Follow the installer’s instructions.
7. Restart Windows and test the program.

Not every installer supports Windows repair controls. If no repair option exists, reinstall the application from its original vendor, launcher, disc, or trusted installation media.

Reinstall a game

For a game installed through a launcher, use the launcher’s file-repair or verification feature before downloading loose DLL files.

For Steam:

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

If the game folder contains a redist, prerequisites, support, or similar folder, run the Visual C++ installer supplied there. The game’s own installer may contain the exact runtime version and manifest it expects.

If reinstalling the application fixes the error, the missing file was probably part of that application’s installation or its private runtime deployment. Keep the Microsoft redistributable installed as well if the application requires it.

Fix 3: Check whether the error identifies the real failing program

Time needed: 5 to 15 minutes

Read the error dialog carefully. It may name a program, plugin, launcher, updater, or helper process rather than the application you were trying to open.

For example, a game launcher may start a separate executable. A photo application may load an older plugin. A hardware utility may launch a control-panel component. The executable named in the message is the best starting point.

Record:

• The application name.
• The full executable name, if shown.
• Whether the error appeared during installation, startup, or while opening a file.
• Whether the problem affects one program or several.
• Whether the issue began after an update, cleanup, antivirus alert, or hardware change.

If only one plugin fails, repair the host application or reinstall that plugin. If multiple unrelated programs fail, continue to the Windows component checks later in this guide.

Fix 4: Understand where msvcp90.dll may be installed

Time needed: 5 to 15 minutes

msvcp90.dll does not have to appear as a loose file in C:\Windows\System32.

Visual C++ 2008 commonly uses the Windows side-by-side store under the WinSxS\Fusion area. An application can also use a private copy beside its executable. Microsoft documents both central runtime installation and application-local deployment in its Visual C++ deployment guidance and runtime version auditing documentation.

That means finding a file somewhere on the disk does not prove that the failing application can load it. The file may be:

• The wrong architecture.
• The wrong Visual C++ version.
• Corrupted.
• In an application directory Windows is not searching.
• Missing a required manifest.
• A private copy that conflicts with another bundled runtime file.
• Present but unavailable because security software removed a related dependency.

Do not copy a file into System32, SysWOW64, or WinSxS manually. Windows uses servicing and side-by-side rules for these locations, and manual changes can create additional problems.

The debug counterpart is named msvcp90d.dll. It is intended for developers and debug builds. It is not a replacement for the normal msvcp90.dll used by a released application.

Fix 5: Identify the exact error variant

Time needed: 10 to 30 minutes

Different messages point to different causes. Use the wording of the error to choose the next step.

“MSVCP90.dll is missing from your computer”

This normally means the application cannot obtain the Visual C++ 2008 runtime it needs.

Do the following in order:

1. Install the correct Microsoft Visual C++ 2008 package.
2. Install x86 if the application is 32-bit.
3. Install x64 if the application is 64-bit.
4. Repair or reinstall the application.
5. Check the application’s bundled prerequisite installer.
6. Check antivirus Protection history if the problem began after a security alert.

“The dynamic link library MSVCP90.dll was not found in the specified path”

This can indicate that a plugin or application was launched from an incomplete directory, removable drive, network location, or damaged installation.

Repair the application first. If the program uses plugins, reinstall the plugin and check whether the plugin folder contains its own runtime files. Do not solve this by copying a random DLL into the folder.

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

This is not necessarily a simple missing-file problem. It usually indicates that the application’s manifest requests a Visual C++ side-by-side assembly that Windows cannot load.

Use Event Viewer:

1. Press Windows.
2. Type Event Viewer.
3. Open it.
4. Expand Windows Logs.
5. Select Application.
6. Look for an event from SideBySide created when the program failed.
7. Check the event details for the requested architecture and assembly version.

Event ID 33 is commonly useful for this type of investigation. Record the exact requested VC90 version rather than guessing.

You can also use Microsoft’s built-in sxstrace tool. Open Terminal, Command Prompt, or PowerShell as administrator and run:

sxstrace trace -logfile:sxstrace.etl

Now reproduce the application failure. Stop tracing with:

sxstrace stoptrace

Then create a readable report:

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

Open the resulting sxstrace.txt file and look for the assembly name, architecture, and version. Microsoft documents this process in the sxstrace command reference.

Some older programs request a specific non-SP1 VC90 assembly, such as version 9.0.21022.8. A current VC++ 2008 SP1 installation may not satisfy that exact manifest request. In that case, obtain the prerequisite from the original application installer or its vendor. Do not download an arbitrary older DLL.

“The procedure entry point could not be located”

This usually means the application loaded an incompatible or wrong-version copy of the runtime. The file exists, but it does not export the function the program expects.

Repair or reinstall the affected application and the official VC++ 2008 runtime. If the application has a private runtime folder, do not replace one file while leaving related files such as MSVCR90.dll, msvcm90.dll, and the manifest untouched.

“MSVCP90.dll is either not designed to run on Windows or contains an error”

This is a Bad Image-style error. It can indicate corruption, the wrong architecture, an incompatible private copy, or a damaged dependency.

Install or repair the matching Visual C++ package, then repair the application. If the error refers to a path under WinSxS, avoid deleting or replacing files there manually. Continue with the application repair and Windows component checks below.

Fix 6: Check whether antivirus quarantined the runtime

Time needed: 5 to 15 minutes

Antivirus quarantine is a possible cause when the problem begins immediately after an alert, scan, update, or application installation. It does not prove that the removed file was safe or malicious.

In Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Choose Protection history.
6. Inspect entries created when the application stopped working.
7. Check the original file path and detection details.

If the item came from a trusted Microsoft installer or a trusted application installer, reinstalling that package is safer than restoring an isolated file. If you restore a quarantined file, Windows Defender may detect it again. Microsoft explains this risk in its Protection History guidance and quarantined-file restoration documentation.

Do not create a permanent antivirus exclusion for a DLL downloaded from an unknown source. If the original path is inside a temporary download folder, an unknown crack, or an unofficial program bundle, leave the file quarantined and obtain the application again from its legitimate source.

Fix 7: Install Windows updates

Time needed: 10 to 30 minutes, plus download time

Windows Update is not a replacement for the Visual C++ 2008 runtime, but it can repair servicing infrastructure and component-store problems that interfere with installers.

On Windows 11:

1. Open Start → Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart when prompted.
6. Check again after restarting.

On Windows 10:

1. Open Start → Settings.
2. Select Update & Security.
3. Select Windows Update.
4. Choose Check for updates.
5. Install available updates.
6. Restart Windows.

Microsoft provides the current steps in its Windows Update instructions.

After updating, reinstall or repair the Visual C++ 2008 package and test the application again. Do not expect Windows Update alone to install every legacy application runtime.

Fix 8: Repair Windows components with DISM and SFC

Time needed: 15 to 45 minutes

Use DISM and SFC when:

• Several unrelated applications fail.
• Windows has other corruption symptoms.
• The Visual C++ installer reports component-store errors.
• Windows Update is failing.
• System files appear damaged.

They are not the first fix for one application that simply lacks an application runtime. msvcp90.dll is an application dependency and may never have been part of the protected Windows image, so SFC may not restore it.

Microsoft recommends running DISM before SFC.

1. Open Start.
2. Type Terminal or Command Prompt.
3. Right-click the result.
4. Select Run as administrator.
5. Approve the permission prompt.
6. Run this command:

DISM /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish.
2. Restart Windows if requested.
3. Open an elevated terminal again.
4. Run:

sfc /scannow

1. Wait until the scan reaches 100 percent.
2. Restart Windows.
3. Repair or reinstall the Visual C++ 2008 runtime.
4. Test the affected program.

If DISM reports that it cannot repair the component store, resolve Windows Update or servicing problems first. If SFC reports that it found and repaired damaged files, restart and test again. If SFC reports that it could not repair everything, review the result and continue with application repair rather than repeatedly running the same scan.

Microsoft documents this sequence in its System File Checker and DISM instructions.

If manually hunting through Windows components and repeating DISM and SFC does not show what changed, Outbyte PC Repair can perform a free scan that identifies reported problems; repairs are completed by the full version, and it is not required when reinstalling the affected game or application is the definitive fix.

Fix 9: Do not use regsvr32 for msvcp90.dll

Time needed: 2 minutes

regsvr32 is for DLLs that provide registration entry points such as DllRegisterServer, commonly used by some COM or ActiveX components. msvcp90.dll is a C++ runtime library loaded as a code dependency, not a COM component that needs registration.

Running:

regsvr32 msvcp90.dll

will not repair the Visual C++ runtime. It may produce an error stating that the module was loaded but the DllRegisterServer entry point was not found.

Use the official Visual C++ installer instead. Microsoft explains DLL registration requirements in its registration documentation.

Fix 10: Check Windows Features only for a separate dependency

Time needed: 5 minutes

Turning Windows Features on or off does not install msvcp90.dll. Do not enable random features as a substitute for the Visual C++ 2008 Redistributable.

You can still check whether the application has separately reported a .NET or legacy component requirement:

1. Open Start.
2. Type Turn Windows features on or off.
3. Open the matching Control Panel result.
4. Review the feature list.
5. Change a feature only when the application’s documentation specifically requires it.
6. Restart if Windows requests it.

The Visual C++ runtime and optional Windows Features are different components. Enabling .NET Framework features will not normally solve an msvcp90.dll error.

Fix 11: Update drivers only when the failing program belongs to hardware software

Time needed: 10 to 30 minutes

Driver reinstallation is a low-priority fix for this file because msvcp90.dll is a C++ runtime library, not a driver component.

Consider a driver-related repair only when the failing executable belongs to:

• A printer or scanner utility.
• A graphics control panel.
• A motherboard or chipset utility.
• A hardware monitoring application.
• A vendor control center installed with a device.

Use 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 and driver date.
8. Select Update Driver.
9. Choose Search automatically for drivers.
10. Restart Windows if a driver is installed.
11. If the hardware utility itself is damaged, reinstall the utility from the hardware manufacturer’s official installer.

Do not uninstall graphics, chipset, printer, or storage drivers merely because an unrelated older program reports msvcp90.dll.

When several devices have stale drivers, manually checking each category can mean guessing which of many entries matters. Outbyte Driver Updater provides a free scan showing reported driver problems, while driver installation is handled by the full version; it is optional and does not replace reinstalling the specific game or application that owns the failing executable.

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

Fix 12: Investigate a private DLL with Microsoft Process Explorer

Time needed: 15 to 30 minutes

If the official runtime is installed but the error remains, the application may be loading a private copy beside its executable.

Microsoft’s Process Explorer can display the DLLs loaded by a running process. Download it from the official Process Explorer page.

The difficulty is that a program displaying the error may exit immediately. If it stays open long enough:

1. Start Process Explorer as administrator.
2. Launch the affected application.
3. Find its process in the list.
4. Select the process.
5. Open the process properties.
6. Review the loaded DLL list.
7. Look for msvcp90.dll, MSVCR90.dll, msvcm90.dll, and related runtime files.
8. Note the full path of the loaded files.
9. Compare that path with the application’s installation directory and the Windows runtime locations.

If a private DLL is wrong or damaged, repair or reinstall the application. Do not overwrite it with a copy from another program or from an unofficial website.

Fix 13: Use System Restore only after a clear recent change

Time needed: 20 to 45 minutes

System Restore is appropriate when the failure clearly began after:

• An application installation.
• A driver or Windows update.
• A cleanup operation.
• A security action.
• A system configuration change.

It is not the first choice for a long-standing missing runtime. It also does not replace personal documents, but it rolls back monitored system files, installed programs, drivers, and settings.

To check for a restore point:

1. Open Start.
2. Type Create a restore point.
3. Open the result.
4. Select System Restore.
5. Review the available restore points.
6. Choose one created before the failure began.
7. Review the affected programs.
8. Start the restore only when the date and consequences are acceptable.
9. Let Windows restart and complete the process.

Microsoft describes this recovery option in its Windows recovery guidance.

After the restore, install the official Visual C++ 2008 package again if necessary.

Why the error happens

The most useful troubleshooting order is based on the application and the wording of the message.

Likely cause	What it means	Best response
Missing or damaged VC++ runtime	The program cannot load its C++ Standard Library dependency	Install or repair the official VC++ 2008 package
Wrong architecture	A 32-bit program was given only x64, or a 64-bit program needs x64	Install the matching x86 or x64 package
Incomplete application installation	The program or plugin lost files or prerequisites	Repair, reinstall, or verify the application
Exact side-by-side requirement	The manifest requests a particular VC90 assembly	Check Event Viewer and sxstrace, then contact the application vendor
Wrong private DLL	The program loads an incompatible copy beside its executable	Repair the application and inspect the loaded path
Antivirus quarantine	A runtime or related dependency was removed	Check Protection history and reinstall from a trusted source
Windows component corruption	Servicing or system components are damaged	Run Windows Update, DISM, and SFC when symptoms are broader
Driver utility problem	A hardware control application is damaged	Repair that utility and update its related driver
User-profile problem	Only one Windows account is affected	Check permissions, shortcuts, per-user data, and startup entries

There is no single universal repair for every message. The application named in the error determines whether the problem is a central runtime, a private application copy, a manifest, or another dependency.

What not to do

Avoid these common but unreliable repairs:

• Do not download msvcp90.dll from a DLL archive website.
• Do not replace files in System32, SysWOW64, or WinSxS.
• Do not install only the newest Visual C++ package and assume it includes every older runtime.
• Do not delete Visual C++ Redistributables because several versions are installed.
• Do not run regsvr32 on the runtime DLL.
• Do not delete the WinSxS folder or use a registry cleaner.
• Do not restore an antivirus quarantine item without checking its original path and source.
• Do not reinstall graphics or chipset drivers for an unrelated application error.
• Do not repeatedly run SFC when only one program lacks its own runtime dependency.

The safe sources are Microsoft’s Visual C++ 2008 download page, the Microsoft supported Visual C++ downloads table, and the original application’s trusted installer.

Frequently asked questions

Is msvcp90.dll a Windows system file?

It is a Microsoft runtime file, but it is not a core Windows API DLL in the same sense as the files required by the operating system itself. Applications built with Visual C++ 2008 depend on it.

It may be installed centrally under the Visual C++ side-by-side store or privately inside an application directory.

Which Visual C++ package installs msvcp90.dll?

The relevant family is the Microsoft Visual C++ 2008 Redistributable, commonly the SP1 package. Use vcredist_x86.exe for a 32-bit application and vcredist_x64.exe for a 64-bit application.

Does Visual C++ 2010 or 2015 replace Visual C++ 2008?

No. Visual C++ runtime generations are separate and can be installed side by side. A newer package does not generally provide msvcp90.dll.

Does 64-bit Windows need the x86 package?

Yes, when you run a 32-bit application. Windows architecture and application architecture are separate choices. Many 64-bit PCs need both x86 and x64 Visual C++ packages.

Why is the file not in System32?

Visual C++ 2008 commonly uses the WinSxS Fusion store, and applications can also use private deployment. The file does not need to appear as a plainly visible loose file in System32.

Can I copy msvcp90.dll from another computer?

That is unsafe as a general repair. The copy may have the wrong architecture, version, servicing state, manifest, or related runtime files. Use the official redistributable or the application’s own installer.

Is msvcp90.dll malware?

The filename itself belongs to a legitimate Microsoft runtime, but malware can use misleading filenames or replace legitimate files. Check the file’s path, digital signature, original installer, and antivirus history. Do not assume either that every alert is malware or that every quarantined file is safe.

Will SFC restore it?

Not necessarily. SFC repairs protected Windows system files. An application runtime may not be part of that protected image. Install or repair the Visual C++ package first, and use DISM and SFC when broader Windows corruption is present.

Do I need to register the DLL?

No. msvcp90.dll is not normally registered with regsvr32. It is loaded as a runtime dependency.

What if the official installer succeeds but the error remains?

Repair or reinstall the application, check its bundled prerequisites, inspect Event Viewer for SideBySide events, and use sxstrace. The application may require an exact older VC90 assembly or may be loading a damaged private copy.

What information should I provide when asking for help?

Include:

• The exact error text.
• The application or game name.
• The executable named in the dialog.
• Whether Windows is 32-bit or 64-bit.
• Whether the application is 32-bit or 64-bit, if known.
• Which Visual C++ 2008 packages are installed.
• Whether the issue affects one program or several.
• Whether it began after an update, reinstall, cleanup, or antivirus alert.
• Any SideBySide Event Viewer details.
• The requested assembly version from sxstrace, if available.

Do not include a random DLL download link as a proposed solution. The useful evidence is the failing application, its architecture, the exact error variant, and the runtime or manifest version it requests.

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.