Diablo IV Forum

Diablo 4 game hasn't been running since I ran the update on Steam since early this morning. I need an answer for why this is happening.

Same issue since the patch.

Microsoft Visual C++ Runtime Library

Assertion failed!

Program: C:\windows\system32\winevulkan.dll
File: ....\wine\dlls\winevulkan\loader_thunks.c
Line: 2887

Expression: !status && "vkCreateImageView"

For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts

(Press Retry to debug the application - JIT must be enabled)

--

It also seems like BattleNet insists there is an update, although it updates to full prior to pressing play. Version says 1.4.2.54489.

Turned on D3DMetal and Esync and it seems to have fixed it…

THANK YOU! Had the same issue. Would have had no idea how to fix it. Many thanks!!

can't play too. After update the new patch, the battle net just insist to update again and again.

i've turned on D3D and ESync, but still got the exception... does any one have the same issue?

how to fix?????

nothing to change... same..can't play

Sadly D3DMetal is not really an option for Intel Macs that ran Diablo 4 so far.

From the error message it looks like the Wine-Vulkan implementation has a problem since the patch?

Same for me.
I also can't seem to update the Battle.net software.
I've deleted everything and reinstalled, but still... Old version, and game crashes before it loads with the same message as everyone else here.

Et Mitsurugi wrote:

Sadly D3DMetal is not really an option for Intel Macs that ran Diablo 4 so far.

From the error message it looks like the Wine-Vulkan implementation has a problem since the patch?

before i didn't use D3D and Es~~~ something, and just fine to play the game.. but now i don't know why...

Anyone can play game??? I still can't play.

Assaf Marx wrote:

Same for me.
I also can't seem to update the Battle.net software.
I've deleted everything and reinstalled, but still... Old version, and game crashes before it loads with the same message as everyone else here.

same with you. have you fix it?

다 같은 문제가 있군요.
저도 마찬가지입니다.

crossover 에서 고쳐줘야되는 부분 같은데....

제발 고쳐줘요!!!

Assertion Failed!
Program: C: windows|system32\winevulkan.dll
File: //wine/ds/winevulkan/loader _thunks,5
Line: 2887
Expression: status Ba. "Vl CreateImageWiew
For information on how your program can cause an assertion
Failure, see the Visual C++ documentation on asserts
(Press Retry to debug the application - JIT must be enabled)

Had problem with Diablo 4 not running with "Contact Blizzard" error. Here's what I did on my MBP M2.

1. Uninstall Diablo 4 and Battle.net and delete the bottle
2. Reinstall Diablo 4 - but no high definition texture
3. Turn on D3DMetal and Esync

so u can play now?

Lokhere wrote:

Had problem with Diablo 4 not running with "Contact Blizzard" error. Here's what I did on my MBP M2.

1. Uninstall Diablo 4 and Battle.net and delete the bottle
2. Reinstall Diablo 4 - but no high definition texture
3. Turn on D3DMetal and Esync

so can play now?

Is there a fix on Intel Macs please? This is pissing me off. Thanks

I'm not sure if it's a problem with Crossover or Steam. I think I've reinstalled it about 5 times already.

isrhapahael wrote:

I'm not sure if it's a problem with Crossover or Steam. I think I've reinstalled it about 5 times already.

Battle.net also has the same problem

Hi all!

Experience same problem as wolv32.

Battlenet indicates an update (green arrow on battlenet logo). I let the new patch install. Launch button indicates play, nothing happens and turns back to update. Green arrow hasn't disappeared.

Then I get a Blizzard error message saying: An internal error occurred. Please wait a few moments and try again. If this error continues, try restarting the Battle.net desktop app. Error Code: BLZBNTAGT00001398

Blizzard suggests:

This error is caused by performing conflicting actions at the same time. Follow the steps below to resolve the problem.

1.This problem will often resolve itself, try again.
2.Restart the Battle.net desktop app to clear any stalled Agent processes.
3.Delete the Battle.net Tools folder to automatically rebuild outdated or corrupt files.
4.Restart your computer to resolve problems caused by programs and services running in the background.

I have done and executed what Blizzard suggests to do a dozen times over the last few days since D4 isn't working. Nothing helps.
It's annoying and frustrating to say the least.

@ codeweavers-team: please can anyone from you shed a light on this problem? What causes this (Blizzard patch? Crossover bug/problem since new patch? Internal Mac problem?) Don't leave us sitting here in the dark.

Thnx in advance!

Tomas Bossuyt wrote:

Hi all!

Experience same problem as wolv32.

Battlenet indicates an update (green arrow on battlenet logo). I let the new patch install. Launch button indicates play, nothing happens and turns back to update. Green arrow hasn't disappeared.

