Couldn't update after 11.1, now can't install

i’m also experiencing this issue. i’m running on nixos, using lutris, and have had zero issues until today. my system is immutable, so, nothing has changed except for the battlenet client and game data.

i have attempted to uninstall and purge all game and VM information, and start from scratch, to no effect.

3 Likes

Similar to Dukhat, I’m good now too.

I changed my wine version in Lutris to ge-proton, launched the launcher, it downloaded the game. I switched back to wine-ge-8-26 and launched WoW.

Unfortunately I uninstalled the game and tried reinstalling initially, so I don’t know if that step is required or if it would have worked without doing that. I would also back up your interface and settings just in case.

1 Like

I run WoW through Lutris on Linux Mint. I was having the same issue. I can confirm that changing the Wine version in Lutris to ge-proton fixed my issue. I’m all good. Thanks everyone.

3 Likes

Using Bottles on Fedora I was having issues repairing, and now doing a fresh install. getting the xx845 error. Trying different runners doesn’t really seem to change anything at the moment. Any other suggestions would be helpful.

This resolved my issue as well using what has been said.
Under Lutris I changed the Wine runner to ge-proton and launched battlenet.
The game then successfully updated.
I then exited battlenet and switched the runner back to wine-ge-8-26 and I was able to log into wow.

3 Likes

I got the game reinstalled using ge-proton and switched back to wine-ge-8-26 and the game runs.

However, now I’m getting a couple little odd issues. Like, the cursor doesn’t change when hovering over certain NPCs and objects – it is always a hand.

3 Likes

I with you! I got 22 days left and if no fix… just wont resub until fixed. I went LINUX everything at home and office except for they make me keep Windows for work equipment

EDIT: The ge-proton in Wine worked to get updated. Sad they just don’t have LINUX version for us geeks

3 Likes

Have fun, I suppose. Make sure you’re reaching out to Linux in order to get it fixed, though.

Edit aside, they’re still your first stop in this case next time this happens. Players can sometimes help, but fixing compatibility issues will be wholly in Linus’ court and/or whomever developed your specific compatibility layer.

1 Like

Hi,
I also had this issue running the game through Lutris on Arch Linux. When I went into the runner options on Lutris, it said that the version of GE-Proton I was using was out of date, so I just switched it to the normal GE-Proton version, and everything worked fine! No reinstall needed :slight_smile:

3 Likes

Since i was at work most of the day, I came here first because I figured:

  1. Someone else had the issue
  2. Someone probably figure it out

But Yes, LINUX and LINUX app support is where I would be monitoring next and if needed upload information that would help.

Fixed it. Going to do my best to recall the process. I NEVER UNINSTALLED.

Update → Something went wrong.
Update → Something went wrong.
Scan and Repair → Something went wrong.
closed bnet (launched via the installer as a non steam app), killed the app via steam X STOP, as I always need to do. Manage the non-steam App, switched from Proton Experimental to Proton 8.0-5. Launched.
Update → Something went wrong.
Scan and Repair → Something went wrong.
Closed app in the same way.
IIRC, Switched non-steam app to Proton 9.0-4.
Took down a custom “bad servers” firewall.
Update → Something went wrong.
Closed app in the same way.
Put the “bad servers” firewall back up.
Went into steam settings >> Compatability >> Run other titles with: Switched from Proton Experimental to Proton 8.0-5.
Switched non-steam app to Proton 8.0-5.
Launched the non-steam Bnet installer. I was presented with a language selection this time. (I PANIC LOL)
Switch both settings to Proton 9.0-4. Presented with a language selection.
Switch both settings back to Proton Experimental. Presented with a language selection (Swig of whiskey).
Select language, hit okay.
Bnet had removed my previous account verification cert/cookies.
Typed in password. Had to use 2FA.
Games showed as uninstalled. Favorite games were reset.
A moment… WoW started updating by itself. WoW was fully installed and resumed the update.
I had to switch accounts from a secondary account to the account I use now.
WoW Classic shows installed when I switch back to it.
Add Hearthstone to favourites, it is installed.
WoW install finishes, having started the download at about 1.30GB/1.31GB.
Launch WoW, verify 2FA. Enter game, jump, Exit game /thumbsup.

1 Like

Same issue here!

I’ll try those steps when I get back home!

Thank you!

Yes, just opening Lutris and changing the Wine version makes battle.net start up successfully. You may have to try until you find the one that works.

1 Like

You need STEAM installed though. i dont have steam gaming on this system

Thank you. This worked and was super easy

Fingers crossed, as the install is still running, but swapping to GEProton in Lutris seems to have allowed my download to actually start instead of erroring out almost immediately. Thank you, whiskey-swigging orc.

This worked for me as well.

Thank you!

I was still getting the same error, even when trying to use GE-Proton to try and install the games.

However, I was able to get around the error by:

  • Removing all Battle.net files
  • Configuring Lutris to use GE-Proton
  • Install the Battle.net launcher (which kicked an error at the end of the install, but still installed)
  • Changed Lutris preferences back to Wine
  • Launched Battle.net launcher
  • Installed Retail and Cata Classic without any issues.

I tried to save time by using a backup copy of Retail, but it wouldn’t recognize it, forcing me to download the full game (RIP data cap).

For tech novices likenmyself using a Steam Deck on the Linux OS base, do I understand correctly that simply changing the proton version in Compatibility until “wiggling the handle” knocks the problem loose is my best shot here?

Everything I’ve seen has been about Lutris, but yes, changing the compatibility seems to be working.

I’d try using a different proton version on the SD to see if you can successfully update, then switch back to what was working before.

1 Like