Quick answer
Reinstall the Visual C++ Redistributables and DirectX End-User Runtime, then reboot. If the error persists, check if you're running a 32-bit game on a 64-bit OS or vice versa.
What's actually happening here
Error 0xc000007b is Windows' way of saying "this program can't run because a required DLL is either missing, corrupt, or the wrong bitness." It's not a single root cause. It's a pile of possibilities, and the fix is a process of elimination.
The most common trigger I see: you install a game from Steam or GOG, it pulls in a DirectX or Visual C++ runtime that's older or broken, and the game's executable tries to load a 32-bit DLL on a system where the matching 64-bit version is already registered. The loader chokes. This shows up as the 0xc000007b box right at launch, sometimes after a splash screen.
You'll also see this with .NET Framework apps, especially ones ported from 32-bit to 64-bit. I've fixed it on Windows 10 22H2 and Windows 11 23H2 the same way.
The main fix (do these in order)
- Install the Visual C++ Redistributables. Go to Microsoft's site and grab the latest
vc_redist.x86.exeandvc_redist.x64.exe. Run both, even if you think you have them. The 32-bit is essential because most games are still 32-bit, and the 64-bit is needed for system components. You don't need the old 2008–2013 ones unless a specific game asks for them. - Repair DirectX. Download the DirectX End-User Runtime Web Installer from Microsoft. It doesn't replace your modern DirectX 12—it adds legacy DLLs that older games rely on. Run it, let it finish, reboot.
- Do a clean boot. Press Win+R, type
msconfig, go to Services, check "Hide all Microsoft services", click "Disable all". Then go to Startup and turn off everything. Reboot. This rules out a third-party service or startup app that's messing with the game's DLL loading. - Run the system file checker. Open an elevated Command Prompt (right-click Start → "Terminal (Admin)") and run
sfc /scannow. This checks the Windows system files and repairs any corrupt ones. It takes a while but it's worth it.
What if the main fix fails
If you've done the above and still see the error, the problem is likely a specific missing DLL. Check the Windows Event Viewer (right-click Start → Event Viewer → Windows Logs → Application). Look for an Error event from the game's executable. The event details often name the exact DLL that failed to load. That's your clue.
Another angle: the game might be built for a different architecture than your OS. A 16-bit installer or a 32-bit game on a 64-bit system works fine, but a 64-bit game on a 32-bit system won't. Verify your OS is 64-bit (Settings → System → About) and the game's requirements match.
If it's a Steam game specifically, sometimes the local files get corrupted. Right-click the game in your library → Properties → Local Files → "Verify integrity of game files". This re-downloads whatever's broken.
And don't forget the classic: reboot after every step. Windows caches DLL paths, and a reboot forces it to re-evaluate.
Prevention (so this doesn't come back)
The root cause is usually a missing or stale runtime. Keep the Visual C++ and DirectX runtimes current. Windows Update handles most of this automatically, but the redistributables are separate installs—Microsoft doesn't roll them all into Windows Update.
Also, if you're using a game launcher like Steam or Epic, let it install its bundled runtimes. Don't skip those prompts. They're there because the game needs them.
Finally, if you're still stuck, look up the specific game plus "0xc000007b" on forums. Games with known engine quirks (Unity, Unreal) often have game-specific fixes—like disabling a particular graphics setting or editing an ini file.
That's the whole process. It fixes 90% of these in an hour, and the other 10% is a specific DLL you can track down with Event Viewer.