Game won't start after today's patch (0xc000007b)

I have the same issue. The play button was stuck in “Playing Now” state for a few seconds and then becomes clickable “Play” again. Have played Overwatch on this computer for years until yesterday.

Tried running other games too. I can run Starcraft but not Overwatch.

Windows 10 Pro, Ryzen 9 3900x, RTX 3060 Ti, 64GB RAM. No other big application was running.

1 Like

Does clearing the Bnet cache help? It sounds like part of the update is either missing or was corrupted during install. If the cache doesn’t work, maybe a reinstall?

Im having same issue with the error code [(0xc000007b)]. Anyone having luck fixing it yet?

1 Like

mine also wont work. Error 0xc000007b

I tried doing this, but it did not help

1 Like

I fixed the issue with yesterday`s (2024-10-29) patch by installing: “Visual Studio 2015, 2017, 2019 e 2022”. In my case, I downloaded the executable file “vc_redist.x64.exe”.

You can find it with a simple Google search. Make sure you are in Microsoft dot com domain.

I was getting the error message: “The application was unable to start correctly (0xc000007b)” but now is fixed.

NEVER put DLL files you download on the Internet in you System32 folder. NEVER. If you did, format your computer.

1 Like

I have an idea as to what is going wrong, but I have no idea of verifying it.

When looking through the logs I found that when it tries to start up the executable it does so with the following parameters.

x/x/x/_retail_/Overwatch.exe with args: -uid prometheus, pid: 19340

Based on when you start up other games it looks like this:

x/x/x/_retail_/WoW.exe with args: -launcherlogin -uid wow, pid: 23888

Pretty sure the name Prometheus is not a game and was added by accident and should probably have been Overwatch or OW or the like.

2 Likes

Worked perfectly! thanks

This didn’t work for me with the 0xE0010FF0 error.

I’m not sure what you or Twicth-1172 is doing, but I didn’t suggest or recommend anything. It was purely an observation based on the logs I could fetch.

I think they meant the methode of Dannemann

confirming Dannemann found the right idea to fix, specifically, the 0xc000007b “unable to start” error. instead of installing all the c runtimes, all i did to fix this was literally grab my vcruntime140.dll out of my W11’s sys32 folder and stick it in the game’s root directory (i.e. Overwatch/_retail_, next to Overwatch.exe). good luck

1 Like

Thx you for your time !

Error 0xE0010FF0 is still there and the game does not start. Verifying all game files brought up no errors and starting Overwatch.exe directly also did not help. Overwatch.exe also has no dependency error. However, this means that it is not an issue of the battlenet launcher. Clearing the battlenet cache also did not help.

2 Likes

same Error 0xE0010FF0, I have tried all the above and nothing has fixed it, its on bnet side

I finally found a hint at what is going wrong and it is precisely related to what I initially suspected: Blizzard changed some part of the code related to initializing the GPU. So, what is the hint that tells me this? I discovered a folder with Battlenet error logs that contain a lot of files named similar to “libcef-20241029T220817.693524.log” and these files contain the following error message:

[1029/221427.724:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is

So if the game cannot initialize the GPU, because someone messed something up, then it can of course not start.

Yup, I have those exact same error files.

I’m getting an error message for Sensapi.dll. Game crashes after 2 or 3 minutes into use. I would not mark this issue as “solved” at all.

I have done everything short of downloading the driver which I do not feel comfortable with doing since I was able to play it perfectly fine before the patch. Currently uninstalling and reinstalling it once again just to see if it works. The issue is not solved.

Neither works unfortunately