Use the “Windbg” software to run the exe file in debug mode. It is a gui based debugger and shows what steps are being executed. This will help you to figure out what dll files are causing the problem or which step is actually creating the error. You can find the app in the app store as well.
I also faced the same problem when I had visual studio 2017 installed. But it was solved when uninstall the 2017 version and installed the 2015 visual studio. Also note that you need microsoft viual c++ 2015 redistributable (both x64 and x86 versions) installed. There might be a problem in installation if you have microsoft viual c++ 2017 redistributable then all you need to do is to uninstall the 2017 version and try again.
The 0xc000007b error may also arise if you don’t have the necessary dll files. You can search the internet to get those dll files. I used the link given in the following video: https://www.youtube.com/watch?v=1PbnHBkED4s
If all of this does not help then you can try to 32 version using the method that I mentioned earlier.
Looking through your log, it appears you may need to re-install one of the VS C++ Redistributable packages. I would start with the 2015 Redistributable, which you can find here:
So I uninstalled the 2015 packages and re-installed them, I didn’t have the 64 2015 previously. Tried to run the launcher, same error. Uninstalled / reinstalled, same error.
I uninstalled / reinstalled the 2017 packages, same error, and then uninstalled / reinstalled same error.
So i downloaded the DLL’s that were provided on the link and copied / pasted em, same error. However this time it first tried to install an Update for the launcher.
So then I uninstalled and reinstalled again. This time it added a Win64 Folder, but when I try the EpicGamesLauncher.exe in both directories, it’ll still do the same error. Even the CrashReportClient.exe, it won’t launch because of that error.
I feel like it’s getting closer because of adding the Win64 folder, but still getting the same issue unfortunately.
I also went through the same ordeal. Try the “WinDBG” method now with the 64 bit exe file and enter “g” in the input when the output of the WinDBG halts.