BLZBNTAGT00000840: Something went wrong with a file

[Aeternethy-ravencrest]

Did not work for me. I tried it like Elementuml described.
I’m on Pop!_OS 22.04 LTS and run WoW via Bottles.

It seems that only the Launcher has an issue of not recognizing that the client has been updated. I can run WoW.exe from my normal Bottle with wine-ge-proton-8-26. Logged in and I can play without any flaws.

[Kuhle-wild-growth]

Here’s what I did to get it working again on Steam Deck

1. Install Lutris
2. Find and install Battle.net through Lutris
3. Change the runner for Battle.net to GE-Proton (before that it would bring up the error on installation)
4. Run Battle.net through Lutris or desktop icon
5. Moment of truth, download WoW
6. Go back to Lutris and change the runner back to the default Wine
7. Add Battle.net to Steam (because you want to be running it in Gaming Mode for proper controls with ConsolePort) (adding it through Lutris didn’t work, I had to add it by right-click on the desktop icon for Battle.net)
8. Don’t force any compatibility layer or whatever through Steam, it should just run as-is with Wine

[Crimsond-draenor]

None of the battle.net workarounds worked for me.
Until this is fixed, I changed the path in steam to open wow.exe instead of battle.net.
I have to manually login every time I start the game, but at least it’s working.
Hope they fix it soon.

[Lyralise-argent-dawn]

The original workaround switching Proton versions around doesn’t work anymore, at least for me.

The ‘stable’ way I was able to find that works for me as of 22-01-2025 is:

1. Use GE-Proton9-23 or higher.
2. Remove the following three folders in your Proton prefix under: /home/yourlinuxusernamehere/.steam/steam/steamapps/compatdata/3525597976(though your compatdata number might be dfifferent)/pfx/drive_c/ProgramData

• Battle.Net
• Battle.net_components
• Blizzard Entertainment

3. Once Battle.Net start it will tell you WoW isn’t located. Click ‘Locate Game’.
4. Select the World of Warcraft folder in the window that opens and click ‘Open’.
5. The patch should now install normally.

[Sanrie-argent-dawn]

Did a fresh install of Battle.net and WoW during the last reset. The new error hasn’t ocurred for me. Running on the latest Linux Mint and through Steam with Proton Experimental and an AMD system.

WoW is running fine on Proton Experimental too so no need to switch back for me (yet).

[Crimsond-draenor]

Tried again today, battle.net launcher had an update, seems to be fixed.
After updating and restarting the launcher I was able to start WoW without issues.

[Regrin-pyrewood-village]

Alternative workaround:

Based on a suggestion from /r/linux_gaming Reddit, the problem is within Battle.net Agent version 8988. If you happen to still have an older Agent version present on your system, simply remove everything from the version 8988 and make that directory immutable:

(change the path accordingly if yours differ)

rm -r ~/.wine/drive_c/ProgramData/Battle.net/Agent/Agent.8988/*
sudo chattr +i ~/.wine/drive_c/ProgramData/Battle.net/Agent/Agent.8988

This will prevent Agent from being updated to version 8988. Solution is useful for those of us who use vanilla Wine without Lutris or Steam and cannot switch to Proton runner.

@Crimsond: I’m happy the lastest Bnet update worked for You, but it didn’t fix it for me. This workaround was the only solution in my case.