This is probably part of a bigger problem that isn’t yet solved, as HotS also won’t install even after Battle.net started. Looking up the error codes in regards to wine shows that it’s a recent and common problem.
The appropriate fix to solve these issues are part of GEproton9-23 (see very first entry). I strongly suggest implementing this as custom runner for Battle.net in the installer.
I’m not sure why this took a couple of tries but updating the runner to GEproton9-23 did eventually work. (None of the other runner swaps recommended worked for me.)
This is not super relevant but just FYI if you stumble into this thread, the newer versions of wine staging didn’t appear to work. I tried the 10.0 version which came out yesterday (Jan 21st).
I had to switch back from ‘Proton Experimental’ to ‘wine-ge-8-26-x86_64’ and then i could update and play again. Just in case for someone else the Proton environment doesn’t work.
Hi. I had the same issue.
Ubuntu 24.10
Latest Lutris.
Also reinstalled diablo 4. But no change.
Then I installed with ProtonUp-Qt (ProtonUp-Qt-2.10.2-x86_64) wine-proton-9-0-4-amd64 and this fixed the issue.
Installed from Kro4ek Wine-Builds Vanilla
Hope this helps some one else
Still getting the BLZBNTAGT00000840 Error, switching between versions seems to be working for now, but seriously does anyone have a solution other than swapping between wine versions? I would say this issue is not solved so who marked it as such?
I did, because I’m the thread-opener and its good custom to do so, since the 840 error I reported was solved for me and others.
Edit: And the issue is back with the next update and swapping does not work. People on the US Forums tried another trick that was successful in the past which is described here: Unable to update games with error BLZBNTAGT00000840 - #30 by KasiKuula-2657 - Desktop App Bug Report - Blizzard Forums - please also read the replies. For this to work you need to have an older agent version in your directory. I had one and there was no need to fix anything, the update just worked.
This is again not a permanent solution, sooner or later we will need the updated agent. I would have preferred the version-swap-around.
I had this issue this morning. I switched from ge-proton to GE-proton (no idea what the difference is) and nothing worked, update failed at 93%. I then switched to wine-ge-8-26-x86_64 and still no joy. I then switched back to GE-Proton and it worked. I have since downloaded this version and placed it in ~/.local/share/lutris/runners/proton. I’m now running GE-Proton9-23, so hopefully this will fix the issue!
I have tried everything in this post, and even with this GE-Proton, Proton 9.0, Proton Experimental, it fails very quickly and doesn’t even open. The default Wine fails with the error in a download/update.
People made me belive wow worked in linux, well… Guess I am unlucky with the timing
Battle.net update error on Lutris:
since latest update, Battle.Net has issues on Lutris and globally Wine.
But this issue are fixed in Proton-ge 9.23.
→ How to install Proton-ge 9.23 for Lutris
1) First be sure you use the latest Lutris version: 0.5.18 2) download Proton-ge 9.23
3) extract archive in this place:
Lutris native: /home/$USER/.local/share/lutris/runners/proton/
Lutris Flatpak: /home/$USER/.var/app/net.lutris.Lutris/data/lutris/runners/proton/ 4) now restart Lutris and change Wine version associated to your Battle.net version to Proton-ge 9.23
Now Battle.Net should work as intended in Lutris.
Nota: A) even if there is an error during Battle.Net install, the install stop towards 98%, you can ignore it, launch Battle.Net, everything works fine. B) For Lutris native version, you will need to install umu-launcher to use Proton-ge and Steam Proton too. See their Github page: GitHub - Open-Wine-Components/umu-launcher
Thanks for the help, I had tried that before with that release and got this weird Python error:
Start monitoring process.
Traceback (most recent call last):
File “/usr/lib/python3.8/runpy.py”, line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File “/usr/lib/python3.8/runpy.py”, line 87, in _run_code
exec(code, run_globals)
File “/home/user/.local/share/lutris/runtime/umu/umu-run/main.py”, line 5, in
File “”, line 991, in _find_and_load
File “”, line 971, in _find_and_load_unlocked
File “”, line 914, in _find_spec
File “”, line 1407, in find_spec
File “”, line 1381, in _get_spec
File “”, line 1362, in _legacy_get_spec
File “”, line 414, in spec_from_loader
File “”, line 709, in spec_from_file_location
File “”, line 191, in get_filename
File “”, line 713, in _get_module_code
File “”, line 647, in _compile_source
File “/home/user/.local/share/lutris/runtime/umu/umu-run/umu/umu_run.py”, line 662
xdisplay(“:0”) as d_primary,
There was a umu-run in .local/share/lutris/runtime/umu, probably automatically installed by Lutris? But I noticed the Python syntax error and suspected it might be a not compatible “compilation”. Maybe using a different Python version than my system Python (Ubuntu 20 3.8)
So I went into the GitHub, compiled my umu-run and replaced the one there, and now Wow is installing.
TL:DR I think the newest Lutris + Proton GE is not working with the embedded umu-run, and the user needs to compile its own umu-run and replace the lutris one in lutris/runtime/umu
Lutris Flatpak provide the right umu-launcher version. But Lutris package provided by official Linux distribution does not yet provide the latest umu-launcher package. Without the latest umu-launcher package, Lutris 0.5.18 can not use correctly proton-ge and other Steam Proton version.
If you use a Debian-like distribution, you do not need to compile umu-launcher, there is a deb package available on their Github page. Then umu-launcher package will be soon available as an official package for all Linux distribution.