If you see code 0xc000007b, you are being told that a binary you're attempting to use is either corrupt or not intended to be run in the process attempting to use it. That description is intended to be vague because this error code can cover a large number of situations. There are no one-size-fits-all solutions to this problem but this guide should help to track down the root cause of this issue. The root cause could vary from user to user and a case-by-case solution will be needed.
Why am I seeing this code?
Often, this error code is caused by a 64-bit process trying to use a 32-bit dll or vice versa. In this case, the 64-bit launcher is probably trying to load a .dll that it wasn't meant to run with. The problem is that this isn't the only situation that could cause this error code. It could be a subtle problem with any of the binaries used/referenced. All the ways users can get into this state are not presently clear, but usually it has to do with dependencies that are corrupt, modified, incorrectly installed, or that have been tampered with.
Included below are steps for using two different tools, Dependency Walker and Procmon for troubleshooting the cause of this error code. Please follow the steps to generate logs from both Procmon and Dependency Walker.
Using Dependency Walker
To generate logs for the Epic Games launcher using Dependency Walker, do the following.
- Download Dependency Walker 2.2 x64 from here.
- Extract depends22_x64.zip to C:\DWalker
- Open a command window as administrator (Start Menu -> type “cmd” in the search box and right click on cmd.exe and select Run as Administrator)
- Enter the following command to switch to the folder we extracted Dependency Walker to:
- cd C:\DWalker
- Enter the following command to have the tool generate logs while running Epic Games launcher:
- depends.exe /c /f:1 /pb /pp:1 /pg:1 /ot:Log.txt "c:\Program Files\Epic Games\Launcher\Engine\Binaries\Win64\EpicGamesLauncher.exe"
- Note: this step assumes that you have installed the launcher in the default location. If you have installed it elsewhere, you may need to update the file path accordingly.
- This will run the Epic Games launcher and you'll see the familiar 0xc000007b error message. Click OK to dismiss it as usual.
- You should now have a Log.txt file in the C:\DWalker folder. The next section will go over what to look for in this log to pinpoint the problem module.
Troubleshooting the problem with Procmon
Sometimes, we won't be able to determine the source of the issue using Dependency Walker. Procmon is another tool that can be used to discover the cause. To generate a Procmon log, complete the following steps:
- Download Procmon here.
- Open the zip file you download and move the Procmon.exe to somewhere on your machine.
- Right click on that executable and select Run as administrator.
- When the application launches go to the menu bar at the top and select Filter then select Filter... from the menu that pops up.
- In the window that opens select the top left drop-down and change it to Process Name
- Change the drop-down directly to the left of that one to is.
- In the text box to the right of that enter EpicGamesLauncher.exe
- Click the Add button.
- Click OK.
- Run the launcher.
You should see the window in Procmon start to fill up. Once you have seen the error window show up from the launcher, dismiss the dialog and go back to Procmon and follow these steps:
- Go to the top left menu and select File, then Save...
- A Save To File dialog will appear. The default settings should be correct. They should be Events displayed using current filter and a format of native process monitor format.
- Check the file location and press Ok.