Visual C++ Runtime Errors in Games: Missing DLLs, x86 and x64

Choose your symptom

• MSVCP140.dll or VCRUNTIME140.dll is missing — Check the v14 family and the app’s architecture.
• MSVCP120.dll, MSVCP110.dll or MSVCP100.dll is missing — Check the corresponding older family, not just the newest v14.
• Only Runtime Error or 0xc000007b is shown — Collect prerequisites and the affected executable; do not guess a version.
• The Microsoft installer itself fails — Keep the setup code and logs for the matching failure branch.

STEP 1: Identify the message and the affected application

1. Capture the full error, DLL name such as MSVCP120.dll, code and executable being launched. If the message only says Runtime Error, check official prerequisites and logs before deciding it is a particular Visual C++ family.
2. Use the game’s official support to confirm its architecture and required runtime. A 32-bit game needs x86 even on 64-bit Windows. For a launcher, mod or plug-in error, check that component’s provider rather than assuming it matches the game executable.

Result and next action: Continue with the required family and architecture confirmed, or record them as unknown and ask the publisher. Do not choose x64 solely from the Windows edition.

STEP 2: Check the matching installed package

1. Press Win+R, enter appwiz.cpl and inspect Microsoft Visual C++ Redistributable entries in Programs and Features. Record the year or 14.x family and the x86/x64 suffix separately. Windows 11 Installed apps can also show their names.
2. Example: a confirmed 32-bit game needs MSVCP120.dll, but only 2013 (x64) appears. Check for the 2013 (x86) prerequisite; do not delete x64 or newer v14 entries. This list alone does not establish the state of DLLs bundled inside a game.

Result and next action: Match both family and architecture. Leave unrelated versions installed, then choose repair or installation for the identified prerequisite.

STEP 3: Repair or install the identified Microsoft package

1. Open Microsoft’s distribution page in Sources and choose the family and architecture confirmed for the affected app. A game needing 2013 or earlier has a separate prerequisite; the latest v14 is not a replacement for every older family.
2. If the matching package is installed, select it in Programs and Features and use Change → Repair where offered. If absent, use the official Microsoft installer. If Change or Repair is unavailable, check that same official package’s installer options rather than uninstalling all versions.

Result and next action: Record the package name and setup result. If installation fails, preserve the error and use the failure section below before retrying.

STEP 4: Repeat the original launch and follow the result

1. Restart and launch the same executable in the same way. If the missing-DLL message disappears, check that the game reaches its title screen. If another name appears, record it and confirm its own prerequisite.
2. If setup failed, retain its error and logs. If setup succeeded but the same game error remains, recheck architecture, game files and any mod or plug-in involved. For Steam, verify files; otherwise give official support the full error and relevant installed-package list.

Result and next action: Keep a changed error separate from a solved launch. Stop adding unrelated redistributables when the evidence points to the same unresolved component.

Match the DLL family before selecting a download

1. VCRUNTIME140.dll, VCRUNTIME140_1.dll or MSVCP140.dll: check the v14 family. MSVCP120.dll or MSVCR120.dll: check 2013. MSVCP110.dll or MSVCR110.dll: check 2012 Update 4. MSVCP100.dll or MSVCR100.dll: check 2010 SP1. Confirm the publisher’s requirements and architecture for each candidate.
2. The older families have separate sections on Microsoft’s page and can coexist. Their continued availability does not mean they are currently supported. If a download requires sign-in or is unavailable, use the publisher’s guidance; do not substitute a third-party DLL archive.
3. ucrtbase.dll or api-ms-win-*.dll can involve Windows Universal CRT components. Check Windows Update and the publisher’s prerequisites. A generic Runtime Error or 0xc000007b alone does not select a year or architecture.

Match the app, not the Windows label

1. Find the architecture of the executable that fails. A 32-bit game on 64-bit Windows still needs its x86 prerequisite. A separate launcher or plug-in can have different requirements.
2. If the target is unknown, inspect the publisher’s prerequisite instructions or ask support. x86 and x64 packages can coexist on 64-bit Windows, but their presence is not a reason to install every family blindly.

Read installed-package names carefully

1. In Programs and Features, record the relevant family, full version and architecture before using Change or Repair. Do not remove other years merely because they look old.
2. If the name is absent, recheck the family and architecture against the publisher’s requirement. If the game includes a private runtime, the Windows list alone cannot verify or repair those bundled files.

If repair or installation fails

1. No matching entry or no Repair option: recheck the required family and architecture, then inspect the matching Microsoft installer’s available operation.
2. A newer version is already installed: record the installed version in the same family and architecture. Check its repair option or Microsoft’s current package instead of repeatedly running an older installer.
3. Invalid installer package, code 1620: record the package and download source. Obtain a fresh copy of the matching official package rather than reusing a damaged file.
4. Generic failure, code 1603: preserve the setup message and logs. Check Windows Update and restart before a controlled retry. The code alone does not identify one cause.
5. Access denied, code 5, or file in use, code 32: save work, close running apps and restart. On a PC you administer, the verified Microsoft installer may require Run as administrator; on a managed PC, ask its administrator. Keep security protection enabled.
6. An older version cannot be removed, code 1714: identify the exact old package in the log and follow Microsoft’s guidance for that package or ask support. Do not bulk-delete redistributables or Windows Installer storage folders.
7. Setup succeeds but the game still fails: recheck the failing executable, architecture and complete DLL name. Compare verified game files and the documented mod configuration before asking game support.

Five details to give support

1. Keep the game and launch method; complete error and DLL name; affected executable’s architecture (or unknown); matching installed family/version/architecture; and repair or installation result with its error code. Review personal details before sharing screenshots or logs.

Protect saves and keep changes reversible

• Do not bulk-uninstall older Visual C++ entries; other software may require them.
• Do not copy unofficial DLL downloads into the game folder or Windows directories, and do not disable protection to force setup through.