0xc000007b: Check 32-bit vs 64-bit Windows Apps

Install the Visual C++ package for the app’s architecture. A 64-bit PC can still need the X86 package.

Match the app, not only the OS

0xC000007B is NTSTATUS STATUS_INVALID_IMAGE_FORMAT (“Bad Image”): Windows rejected an executable or DLL as the wrong format for this process (MS-ERREF). The familiar dialog is often The application was unable to start correctly (0xc000007b).

Why a 64-bit PC still needs the x86 package

Microsoft’s diagnostics note that most of these failures are bitness / architecture mismatches—for example a 64-bit process loading a 32-bit DLL, or a 64-bit EXE on 32-bit Windows. Event logs may only show Faulting module name: ntdll.dll, which does not name the real bad dependency (DSVC guide on C000007B).

A classic Microsoft example: copying an x86 MFC DLL into a folder meant for an x64 build. The 64-bit app then fails with 0xc000007b. Fix the architecture— do not grab a random same-named DLL from the web.

Official deployment docs state that vc_redist.x86.exe installs the 32-bit libraries on both x86 and x64 computers, while vc_redist.x64.exe installs the 64-bit libraries for x64 machines (which DLLs to redistribute).

So if a 32-bit game or tool fails with 0xc000007b on 64-bit Windows, the missing piece is often the 32-bit (X86) Redistributable—even when X64 is already installed. That is why matching the package to the app matters.

Redistributable package architecture must match the app’s target architecture (latest supported Visual C++ redistributable).

Steps

  1. Confirm whether the failing app is 32-bit or 64-bit (Task Manager → Details → Architecture column, or the vendor’s install notes). On Windows 10/11 the column may say “32-bit” / “64-bit”.
  2. Open the official Microsoft Learn page below. Install or Repair the matching X86 and/or X64 package for that app. If you are unsure and you run mixed apps, installing both packages is a common, safe choice—not a hard rule.
  3. Restart Windows, then try the app again.
  4. Still failing? Return to the home tree: runtime, system files, or still failing (advanced Process Monitor / Dependency Walker notes live there—not in this main path). Came from a game launcher? See from-game.

Open the official Visual C++ Redistributable page on Microsoft Learn On that page, choose the X86 and/or X64 button that matches your app. We never host DLL files.

If Windows names a specific missing file such as msvcp140.dll or vcruntime140.dll, continue on msvcp140 dll was not found—same official install entry, focused on those DLL names. This page stays on architecture.

Related home step: #bitness · Dialog wording: the application was unable to start correctly 0xc000007b

Windows Task Manager Details view with callouts pointing to the Details tab and the Architecture column
Click Details, find the app, and read its Architecture value.

FAQ

Why does a 64-bit PC still need the x86 Redistributable?

vc_redist.x86.exe installs 32-bit libraries on x64 computers. A 32-bit app failing with 0xc000007b often needs the X86 package even when X64 is already installed.

Should I always install both x86 and x64?

Install what the failing app needs. Installing both is a common, safe choice when you run mixed apps—not a hard rule.

Where do I get the official packages?

Only from Microsoft Learn, linked from the steps: latest supported Visual C++ redistributable. Do not download loose DLLs or unofficial all-in-one packs.