0xc000007b.com

Windows startup error

0xc000007b

A Windows app shows this code? Confirm the dialog, match the app’s 32-bit or 64-bit architecture, then repair the official Visual C++ Redistributable if needed.

Start hereThree checks · official Microsoft links · no DLL downloads

Choose your starting point

What matches your screen?

1 minute
01I see the 0xc000007b dialogConfirm the exact code, then check the app architecture.02A game or fresh install failsUse the launcher repair path before changing Windows files.03Windows names msvcp140.dllOpen the focused Visual C++ runtime guide.

1. Symptoms

0xC000007B is the NTSTATUS STATUS_INVALID_IMAGE_FORMAT. A common dialog is “The application was unable to start correctly (0xc000007b).” The same English sentence can appear with a different code — this site only covers dialogs that show 0xc000007b / C000007B. Some searches shorten the code to 0xc00007b; the standard status covered here is 0xc000007b.

Three-step callout showing how to recognize the Windows Application Error message and confirm code 0xc000007b
First confirm the message, then confirm the exact 0xc000007b code.

Matching dialog page: the application was unable to start correctly 0xc000007b. Background: Diagnosing STATUS_INVALID_IMAGE_FORMAT (C000007B) · NTSTATUS 0xC000007B.

Only one program fails, or every program?

Use the scope of the failure as a triage clue. If one app or game fails while unrelated apps open, start with that app’s clean reinstall, launcher repair, and vendor prerequisites before repeatedly repairing Windows. If several unrelated programs fail, or Windows components also report bad-image errors, continue to system-file checks after the architecture and runtime steps.

2. Check 32-bit vs 64-bit

Most 0xc000007b failures are an architecture mismatch — for example a 64-bit process loading a 32-bit DLL, or a 64-bit EXE on 32-bit Windows. Event Viewer often shows Faulting module ntdll.dll and Exception code 0xc000007b; that does not mean you should repair or replace ntdll.dll, and it usually does not name the bad dependency.

  1. Confirm whether the failing app is 32-bit or 64-bit (Task Manager → Details → Architecture, or the vendor’s install notes).
  2. Make sure any DLLs next to the EXE match that architecture — remove loose copies you pasted from a “DLL pack”.
  3. Continue with the matching Visual C++ Redistributable in step 3.
Three-step guide showing Ctrl Shift Esc, Task Manager Details, and the Architecture column with 32-bit and 64-bit values
Open Task Manager, click Details, then read the Architecture column.

Deep dive: 0xc000007b 32-bit redistributable missing.

3. Install the Visual C++ Redistributable

If Windows reports msvcp140.dll / vcruntime140.dll “was not found”, or you suspect the wrong-architecture runtime is installed: undo any manual DLL copies first, then install or repair the matching v14 Visual C++ Redistributable from Microsoft Learn (X86 and/or X64, based on the app — not on “Windows is 64-bit so I only need x64”).

Named “was not found” messages are a related DLL-missing family (often discussed with STATUS_DLL_NOT_FOUND / 0xC0000135). They are not the same code as 0xC000007B. If your main symptom is the 007b dialog, stay on this diagnosis tree; use the dedicated runtime page when Windows names those DLLs.

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.

Three-step guide showing Microsoft Learn, matching X86 or X64 to the app, and downloading or repairing Visual C++ Redistributable
Use Microsoft Learn, match X86 or X64 to the app, then download or repair.

Named-DLL page: msvcp140 dll was not found. Side-by-side text is different — see side by side configuration is incorrect.

4. System files (if still failing)

Only after bitness and the official redistributable: if you still fail and you suspect Windows protected files are damaged, run DISM, then SFC, from an elevated Command Prompt. If the real problem is a wrong-architecture DLL inside the app folder, SFC often will not fix it.

On Windows 10 or Windows 11, open Start, search for Command Prompt (or Windows Terminal), choose Run as administrator, and run the commands in this order. Let DISM finish before starting SFC. If either tool reports that it cannot repair the image or files, stop repeating the same commands and return to the app vendor or Windows repair options.

  1. Repair the Windows image first:
    DISM.exe /Online /Cleanup-Image /RestoreHealth
  2. Then scan system files:
    sfc /scannow
  3. If a specific file is truly corrupt, check disk health and replace it from a correct vendor source (reinstall the app or component that owns it) — never from a random DLL download site.

Repair a Windows image (DISM) · Use System File Checker · sfc command.

5. Still failing

Installed Visual C++ but 0xc000007b remains?

Do not keep reinstalling the same package blindly. Recheck the failing EXE’s architecture, remove any hand-copied DLL from the app folder, and test the clean vendor install again. If the matching X86/X64 runtime and a clean app install still fail, use the optional Process Monitor path below or contact the app vendor with the exact executable name and Windows version.

  1. Reinstall the app that fails to start.
  2. Check the app folder for DLLs someone replaced by hand; remove those copies and restore from a clean install.
  3. Advanced users can optionally use Process Monitor or Dependency Walker (same architecture as the EXE; watch the CPU column) to spot the failing image — see Microsoft’s C000007B diagnosis article and ProcMon start-failure guide. This page does not teach a full WinDbg session.
  4. If you still cannot locate the bad module, contact the application vendor (developers of Microsoft apps can open Microsoft support).

6. Came from a game or launcher

If a game or a newly installed app pops the 007b dialog first: confirm the code is 0xc000007b, undo any manual “DLL pack” drops in the game folder or system folders, then jump straight to bitness and runtime. This is an entry point into the same tree — not a separate game guide, and not a list of game titles.

Use the launcher’s repair path first

  1. Use the launcher’s built-in Verify or Repair files action for the affected game.
  2. If the launcher itself fails, use its official support or clean-reinstall instructions instead of downloading DLLs.
  3. Return to bitness and Visual C++ when the launcher repair does not resolve 0xc000007b.

When a game names a legacy DirectX DLL

If the dialog explicitly names files such as d3dx9_43.dll, xinput1_3.dll, or xaudio2_7.dll, that is a separate legacy DirectX dependency path. Use Microsoft’s DirectX End-User Runtime and never download an individual DLL. If the dialog shows the exact 0xc000007b code, stay on this page’s architecture-first diagnosis tree.

FAQ

What does 0xc000007b mean?

0xC000007B is NTSTATUS STATUS_INVALID_IMAGE_FORMAT (“Bad Image”). Most cases are an architecture mismatch, not a random broken file.

Should I check bitness or the Visual C++ Redistributable first?

Check 32-bit vs 64-bit first, then the official Visual C++ Redistributable. Do not treat them as optional picks.

Is “msvcp140.dll was not found” the same as 0xc000007b?

No. Named “was not found” messages are a related missing-DLL path, not the same code as 0xC000007B. See msvcp140 dll was not found when Windows names those DLLs.

Where should I get the Visual C++ Redistributable?

Only from Microsoft Learn (button in step 3). This site does not host DLL files.