Detailed analysis
0xc000007b is one of the most infuriating errors in Windows because it tells you absolutely nothing about what's actually wrong. "The application was unable to start correctly" — thanks, Windows. The fastest fix: install every Visual C++ Redistributable and DirectX runtime you can find, restart, and try again. If that doesn't work, read on for the targeted approach.
What's actually happening
Error 0xc000007b (STATUS_INVALID_IMAGE_FORMAT) means Windows tried to load a DLL that your game needs, but the DLL was either the wrong architecture (32-bit DLL loaded by a 64-bit game or vice versa), corrupted, or simply missing. Windows doesn't tell you WHICH DLL failed — it just throws this generic code and gives up.
The most common cause is a 32/64-bit mismatch. Your game is 64-bit and it's finding a 32-bit version of a runtime DLL (or the other way around). This happens when you've installed the x86 version of Visual C++ but not the x64, or when a game ships with a DLL that's the wrong architecture for your system.
The shotgun approach (fixes it 70% of the time)
If you just want to fix this and move on, do all of these in order. This carpet-bombs every possible missing dependency:
- Install ALL Visual C++ Redistributables. Every version from 2005 through 2022, BOTH x86 AND x64 for each. Yes, that's a lot of installers. Go to Microsoft's official download pages for each: 2005, 2008, 2010, 2012, 2013, and the combined 2015-2022 package. Install the x86 and x64 versions of every single one. This takes about 10 minutes but covers the most common cause.
- Install the DirectX End-User Runtime Web Installer. This is NOT the same as having DirectX 12 built into Windows. The End-User Runtime installs legacy DirectX DLLs (D3DX9, D3DX10, D3DX11, D3DCompiler, XInput, XAudio) that many games still depend on. Download it from Microsoft's website and run it.
- Enable .NET Framework 3.5 and 4.8. Open the Start Menu, search for "Turn Windows features on or off", and make sure both .NET Framework 3.5 (includes 2.0 and 3.0) and .NET Framework 4.8 Advanced Services are checked. Click OK and let Windows install them. Some games depend on .NET even if you wouldn't expect it.
- Restart your PC. Not optional. Several of these installers need a restart to register their DLLs properly.
- Try launching the game. If it works, you're done. If not, move to the targeted approach below.
The targeted approach (when the shotgun doesn't work)
If installing everything didn't fix it, you need to find the specific DLL that's failing. Windows won't tell you, but these tools will.
Use Dependencies (the modern Dependency Walker). Download Dependencies from GitHub (search "lucasg Dependencies" — it's the maintained replacement for the ancient Dependency Walker tool). Open the game's .exe file in Dependencies. It builds a tree of every DLL the game needs and highlights any that are missing or have errors in red. The red entries are your problem DLLs. Common culprits: msvcr110.dll (needs VC++ 2012), msvcp140.dll (needs VC++ 2015-2022), d3dcompiler_47.dll (needs DirectX runtime), xinput1_3.dll (needs DirectX End-User Runtime).
Use Process Monitor to catch the failure in real time. Download Process Monitor (ProcMon) from Microsoft's Sysinternals. Run it, set a filter for your game's process name, then launch the game. When it crashes, look for DLL load operations that returned NAME NOT FOUND or PATH NOT FOUND. That's the specific DLL causing 0xc000007b.
Check for 32/64-bit mismatches. Right-click the game's .exe > Properties > Details tab. Check the "Original filename" or just run Dependencies on it — it'll tell you if it's a 32-bit or 64-bit executable. Then check the DLLs in the game folder. If the game is 64-bit but a DLL in its folder is 32-bit (or vice versa), that DLL needs to be replaced. Verify game files through your launcher to get the correct version.
Common causes (in order of likelihood)
Missing Visual C++ Redistributables. By far the #1 cause. Most people only install the latest (2015-2022) but forget older games need older versions too. A game from 2014 might need the 2012 or 2013 runtime specifically.
Corrupted DLL in the game directory. Some games ship DLLs inside their own folder that override system versions. If one of those gets corrupted (bad download, disk error, modding gone wrong), you get 0xc000007b. Verify game files through Steam/Epic/GOG to replace them.
Antivirus quarantine. Norton, Avast, and Bitdefender love quarantining game DLLs. The file vanishes silently and you get 0xc000007b instead of a helpful "your antivirus ate your game" message. Check the quarantine and add your game folder to exclusions.
Corrupted Windows system files. If 0xc000007b happens across multiple different games and applications, your system DLLs might be damaged. Run 'sfc /scannow' in an admin Command Prompt. If it finds issues, run 'DISM /Online /Cleanup-Image /RestoreHealth' first, then sfc again.
Mods that replaced DLLs. If you installed ReShade, ENB, SpecialK, or other injection-based mods, they place modified DLLs in the game directory. Remove them and test with a clean install.
Is this a hardware problem?
No. 0xc000007b is always a software issue — missing, corrupted, or mismatched DLLs. You do not have a hardware problem. Don't let anyone convince you to buy new RAM or a new GPU because of this error.
The one exception: if your storage drive is failing, it can corrupt files silently, which causes 0xc000007b when the game tries to load a corrupted DLL. If you're getting this error across many different programs and your drive shows "Caution" in CrystalDiskInfo, that's your actual problem.
Games where this is most common
GTA V (especially the Rockstar Launcher version), The Witcher 3, Cyberpunk 2077, Elden Ring, older Assassin's Creed titles, Far Cry series, Dark Souls series, older Call of Duty games, FIFA/EA Sports FC, and heavily modded games like Skyrim and Fallout
4. Basically any game that's been around for a while and has accumulated dependencies across multiple Visual C++ versions.
Frequently asked questions
Q: I installed all the Visual C++ versions and it still doesn't work. Now what?
A: Use Dependencies or Process Monitor to identify the exact DLL that's failing. There might be a game-specific DLL that's corrupted in the game folder itself. Verify game files through your launcher, or fully uninstall and reinstall the game.
Q: Why does Windows give such a useless error message?
A: Because 0xc000007b is a low-level NT status code that fires before the application even starts running. At that point, Windows doesn't have enough context to give you a helpful message. It just knows "a DLL failed to load" but not which one or why.
Q: The game used to work fine. What changed?
A: Usually a Windows Update that corrupted a runtime, an antivirus that quarantined a DLL, or a game update that introduced a new dependency. Start with verifying game files and checking antivirus quarantine.
Q: Should I try running the game as Administrator?
A: It can help in rare cases where the game can't access DLLs in protected directories. Right-click the game exe > Run as Administrator. It won't fix missing DLLs, but it might fix permission-related DLL loading failures.