Then I get a Blizzard error message saying: An internal error occurred. Please wait a few moments and try again. If this error continues, try restarting the Battle.net desktop app. Error Code: BLZBNTAGT00001398

Blizzard suggests:

This error is caused by performing conflicting actions at the same time. Follow the steps below to resolve the problem.

1.This problem will often resolve itself, try again.
2.Restart the Battle.net desktop app to clear any stalled Agent processes.
3.Delete the Battle.net Tools folder to automatically rebuild outdated or corrupt files.
4.Restart your computer to resolve problems caused by programs and services running in the background.

I have done and executed what Blizzard suggests to do a dozen times over the last few days since D4 isn't working. Nothing helps.
It's annoying and frustrating to say the least.

@ codeweavers-team: please can anyone from you shed a light on this problem? What causes this (Blizzard patch? Crossover bug/problem since new patch? Internal Mac problem?) Don't leave us sitting here in the dark.

Thnx in advance!

"They are telling us to set up and enable two options.

A week has just passed. I was told to wait, but there have been no updates or changes... When is it going to change? I don't have to wait two weeks or a month, right?

hope so. we've paid for this software, but I don't feel comfortable with this kind of service.

so i have done some research...

this is not codeweavers fault. it is blizzard. it's always blizzard.

they released a patch that sunday, june 9th.

since then, i have also had the same error (intel mac, mac pro)

blizzard will not publicly acknowledge it, but it is something they broke in the process. they were happy to keep taking folks money with the new expansion, and even released a new build to fix COSMETICS, but left thousands of us unable to play.

there is a patch today sometime, so keep an eye out for the update. i am not optimistic they will fix it. but we can hope.

UPDATE: new patch still does not fix it. have to use GeForce NOW to play =[

It's not just Blizzard that's the problem, right? We've been waiting without any progress for a week, and they haven't informed us of anything. We're just sitting here waiting. Even if the issue occurred because of a Blizzard update, isn't the program we're paying to use supposed to manage it? Regardless of where the error or conflict originated, they should address it quickly, don't you think? Am I wrong? Even when we submit inquiries, all we hear is "Just wait." That's the only response we've gotten. The season has ended, and an expansion pack is coming out, but they're making us lose all interest and fun.
Maybe I'm just impatient, but it's frustrating. Why? Because we can't play the game.

actually, no. this is not a codeweaver's problem at all. they can't manage a massive memory leak (i'm a dev, i've read the crash data) in blizzard's build.

they refuse to acknowledge it. it is disgusting.

https://us.forums.blizzard.com/en/d4/t/06092024-diablo-4-recurring-game-crashing-issues/169916/

plenty of us with the same issue - no common denominator on hardware - the build is just jacked for random machines.

it works perfectly on GeForce NOW! thank god. even better than on crossover. honestly probably where i am spending my money moving forward. never have to worry about this nonsense again.

"I’m so frustrated. Fix this quickly. How long do I have to wait? It’s been over ten days already."

me too. like we've paid for nothing. and what makes me even more angry is that they seem don't care about the users' feelings.

Are they busy with updates, or is there another pressing matter? The reason we use your program is for convenience, and since we don't know how to set it up ourselves, we pay for it. Why does it feel like only we are in a hurry?
We are experiencing an error related to Microsoft Visual C++. The main system running it is a crossover, and if it’s a Vulkan problem, it indicates a fundamental issue that isn’t Blizzard's or Steam's fault. (Of course, Blizzard isn't perfect, and neither is Steam.) But after a week or even ten days without any response or fix, what is the person who says it's not a crossover issue thinking?
If this program works like a VPN to bypass issues, then there should be other alternatives or solutions, right? What about our time over these ten days? Complaining here seems to be all we can do. Additionally, suggesting using NVIDIA GeForce Now? Are they getting advertising fees from there? Who will pay for using it? Will Crossover apologize for the long wait and cover the costs? Why are updates to any bugs or issues so slow?
Well, maybe after a month, might just rate this program as garbage.
Coming here and complaining every day feels like keeping a diary. Maybe someday, someone will listen.

I can't play either, clicking on Steam has no response

lwbg wrote:

I can't play either, clicking on Steam has no response

wait~ just wait~

It works at my system after using dx3d und esync and I start battle.net first not diablo 4 icon.
On MacBook Pro M3 Max

derFleck wrote:

It works at my system after using dx3d und esync and I start battle.net first not diablo 4 icon.
On MacBook Pro M3 Max

I'm experiencing something similar. The only difference is that I launch Diablo through Steam, not Battle.net. However, I can't play it. Why might that be? Everything else is the same as you described.

I'm using battle net, but the method above doesn't work for me either. I'm on mbp m2 max. don't know why.