Battle.net Desktop App Forum

Past couple days Battle.net generates lots of Wine debugger console windows and error modal windows. "The program Battle.net.exe has encountered a serious problem and needs to close." Clicking to dismiss the errors seems to let the load proceed, but will get new debug and error windows every minute or so. Had been working well before. This is on an M3Max Mac, running macOS 14.4.1 (64GB of RAM).

This machine had been playing Diablo 4 quite well, and of course, loading Battle.net to launch Diablo as part of that.

I have once or twice been able to eventually get to an open, fully-rendered Battle.net screen, but it may take 10 or 20 minutes to get there, maybe more. Even then, the UI is extremely non-responsive. Clicking Play on the game shows no UI recognition, but a couple minutes later the game did launch and play well. Even still, Battle.net would throw the debugger windows and error dialogs continually while playing.

Very annoying, and very hard to even know if you clicked the button to play properly. This is Crossover 24.0.1

The problem seems to come and go, but rebooting isn't enough to guarantee success.

Are other people having any issues loading Battle.net desktop on recent macOS builds? Has become very brittle: slow, errors and console windows, etc. If I can get through it to launch Diablo 4 the game actually plays alright.

Having the same issues. Battle.Net is incredibly slow, laggy, unresponsive and only signs me in half the time.. Are there any easier ways of launching Diablo?

This has just continued. Agree - is there a way to skip the Battle.net launch to get Diablo to load? I don't care about the desktop app except to launch Diablo 4, but it takes a half hour sometimes of dismissing error screens and other issues before I can successfully click the launch button.

I was trying some different configs to resolve this issue and I may have found one: changed Windows version from 10 to 11 on Wine Configuration -> Applications and the crashes and slutters went away. Not sure if it's a persistent solution, but so far I opened Bnet about 10 times and all of them loaded fine. Opened after quitting Crossover and without quitting, everytime loaded fast and didn't pop the error window.

Tested with "Use browser hardware acceleration" ON and OFF, both worked equally

• Using Sonoma 14.5 - MacBook Pro 16" - M1 Pro 16GB

Thanks for the tip, but so far no luck. I switched to Windows 11 and rebooted. The launch was still super slow, generating one of the console window crash errors. I can keep clicking through the errors, and click into the Battle.net window (until it crashes again) and eventually get to the Play button for Diablo 4. At which point the game works well.

But the result is it takes 15-20 minutes to launch the game each time I do a clean new launch of CrossOver.

Battle.net seems to eventually get into a safe state if I dismiss the crash windows even enough times. But the move to Windows 11 didn't seem to fix things for me, sadly. I'm presently trying the Beta path for Battle.net app, but it has the same issues as the GM release train.

Sigh, oh well. Hopefully a patch is coming.

Sorry to hear that. After the change I never got the slowdown issue again. It was like yours before (15-20 min to load, click close again and again until I could click play).

The other settings are pretty standard (D3DMetal ON and ESync ON). Before changing to Windows 11 I tried to run with WINE_SIMULATE_WRITECOPY=1 (but dind't load) and tried to disable dbghelp on the Libraries tab, under "New override for library", enter "dbghelp" (without the quotes), then click "Add". Next, select "dbghelp" under "Existing overrides" and click "Edit" and in the new pop-up, set it to "Disable". Disabing dbghelp didn't load Battle.net either, so I removed the override and saved.

This last tip I got from https://www.wine-reviews.net/2016/08/ (If Battle.net crashes on start). Pretty old info but I was desperate :)

Don't know if any of the steps above had any impact on the bottle. Last change I made was switching from Windows 10 to Windows 11.

Now it consistently load within 30 seconds after I double click Battle.net icon on Crossover and the launcher runs without any issues, I can click on everything and scroll, both super responsive

Thanks again for the help. I think I'll go with these settings on a brand new bottle. Maybe something got a bit messed up. Glad to know there is a chance of ending up in a good place again!

I am experiencing the same type of issues as well. Will keep checking back.