Application Was Unable to Start Correctly (0xc000007b)
What you are seeing
Windows often titles the window Application Error. The body looks like:
The application was unable to start correctly (0xc000007b). Click OK to close the application.
That code is STATUS_INVALID_IMAGE_FORMAT (“Bad Image”): the loader rejected an executable or DLL as the wrong format for this process—most often a 32/64-bit mismatch. Details and tools are documented in Microsoft’s DSVC guide on C000007B.
Startup failure (not a crash mid-run)
This page is for failures at launch / load time: you click the shortcut or launcher and the dialog appears before the main UI opens. If the program already ran for a while and then crashed, do not force-fit this page—treat it as a normal crash path instead.
Event Viewer clue (do not “fix” ntdll)
In Event Viewer → Windows Logs → Application, a matching failure often shows Exception code: 0xc000007b and Faulting module name: ntdll.dll. That does not mean you should replace ntdll.dll. The log usually does not name the real bad dependency; ntdll is where the failure was reported.
Where to go next (home tree only)
Do not download loose DLLs. Follow the home diagnosis order:
- Confirm the symptom
- Suspected 32/64 mix-up → bitness step or 32-bit redistributable missing
- Suspected Visual C++ / msvcp / vcruntime issue → runtime step or msvcp140 dll was not found
- System files (only if still failing)
- Still failing
- Opened from a game/launcher → from-game entry
Advanced users who need to pinpoint a rejected image can use Process Monitor (see still failing)—this page does not teach a full debugger workflow.
FAQ
When should I stay on this page?
Only if the dialog shows 0xc000007b (or C000007B). The same “unable to start correctly” wording can appear with other codes—if yours does not include this code, leave this page.
Is this a crash mid-run?
No—this page is for launch / load time failures. If the program already ran and then crashed, treat it as a normal crash path instead.
Event Viewer shows ntdll.dll—should I repair it?
No. Do not replace ntdll.dll. The log usually does not name the real bad dependency.
What next?
Do not download loose DLLs. Follow the home diagnosis order starting at symptoms, then bitness and runtime.