"Something went wrong with a file. We're not sure what caused it, so please try again or click the code below for more information."
BLZBNTAGT00000840
I recovered the bottle from a timemachine backup, tried crossover previews, tried reinstalling the bottle from scratch but to no avail. The same error pops up every time.
I'm able to reinstall the game so writing to the disk is no problem. But just before the install completes, one file apparently causes some kind of issue.
This looks like it’s related to battle.net and all blizzard games. I don’t know if this is helpful or not, but I found some some Reddit posts about Linux users experiencing this problem, using wine.
The posted solution was to change the version of wine, update, and then switch back, which currently would not be an option for us.
Got the same issue, both on crossover with d2r, and on the native bnet client for HOTS. Still able to connect to d2r with my switch, so definitely a bnet client issue. would be good to know if the problem also appears on PC
Very disappointed from this product - talking about CrossOver. I have bought this specifically to play D2R, but along with all issues with video performance now the battle.net client cannot be updated as well and I cannot even play. I have raised a case about the video issues which are around white artifacts appearing in certain areas when certain monsters are present but no resolution to this as well. Being honest I don't really think they will take this posts into account and fix the issue.
We absolutely will be investigating why the recent Battle.net update doesn't work with CrossOver, and we'll work on getting a fix out ASAP.
Gabriel, as our support folks have pointed out to you, your ticket responses are coming through without any content, which is why there has been no resolution.
I was directed to this fix in the Diablo 4 post in the forum. Made a backup first and followed the directions. Only fixed my Diablo 4 bottle so far and it works perfectly. (Have not tried it on my Diablo 2R and Immortal bottles because I am not currently playing them so will probably wait for the Crossover fix for those.
I was directed to this fix in the Diablo 4 post in the forum. Made a backup first and followed the directions. Only fixed my Diablo 4 bottle so far and it works perfectly. (Have not tried it on my Diablo 2R and Immortal bottles because I am not currently playing them so will probably wait for the Crossover fix for those.
Do you mind to share your Agent that work? Since mine dont have the old version? I'm a new CrossOver customer. Thanks in advances
When I put the D3DMetal thing to enabled, the game wont even start...
I have all three of my Diablo games (D2R, D4 and Diablo Immortal) in separate bottles. The bottle for Diablo 2R has all the advanced settings turned off and prior to the recent issues with updates, it ran and updated fine. The instructions posted to "fix" the Battlenet issue worked for me with my D4 VoE bottle but I did not bother with my other two Diablo bottles as I am not currently playing either of them and decided to wait and see if CodeWeavers comes up with a solution.
I was directed to this fix in the Diablo 4 post in the forum. Made a backup first and followed the directions. Only fixed my Diablo 4 bottle so far and it works perfectly. (Have not tried it on my Diablo 2R and Immortal bottles because I am not currently playing them so will probably wait for the Crossover fix for those.
Could you or someone else please share the Agent folder? I did not play any previous version via Crossover prior to the issue, so I am unable to implement the temporary workaround. Thanks in advance!
I tested Crossover 24.0.6 when it was released today and the Battle.net application started up with no trouble at all.
I saw that there was an update available for D2R and that the update was necessary before being able to launch the game. I requested the update but the update process errored out. See the screenshot for details.
Open CrossOver: If it's not already running, start CrossOver.
Quit the Battle.net client: Make sure the Battle.net client is fully closed.
Locate your Battle.net bottle: In CrossOver, click on the Battle.net bottle.
Access the C: drive: On the right-hand side, under "Bottle Actions", click "Open C: Drive".
Navigate to the Agent folder: Go to */ProgramData/Battle.net/Agent.
Check for agent versions: You should see two folders: Agent.8916 and Agent.8988. If you don't, you'll need to obtain the older version (8916) from someone else.
Open the folder in Terminal: Go back one level to the Battle.net folder, right-click the "Agent" folder, and from the popup menu select "Services > New Terminal at Folder". (The Services submenu is near the bottom of the popup menu that appears when right-clicking the folder.)
Delete the broken version: Run the following command in Terminal: rm -r Agent.8988 Or just delete it using the Finder. (Don't worry - if anything goes wrong, the client will re-download it)
Create an empty placeholder file: Run the following command in Terminal: touch Agent.8988
Make file immutable: Run the following command in Terminal: chflags uchg Agent.8988 To undo this later, when CrossOver implements a fix, run the following command in Terminal: chflags nouchg Agent.8988 to remove the flag and allow overwriting the file. Or just delete it using the Finder.
Launch the Battle.net client: Open the client from the Battle.net bottle.
Click "Update" on your game and enjoy it :)
If you do not have an Agent.8916 folder in your */Bottles/Diablo II Resurrected/drive_c/ProgramData/Battle.net/Agent folder, you can download it from my Dropbox here: https://www.dropbox.com/scl/fi/zvvvwiljayulalmd4hshu/Agent.8916.zip?rlkey=vggsm57f0b7v118rwwp2u4l16&dl=0
Please note that I am just some rando on the Internet and it is not safe to download and install software directly from people like me. But there it is if you want to risk it. Also note that Codeweavers might not approve of me making that folder available and so might edit or delete this message, in which case I will delete it from my Dropbox and not attempt to share it again.
Crossover 24.0.6 did not correct this issue and so I continued to use the workaround I described above.
Crossover 24.0.7 did correct this issue. D2R updates via the Battle.net application with no trouble and the game itself continues to run perfectly with D3DMetal and ESync enabled with my M4 Pro Mac Mini in MacOS 15.3 Sequoia.
–Before applying the Crossover 24.0.7 update, I unlocked the Agent.8916 dummy file and dragged it to the Trash.
–Then I updated Crossover to 24.0.7.
–Then I launched the Battle.net application which indicated that it wished to update itself. I chose to update and restart, and less than a minute later Battle.net was running again.
–Battle.net indicated that there was an update available for D2R. I clicked the UPDATE button, Battle.net performed its update without a problem, and just seconds later the button changed to PLAY. (As of this evening, Battle.net is up to Agent.8999.)
–I clicked the PLAY button and the game launched and ran as expected.
1
to 17
of 17
Please Note: This Forum is for non-application specific questions relating to installation/configuration of CrossOver. All application-specific posts to this Forum will be moved to their appropriate Compatibility Center Forum.
CrossOver Forums: the place to discuss running Windows applications on Mac and Linux
CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
