CrossOver Support - Community Forums

I did ! :/

For what it is worth, I have access to two other Macs. I tried making a D4 bottle on one of the others and it failed. Finally saw stuff online suggesting that it would fail if the Mac version of Battle.net had ever been installed. Attempted to purge Mac Battle.net from my main system but it didn't work. Tried making a bottle on the Mac that had never had crossover or Mac Battle.net installed and was able to successfully create a D4 bottle. Exported it and then imported it to the Mac where I play. So far, so good. (all with version 24.0.6)

i think i'm gonna erase all my mac to try this... ahahah

Enabling D3DMetal + Esync did it! I had no idea I needed to switch those two on. Running like before now. Thank you!

The new battlenet update from 1/27 8999 tanked on my mbottle I ended up opening the bottle and deleting that folder and creating the file to prevent it from installing. I am still working with agent 8916. Running Crossover 24.06

Okey so ... Thanks a lot for your advices !!!! Because after desinstalling the Mac os Version of Bnet and active Esync with 3Dmetal it's working... Wouawwww !! God is great ! ahah

Wanted to report that the last beta version is working for me finally - i dunno what happens when the demo expires in a few days for the better-test version though?

Wasted Post LOL I think I responded to a removed post. LOL

Since 24.0.7 is out, I thought I'd post my experiences. First, what did not work:

• Letting CrossOver self-update then attempting to update Diablo IV, leaving the existing bottle in place. CrossOver crashed during the D4 update attempt.
• Deleting the Battle.net bottle then trying a reinstall of Battle.net. The install failed; CrossOver hard crashed, app vanished, at some point during the install.
• Exit CrossOver, restart it, then attempt reinstall Battle.net again. This failed as well; apologies as my notes left a gap here... but CrossOver remained running, but crashed shortly after I tried to exit (Cmd-Q) it.

What did finally work:

• Trash CrossOver.app. I DID NOT use the CrossOver Removal Tool.
• Redownload CrossOver 24.0.7
• Reinstall
• Use CrossOver's app selector to create a new Battle.net Desktop App bottle, then install Diablo IV.

Notes: I did see a "BLZBNTAGT00000840" error dialog during the final Battle.net reinstall, but closing that dialog let the install proceed and complete correctly. Battle.net started up after that, and as I said, the Diablo IV reinstall worked.

It's a bit concerning that the upgrade doesn't seem to have produced the same result as a reinstall. This feels like a red flag on the upgrader – ideally the upgrader vs. the installer for the same version should always produce the same result in a repeatable manner.

So, updating to 24.0.7 did absolutely nothing for me. Fresh bottle trying to install Battle.net, gets stuck at 45% download/progress installing the actual Battle.net Desktop App.

Then tried copying over all the Files from a working Win10 PC install from my gaming PC, everything in "Program Data" and "Progam Files (X86)" that is related to Battle.net. Then tried manually installing the Windows Battle.net installer on that bottle. Took strangely long, but eventually worked.

Couldn't log into Battle.net though, said I was in a queue. Killed every single Intel process on the Mac in Activity monitor, deleted Crossover through the Trash and reinstalled it from a fresh download. Then manually ran the Battle.net Launcher from the C: Drive in the corresponding bottle and now it lets me install Diablo IV from scratch. Because it's 140GB, it's going to take a while before I can report back whether it actually runs, too

However Crossover doesn't recognize that Battle.net has been successfully installed in that bottle now, so I have to manually launch the Battle.net Launcher from the C: drive. That's ok for now.

My feeling is, this is not a Battle.net issue, but an installer/updater issue. Maybe the script for installing Bnet needs some attention, maybe one of the links/servers is deprecated.

PS: So Diablo IV installed successfully and runs as well as it did before. What's suspicious again is that Bnet wants to update the game again after running, but only changes a few bytes, as far as I can tell. Strange.

Everytime I pressed Update (Hearthstone and Diablo II re) I got this error

macOS 15.2
Crossover 24.0.7

Turn on D3DMetal and ESync, now I can play normally

What's suspicious again is that Bnet wants to update the game again after running, but only changes a few bytes, as far as I can tell. Strange.

The "false alarm" update notification has been an ongoing but otherwise harmless bug with CrossOver Mac and Battle.net for months now. To my knowledge, it hasn't affected real upgrades or the use of Battle.net and its installed games. Certainly not in my usage, in any event.

Just to confirm regarding the "false alarm" upgrade notifications with Battle.net: I received and installed a real update notification (I believe for the 2.1.1a patch, 2025-02-05), and that installed just fine on my one-again-working setup with CrossOver Mac 24.0.7. I still get the "false alarm" – basically, after the first time starting Battle.net or D4, Battle.net/D4 will show that an update is available when it isn't. Choosing to update will make Battle.net spin for a short while then decide no update was needed, fixing the update status until the next time around.

Hi Everyone!

I also get the false update (it does it's thing while b.net starts up) And have had no issues with the game running at full speed with hi-res mode on and just about everything set to hi in graphics settings. MBP Max 64GB M4.