Posts about Battle.net
If you are unable to play World of Warcraft because of the battle.net launcher changes, cancel your subscription
Just go to https://account.battle.net/overview and click Manage. You will not lose any game time you have payed for, and can resubscribe at any time.
Please keep in mind that Blizzard never claimed to support Linux, so when trying to contact them on Twitter/forums please don't act like they owe you something.
There has been a lot of comments showing up about problems with battle.net games starting today. It appears that Blizzard has updated their Agent.exe to a new build today. The new build is 18.104.22.16809
You can check this by navigating to your ProgramData/Battle.net/Agent folder in your game prefix and you should have Agent. folders for the different versions. If you examine the Agent.8009 folder, there is a Errors folder with a bunch of crash reports. It seems that something is missing leading to an ACCESS_VIOLATION error and the crash of the Agent.exe. Hopefully someone with more knowledge of working out what file is being called can use this information to announce how to rectify this issue.
An application encountered a critical error: Program: C:/ProgramData/Battle.net/Agent/Agent.8009/Agent.exe Exception: 0xc0000005 (ACCESS_VIOLATION) at 0023:0x18f The instruction at "0x0000018F" referenced memory at "0x0000018F". The memory could not be executed. <Application>Agent <BlizzardError.ProjectId>1001 <BlizzardError.Module>Agent <BlizzardError.BuildNumber>Agent 22.214.171.12409 <BlizzardError.Platform>All PC <BlizzardError.DesktopOS>Win <BlizzardError.IssueType>Exception <BlizzardError.Priority>None <Exception.Summary:> 0xc0000005 (ACCESS_VIOLATION) at 0023:0x18f <:Exception.Summary> <Exception.Assertion:> Thread 0x00000464 DBG-ADDR<0000018F>("") DBG-ADDR<00669CEA>("Agent.exe") DBG-ADDR<004CA314>("Agent.exe") DBG-ADDR<004BB545>("Agent.exe") DBG-ADDR<00478F34>("Agent.exe") <:Exception.Assertion>
Something appears to be fixed! We need more data. WoW, D2R users ... please chime in!
Tested: (by me)
Hearthstone (still has that ugly title screen video thing .. probably my version of proton)
Diablo II Remastered
Tested: (by others)
It is normally for Battle.net to hang on launch periodically. If you don't see the login screen within 5-10 seconds, back out and run again. Usually works the second or third time. I think it has to do with some initial background update that hangs the UI.
Last Update: 9/21/2022...
Since we get like 100 posts a day about this, I figured I'd put SOMETHING out .. maybe those sorting this sub by NEW will see it.
There is no fix yet. It appears to be WINE compatibility issue dealing with some sort of certificate validation on Blizzard's end. TOP ... MEN ... are working on it ... TOP ... MEN ...
Now, what can you do in the meantime as a work around?
This thread at the Blizzard forums seems to be being kept alive and up to date. This is where I get my info ..
WineHQ is tracking it. Techie speak here.
If you want to dink around with Lutris or Bottles, there is a fakery that requires some advanced knowledge to circumvent. This is simply locking Blizzard out of updating the AGENT.EXE to a version that is incompatible but people say their games will still not update on their own. This appears to cause many games (or PTR of games) not to update which in turn doesn't allow them to run.
If you still have Blizzard.net and the game installed (even if it isn't working), change the non-steam game launcher to point to the game's RETAIL folder where the game's EXE can be found (aka OVERWATCH.EXE). So far, I can confirm this works for Overwatch.
Copy all the Blizzard content (including your game) from your PC to the Deck into a proton prefix and run the game directly from there. For Overwatch, the game will require you to login every time you play - nor will the game update itself (you'll need to keep the game updated on your own). Obviously you need a PC for this - at least one that is capable enough to install Battle.net and your game (even if it can't really run it). Overwatch has a nasty niggle with this process. This has been confirmed NOT to work with Diablo 2 Resurrected and WoW. If you have other games tested, please leave a comment.
Some have taken to streaming the game from their PC to the Deck until there is a solution.
The best thing you can do? Don't post asking for updates. Watch this sub - change your sorting from HOT to NEW and check back a few times a day. If you're eager, follow the threads listed above - they will have updates probably before we will here. I will try to update this thread as we get more data.
It will be Big News(tm) when the fix comes out and everyone will be yelling about it (and it likely won't be upvoted enough to get to the HOT spot).
Here is my video (hastily shot on my lunch hour) to help you "sideload the whole thing from a PC". So far, I can only confirm this works on Overwatch and doesn't work on WoW, D2R.
Thanks. Have faith. The community is AWESOME. A fix will come.
Let me preface this with I am a software developer and consider myself technically verse.
Battle.net (and WoW classic) worked yesterday. I did not change anything but suddenly today, on starting up Battle.net, the update for WoW kept restarting and never allowed me to launch.
I have now spent hours reinstalling Battle.net. I’ve done it every way I know of:
Using proton ge through adding an external game in steam (like https://bittsguides.com/install-wow-on-steam-deck/amp/)
Every one of them fails at the same spot—during the install of Battle.net, the “Updating Battle.net Update Agent”.
Since then, I have:
Flushed my DNS
Factory reset the deck
Nothing I do can get the updating to finish.
Any help would be appreciated.
Edit: for now you can add your WoW classic exe to steam with proton GE forced (this probably works with other games too). You do have to manually log in but at least you can play.