Battle.net App

Got the login winedbg loop with battle.net. From a quick search online i did this instead - If you add "battle.net-Setup.exe" to steam as a non-steam game, and force it to run with proton (I used proton 9.0.2), steam will handle the installation in the same way it does with games you get off steam (for the most part). This allowed me to login to battle.net and install wow (currently installing). hopefully this helps for the time being.

Yo, did wow launch without issues? I'm currently trying to do this and was hoping you would give feedback.

Yea it worked fine, battle.net updater got stuck at 64% once on startup, but apart from that its been good

Stopped working with 9.16-staging, the app ends up in a debugger loop on startup. Had to downgrade back to 9.15.

"wine: Unhandled exception 0x80000003 in thread 4bc at address 69E400E1 (thread 04bc), starting debugger..."

System information:
Wine build: wine-9.16 (Staging)
Platform: x86_64 (guest: i386)
Version: Windows 10
Host system: Linux
Host version: 6.7.12+bpo-amd64

does it work with 9.16 non.staging?
ntdll write patchset was changed in staging for this release.

it does not working with 9.16 non-staging

I have problems with 9.17 too (both vanilla and staging).

For the moment I am configuring my package manager to keep wine-staging at 9.15 (at least as long as Gentoo main tree keeps it available).

Any chances of this working again without a custom build and extra patches?

Try wine-staging 9.6
I had no problems

i have a black screen on 9.6

Working for me on 9.8 staging

I was able to get it working on Ubuntu LTS 22.04.3 with the following steps. Not sure if all steps are needed.
1. Clone Wine from source.
2. Perform git checkout wine-9.4
3. Apply this patch by hand: bugs.winehq.org/attachment.cgi?id=75727&action=diff
4. Build for WoW64 (32+64 bit). It was important to build in an empty folder and not in the source tree, and to build x64 first, then build x32, while pointing to the x64 build. Anyway, this is covered in the standard build guide, nothing unusual: wiki.winehq.org/Building_Wine#Shared_WoW64
5. Clean prefix. Default 64-bit mode. (rm rf ~/.wine)
6. Start installer and install Battle.net
7. Once install is complete and it displays the login screen, Wine error dialogs popped up and there was no Login button. However in Settings (Gear icon) I was able to turn of Browser acceleration. It will prompt to restart.
8. Instead of launching Battle.net normally, I launched it like this (I used build32 as x32 build dir and wine-src as Wine git source dir, yours may vary; I ran this command from one folder above):

./wine-src/wine ./build32/programs/winedbg/i386-windows/winedbg.exe ~/.wine/drive_c/Program\ Files\ \(x86\)/Battle.net/Battle.net.exe

9. It launched without any Wine error dialogs. However the Login button did not appear. Despite of that, after entering email and password, pressing enter while the password field was still in focussed triggered to login. I was able to login and initiate download of StarCraft without issues. The Battle.net app seemed to work fine.

Just in case I'm not the only one encountering this: I tested 9.2 this morning and endup rolling back to 9.1 for now.
I had "strange" camera movements (camera going back to the PoV from a second before very regularly), and it **seems** happening with 9.2 only.

So Wine 9.2 and 9.1 works with the battle.net launcher?

Nothing changed in this regards to my knowledge: you still have to use Battle.net.14494 or apply the patch listed here bugs.winehq.org/show_bug.cgi?id=29384#c56 (I did not test it myself)

Sorry for bad post: this was intended for World of Warcraft, and I somehow used wrong app

The workaround remains. Delete:
Delete /[WINPREFIX]/drive_c/Program Files (x86)/Battle.net/Battle.net.145x/

That's all Battle.net subfolders numbered greater than Battle.net.14494. This folder works all updates after this do not.

This assumes there's other previous versions for it to fall back on... which I do not have. Not really a work-around.

Very good point sorry mate.

www.dropbox.com/scl/fo/ck1bazqr10x9bq61dj7np/h?rlkey=x80ekfjjf28g5ac8zrj38366q&dl=0

Has anyone tried it?

Still broken.

Even though the Battle.net client is still broken as-is today, it's usable enough to patch WoW, and WoW can be logged into without the Bnet client!

I was playing for a few days now on Fedora 39 with just logging in with email/pass, but earlier today I got Incompatible realms and needed to patch. I installed the Bnet client to my prefix, and at the log-in, used the Settings gear to continue without log-in. WoW was automatically detected. I then right-clicked the Bnet icon in the Wine System Tray and selected Resume Updates. Downloading happened, I eventually got a Bnet notification that WoW was playable, and then I launched WoW and signed-in no problem!

I've only tried WoW but it seems possible to try with any game that doesn't need Battle.net log-in (Diablo 3 I think does email/pass). The Bnet client's main page doesn't render, but Settings from the tray icon renders fine.

The issue seems to be the Chromium web browser component of the Battle.net window crashing. Battle.net will actually still update installed games and I could still run World of Warcraft by right clicking the Battle.net icon in the system tray.

I got Battle.net working correctly with wine-staging-9.0-rc3 by building Wine with the chromium issues hack from bugs.winehq.org/show_bug.cgi?id=29384#c56

Temporary workaround is as our friend b0nt4kun suggests below:

Delete /[WINPREFIX]/drive_c/Program Files (x86)/Battle.net/Battle.net.14542/

I updated WoW and moved on. Hopefully one of our Wine Dev buddies will resolve the underlying cause soon.

Easier is to just rename the last working version of bnet to the new one.
You get a pop-up about a newer version being available, and to check your shortcuts.
Pop-up has big button "continue with newer version" which then launches the old (I think?) bnet.

I took a look at what was actually running once battle.net was up, it appears to be a mix of new and old.

Yesterday's update broke battle.net on wine (8.20 for myself). Some people found a workaround by setting an environment variable WINE_SIMULATE_WRITECOPY=1
us.forums.blizzard.com/en/blizzard/t/latest-update-breaks-battlenet-launcher-on-linux/48424/20
In my case this sadly not to work, as a short term solution I deleted my Battle.net.14542 (I still had Battle.net.14494) which allowed me to have it display something after logon.
It seems to be a display issue, since even with Battle.net.14542 dark screen, the system tray icon allows to access parameters, and games seems to still update automatically (there is a also new vulkan-1.dll in Battle.net.14542 folder which convince me further it's related to display)

I can confirm Battle.net.14542 update breakage. On Arch Linux with wine-8.21-2 it causes "Program Error": "The program Battle.net.exe has encountered a serious problem and needs to close. We are sorry for inconvenience."
Looks like WINE_SIMULATE_WRITECOPY is not a Wine option but Proton, so it wouldn't work with vanilla Wine.

Bug confirmed here in both wine-staging 8.14~bookworm-1 and 8.21~bookworm-1 from winehq. The "WINE_SIMULATE_WRITECOPY=1" environment variable fix doesn't help, maybe that's a Proton thing? Deleting the "Battle.net.14542" directory did work for me, twice in a row in fact, but who knows for how long that'll keep working...

It's always been flaky. Now I can't get a new install working.

The app installs into a fresh prefix and fails to start with the QT error. setfattr -x user.DOSATTRIB qwindows.dll fixes that. Then the login box will appear, you have to press enter after typing in your password because there is no Log in button displayed. Installing corefonts (with winetricks) fixes this.The app will not display correctly after launching unless set to XP or Vista. The app will not install World of Warcraft as these OS are no longer supported. Deep joy. Tried installing VCRUN2015 with winetricks. No improvement.

An old install with display with Windows 10 or above set, however it doesn't install either. It says Initialising, counts up...populates the Warcraft folder with: two sub folders; Data and _retail_; World of Warcraft Launcher.exe; .product.db; Launcher.db. Then switches to Updating, with Initialising below and not a damn thing goes into _retail_ where the retail game should install...

...Turn off Use browser hardware acceleration when available in the Settings | Advanced in the login box.

I have been seeing the symptoms where the Agent (build 8151) would become unresponsive and close and I would see the error �Build marked non-playable for agent: Permissions check failure (2123)� in the Agent logs during the Battle.net installer process. The work-around that I found was as follows:

- Wait until the Battle.net installer has failed to launch the Agent and quits with an error code.
- In the new WINE environment that was created for the install, open the WINE Control Panel.
- Open Add/Remove Programs.
- Click the �Install� button and select the Battle.net installer EXE.
- The installation should complete normally, successfully installing Battle.net

I can not explain why this worked for me. it may have somethinig to do with the permissions that the installer is launched with from this dialog. I tried many other suggested work-arounds and stumbled across this one on my own. Hope it works for others who find this thread!

This worked thanks. Was going crazy with the installer not working on my laptop, despite working fine on my desktop.

With wine-8.0: after installed Battle.net application, fixed issue with user.DOSATTRIB and installed Starcraft Remastered it can't update and run Starcraft.
Update stuck at 0% or in paused state . Attempt to resume or pressing "Update" button manually leads to "Whoops! Looks like something broke. Give it another shot. More help: BLZBNTAGT00000BB8". Probably because of another instance of StarCraft.exe already running after first attempt.
Suspicious messages in Agent-20230204T021039.log:

[I 2023-02-04 02:10:40.0019] Network Connection Response to eu.patch.battle.net:1119/agent - CURL error: 0, Status Code: 404
...
[W 2023-02-04 02:10:40.0144] Build marked non-playable for s1: Permissions check failure (2123)
...
[W 2023-02-04 02:10:49.0184] Failed to create registry key - HKEY_LOCAL_MACHINE\Software\RegisteredApplications

In AgentNGDP-20230204T021039.log:

[W 2023-02-04 02:11:35.0160] - Files found in EM that aren't in DLM: 3
[I 2023-02-04 02:11:35.0164] - garbage collection, final container state - spans allocated: 14871 - spans free: 0 - bytes allocated: 5752356142 - bytes available: 269125550746 - bytes capacity: 274877906944
[E 2023-02-04 02:11:35.0189] - failed to bind shared memory file 'C:/Program Files (x86)/StarCraft/Data/data/shmem': SHMEM_EXISTS
[E 2023-02-04 02:11:35.0190] - failed to bind shared memory file 'C:/Program Files (x86)/StarCraft/Data/data/shmem': SHMEM_EXISTS
[E 2023-02-04 02:11:35.0191] - failed to bind shared memory file 'C:/Program Files (x86)/StarCraft/Data/data/shmem': SHMEM_EXISTS
[E 2023-02-04 02:11:35.0191] - Failed to mount container index at 'C:/Program Files (x86)/StarCraft/Data/data': CCE_SHARED_MEMORY_BIND_FAILURE
[E 2023-02-04 02:11:35.0191] CASC Compaction failure

I also tried to copy Agent.exe from Agent.7984. It either overwrites old binary with new one on first run or complain about unability to update agent when modification blocked with `chattr +i`.

Navigate to the "Battle.net" folder, then run the following command

find -exec setfattr -x user.DOSATTRIB {} \;


It recursively changes an attribute of the files so that the battle.net launcher can locate them.

The latest update to battle.net has broken the functionality through wine. On my installation (through Lutris), I was able to start a game of Starcraft 2 before the game crashed 30 seconds in or so. I tried reinstalling battle.net through Lutris and, while I was able to reinstall it (even though the installer hangs, exiting the installer would leave me with a functioning application), battle.net would not install Starcraft 2 after this. See us.forums.blizzard.com/en/blizzard/t/last-update-completely-breaks-wine-compatibility/33122 for more information.

It's caused by the new Agent.8009/Agent.exe

See here for workaround:
bugs.winehq.org/show_bug.cgi?id=53697
www.reddit.com/r/linux_gaming/comments/xgb5fx/problems_with_battlenet_today/

This issue was recently fixed by a patch pushed out by Blizzard.

For the past 3 months or so crashes have become more frequent in both battle.net and WoW. It will take several attempts to actually launch battle.net, with many either showing no result or will put a battle.net icon in the task bar that is uninteractable.

Downloading games takes much longer than should be required, sometimes with the application spinning endlessly and never installing a game. Wrath of the Lich King Classic in particular had to be "installed" 3 times for it to actually work.

WoW itself will crash quite frequently, with the game locked up but the cursor and rest of the machine responsive. Killing the WoW.exe process is required to continue to use the computer. This behavior isn't reproduced with any specific event and occurs in retail and classic using both nvidia and amd cards. It's likely that a recent patch by Blizzard has caused this behavior, but it's become quite frustrating.

It seems that on a new install launching battle.net happens without problem, but the more you use it the more the odd behavior appears. I'm using the most recent Lutris install script, using pretty much any other runner makes the issue much worse.

Failed to get more then 50% through installer.

Test results have been posted, will be above soon. Any suggests for troubleshooting / fixes?

Many thanks, guys.

Works here with Wine Staging 7.13 on Arch Linux; Battle.net installs without any issues in a clean prefix.
The logs that you posted are just "fixme"s, they're probably not directly related to the issue. Try to see if there are any "err" logs before that.

I will Maciej, I didn't double check what I posted into the test results, I didn't realise they were all fixme's I was going in circles for so long I've picked the wrong bit of code. I'll try a fresh prefix tonight after work and update here.

Many thanks the the response.

I spent a couple of hours last night trying to debug. It wasn't illuminating.

This was the only error I've had:
ERROR:dxva_video_decode_accelerator_win.cc(1320)] DXVAVDA fatal error: Could not load msmpeg2vdec.dll: Module not found. (0x7E)

Now it got silly. I installed libasound2-plugins:i386, libsdl2-2.0-0:i386, libdbus-1-3:i386, libsqlite3-0:i386 and this fixed the crashing and Blizzard Report dialog problem. I now have a log in box (with a graphical corruption hiding the login button). So I removed these four components, so I could install them individual to test if one of them fixed the issue rather than all four. This took Wine out too! I reinstalled Wine, again, and I was back to a login box (with a graphical corruption)...still unable to log in. The fix is surely disabling Browser Hardware Acceleration, sadly before I did that I tried reinstalling those four components: libasound2-plugins:i386 was already, I reinstalled libsdl2-2.0-0:i386 then I remembered to enter Settings and disable Browser Hardware Acceleration...I am currently re-installing World of Warcraft.

I will rip out wine and all these extras at some point, reinstall Wine and test. If I have the original issue, I will test which component above actually fixes it and post new Test Results with my workarounds. Thanks Maciej. I suggest deleting my Garbage Test Results.

> I suggest deleting my Garbage Test Results.
Done.

I'm not knowledgeable about running Wine on Debian-based distributions, but looking at Lutris' dependency list, it does indeed suggest those 4 packages you installed are required:
github.com/lutris/docs/blob/master/WineDependencies.md

On my Arch system I only have 32-bit versions of sdl2 and dbus installed (both pulled as dependencies of wine-staging package). I don't have alsa-lib (which I think is analogous to libasound2) or sqlite.

If you figure out exactly which packages are needed to be present (on top of those pulled as wine dependencies), I can update the HowTo note with this information.

Last Wednesday (or around that day) WoW received an update which was mandatory to play the game. Pressed the update button but it wouldn't update. After a few unsuccessful attempts I decided to reinstall Battle.net and also cleared the application data. However, the reinstalled application can't find any games. If I press �Scan for Games� in Settings->Downloads, it prompts immediately that it can't find any. When I browse the folders manually through the Locate option, the message �The selection contains a non-folder object� appears. I've looked for solution through Google but none of the ones I found had any workable solutions.

Is anybody else been experiencing this lately? (Wine 6.20 for Impish is installed)

This one has come around again, this time on winehq-staging 6.12 the latest release on Debian Buster.

Currently known workarounds:

Try killing Agent.exe process; it will be restarted automatically and there is a chance that installation will proceed.
If that doesn't work:
Close Battle.net App (make sure that wineprefix is closed completely, e.g. by running "wineserver -k")
Delete "C:\ProgramData\Battle.net\Agent\product.db" file
Relaunch Battle.net App

I tried this old gold but App returns the original error before you get to Scan for Games through settings.

The above will remove Agent.exe's game installation info, so you will then have to go to Settings -> Game Install/Update and click Scan for Games to have it repopulated.

I see the bug for this issue: Bug 51331 is marked as resolved. Will that patch be part of 6.13?

This time it was a regression in Wine, so previous workarounds did not help.
Fix was introduced to Wine code after 6.12, so it's included in 6.13 (I just verified that on Staging 6.13 Battle.net App works normally).

Thank you mate. Good to know.

Still doesn't work well for me in any version later than 6.11 (6.12/6.13/6.14). First, it now takes about 5 minutes, until I even see the main window. After it opens, I see spinning blizzard logo for some time and then a message "something went wrong. We're having difficulty retrieving content from our servers. Please try again with button below". After several attempts to reload, it finally shows the content.

Sounds like a separate issue. Have you checked with a clean prefix?

?Tried with clear prefix. In fact, I couldn't install it with wine 6.14. After launching installer, language selection came up. After selecting English, it was stuck more than 10 minutes on "Updating Battle net update Agent". Tried again with wine 6.11 - whole installation took less than 1 minute. After I got it installed, also tried to run it with wine 6.14. It takes more than 5 minutes, until window shows up, and it is unable to load any content, and does not let to press any button. With 6.11 - window comes up in few seconds and works fine.
BTW, using Fedora 33 with Mate desktop, winehq-staging from WineHQ Fedora repos.

I would submit a new bug report, then.

When I try to run battle net app, it fails with a message that says QT windows is missing, try reinstalling the application. Anyone know how to fix this?

Hello.
I have:
Linux Mint 19.2 MATE x64
NVidia Drivers 455.45.01 (GeForce GTX 1050 Ti) - installed
Wine 5.0.3 - installed
PlayOnLinux 4.3.4 - installed (have error "PlayOnLinux is unable to find 32bits OpenGL libraries")
Winetricks - installed
Battle.net have error BLZBNTBTS0000005C under wine 5.2.0-staging (or system or 5.2.0 or 3.2.0...)

eu.battle.net/support/ru/article/19031 - did not help

Can someone help me to solve this problem?
Regards, Alexey.

After installing another version of the driver NVidia Drivers 450.80.02, everything works fine.
Regards, Alexey.

The latest update of battle.net is not fully working by default, at least on 5.20 and 5.22 on my side, everything works but you are not seeing the "content" of the game page so can't per example update your game.
An easy fix is to go to the settings of the app and in the general tab uncheck "Use browser hardware acceleration when available", the settings page is displaying correctly.
The app will then restart and be fully available.

Somewhere between 5.10 (works fine) and 5.14 (does not) battle-net stopped working for me: it always ended in a "We're having trouble launching the Blizzard Update Agent. Please wait one minute and try again. ... BLZBNTBTS0000005C" error message. Terminal output shows a bunch of fixmes and "0154:err:ntdll:RtlpWaitForCriticalSection section 01069DFC "?" wait timed out in thread 0154, blocked by 0150, retrying (60 sec)"
Not a big deal so far, since I could just use wow-staging-5.8 and 5.10.
But with the WoW Shadowlands prepatch WoW crashes with these wine-staging versions. I found some users report 5.18 and 5.19 work for them.
So I tried again and just as before: battle.net will not start, it'll sort of time out and after a minute the afore mentioned error pops up.
The funny thing is: Since some of the reports of "WoW SL pre-patch works with 5.19" I found were on the lutris site, I dowloaded lutris and had lutris install battle.net and wow again and lo and behold: That works.
But: I don't like using lutris, I much rather take care of my prefix myself. So I'd like to get my prefix to work with 5.19 too. Looking at the lutris install files for WoW and Battle.net nothing really strikes me as: Now that's keeping battle.net agent from being able to connect/launch!
That being said I tried the following: I
- changed my prefix from Win7 to Win10 (lutris has it set to Win10)
- used winetricks winhttp and wininet
- manually added all the dll-overrides lutris sets
- added the string "backend" with value "va" to the key HKEY_CURRENT_USER\Software\Wine\DXVA2 (taken from the lutris script)
- vimdiffed $GAMEDIR/drive_c/users/$USER/Application Data/Battle.net/Battle.net.config with mine and applied the changes to mine.

After each step I used wineboot -r in my prefix and tried to run the battle.net client. And it still doesn't work.

Wtf is Lutris doing differently?

There are two bugs that come to my mind:
bugs.winehq.org/show_bug.cgi?id=49590
bugs.winehq.org/show_bug.cgi?id=49712
but the first one was introduced in 5.13 and fixed in 5.14, and the second one introduced in 5.15 and fixed in 5.16 � so 5.14 should not be impacted by any of those.

Are you using Staging 5.19? There are some Staging patches that are required for Blizzard games to work, maybe they also impact Battle.net app.
Also, do you have a PE build of Wine? Lately a lot of Wine libraries were converted to PE format, and using a non-PE build will break a lot of games: bugs.winehq.org/show_bug.cgi?id=45349

After upgrading from wine 5.4 to wine 5.19 (staging) Battle.net was crashing in my case too.

Creating a fresh wine prefix for it worked immediately with only wine 5.19 and staging patches (no winetricks), but build with PE support (requires mingw crossdev compiler)

Up until now I was using Wine Staging 4.3 with dxvk-1.3.4 in order to run Battle.net and all Blizzard games, like Warcraft.

Since patch 8.3 in WoW i had random freezes during the game. These freezes were so severe that i had to restart my PC, making the game unplayable. So I decided to make a new installation on PlayOnLinux and use the latest versions of Wine and dxvk (5.2 and 1.5.5 respectively).

Battle.net applications starts, i make the login but I have a black screen and an erron message that the application couldn't establish a graphic enviroment, prompting me to either exit or restart Battle.net. I remembered the same problem last winter with the white screen and i made the overides on api-ms-win-crt-private-l1-0-0 and ucrtbase but the problem persists. WoW works fine and without freezes with WineStaging 5.2, but without a working version of Battle.net I can't update the game.

So I decided to use the my previous drive with Wine Staging 4.3 to start Battle.net and use the WineStaging 5.2 to run WoW. But to my surprise the black screen migrated there also. Battle.net starts with Wine Staging 4.3 but the black screen follows.

I use a common folder with all the applications (Battle.net, WoW, Hearthstone) so that I don't "install" the games all the tine.

Any thoughts?

When I open the app the window is invisible, I believe things are clickable but I can't see anything

imgur.com/a/yfexiA3

MacBook Pro 15 (2019) 2.6 Ghz w Radeon Pro 555x

I'm also on Staging 4.17. If someone could help that would be greatly appreciated.

Have you tried workarounds for the "white screen after login" issue?

I added the libraries to Battle.net.exe and then it crashed after login.

It actually only crashed once but after adding the libraries nothing changes

After the upgrade to Battle.net.11537 I was getting a white screen after logging in. Found a workaround at forums.lutris.net/t/issues-starting-battle-net-on-pop-os-after-update/7228/26

TLDR, add api-ms-win-crt-private-l1-1-0 and ucrtbase to the winecfg Libraries list as native first.

Thank you very much for posting the fix here this fast.

In my case only ucrtbase was needed. Anyway, thanks a lot for the fix!

Same for me, overriding just ucrtbase fixes the problem.
I've added this info to Troubleshooting Notes.

I'm currently on Wine Staging 4.21 + Battle.net 1.18.0.11698, and I removed the ucrtbase override from Battle.net.exe.
For now everything works � the white screen problem seems to have been fixed, either on Wine/Staging or Battle.net part.

Wine staging 4.12 results in a black window for battle.net. A work around, at least for me, is to use 4.7 as it does not have this issue.

I use Playonlinux for a wine front end. I had wine 4.7 installed, but it looks like 4.11 and before dont have the black battlenet window issue.

Another possible workaround is to use DXVK as mentioned in [1]. That works around the issue for me and makes it possible to use Wine 4.12.1.

[1] www.reddit.com/r/wine_gaming/comments/chizv8/battlenet_black_screen_help/

Wine staging 4.13 fixed that problem for me.

Someone else reported this here first:
www.reddit.com/r/linux_gaming/comments/acb4vm/battlenet_crashes_with_wine40rc4_staging_and/

Happens to me too.

Without DXVK, Battle.net runs.
After installing DXVK (either through Lutris or manually), Battle.net crashes immediatelly after login :(

Kubuntu 18.10, Nvidia 410, wine-4.0-rc4.

Works fine here – Arch Linux, wine-4.0-rc4 (Staging), both with NVIDIA card (415.25) and with AMD one (kernel 4.20).
Are there any specific errors in the logs when it crashes?
Did it start happening recently? If so, was it after Wine update, DXVK update, or something else in the system?
Also, do you have every library installed like described in Lutris wiki[1][2]?

[1] github.com/lutris/lutris/wiki/Game:-Blizzard-App
[2] github.com/lutris/lutris/wiki/How-to:-DXVK

This looks like a problem with DXVK 0.94, as i was able to reproduce crash after updating DXVK from 0.92 to 0.94.
Downgrading DXVK to 0.92 fixes this. (arch 4.19, wine 4.0-rc3, mesa 18.3)

I did compile master branch from DXVK and it looks good. As far as i can tell this fix did the trick github.com/doitsujin/dxvk/commit/652525119f3cf7868d831fb273e6ee5daac0234c
So options are - downgrade to 0.93 and earlier, compile master version or just wait till 0.95

Create a wineprefix for battle/net without DXVK and one with for WoW etc...Simples.

I'm not able to login into battle.net "normally" when using Blizzard Mobile Authenticator and wine-development64-3.16-1.x86_64. As Authenticator asks Approve and Deny, it does not work as expected as battle.net login screen goes to asking password again. But if I select "Enter code manually" from Authenticator and then put the code into login at appropriate box, login works.

I remember this happening for me a while back (weirdly, right now it logs in correctly).
You could try synchronizing your clock on both PC and authenticator.
Another idea to try would be to wait for a bit before clicking "Approve".
If everything fails, then I guess manually entering the code is the only option left.

I'm using wine-staging 3.15 on Manjaro Linux (based on Arch). BattleNet version 10491 works perfectly fine in Wine-Staging 3.15, however whenever BattleNet updates to 10532, it breaks. It just crashes completely when it tries to launch. I don't know if it's a BattleNet bug (a couple users on the Blizzard support forums are reporting similar crashes recently) or a Wine bug. But something in the BattleNet update broke something somewhere.

I tried uninstalling BattleNet completely and reinstalling, but it still won't work. Now I'm stuck with 10532 that keeps crashing and no 10491 to fall back on.

1. What about Staging 3.14 with Battle.net 10532?
2. Can you post your installed lib32- packages? I'm on Arch and I don't have any issues with 3.15 + 10532.
3. Anything shows up in the logs when the app crashes?

I used downgrade to install Wine-Staging 3.14. BattleNet 10532 still crashes. Like I said, though, the previous version I had installed worked fine, even in Staging 3.15. Updating to the current version of BattleNet makes it crash at launch. I don't get it.

Here are my lib32- packages:

$ pacman -Qs lib32-* | grep 'lib32-'
local/lib32-acl 2.2.53-1
local/lib32-alsa-lib 1.1.6-1
local/lib32-alsa-plugins 1.1.6-1
local/lib32-atk 2.28.1-1
local/lib32-attr 2.4.48-1
local/lib32-bzip2 1.0.6-3
local/lib32-cairo 1.15.12-1
local/lib32-curl 7.61.1-1
local/lib32-db 5.3.28-4
local/lib32-dbus 1.12.8-1
local/lib32-e2fsprogs 1.44.4-1
local/lib32-expat 2.2.6-1
local/lib32-flac 1.3.2-1
local/lib32-flex 2.6.4-1
local/lib32-fontconfig 2:2.13.0+15+gc60ed9e-1
local/lib32-freetype2 2.9.1-1
local/lib32-fribidi 1.0.5-1
local/lib32-gcc-libs 8.2.1+20180831-1 (multilib-devel)
local/lib32-gdk-pixbuf2 2.36.12-1
local/lib32-gettext 0.19.8.1-1
local/lib32-glew 2.1.0-1
local/lib32-glib2 2.56.2-1
local/lib32-glibc 2.28-4
local/lib32-glu 9.0.0-4
local/lib32-gmp 6.1.2-1
local/lib32-gnutls 3.5.19-1
local/lib32-gtk2 2.24.32-1
local/lib32-harfbuzz 1.8.8-1
local/lib32-icu 62.1-1
local/lib32-intel-tbb 2018_20180618-1
local/lib32-jack 0.125.0-2
local/lib32-keyutils 1.5.11-1
local/lib32-krb5 1.16.1-1
local/lib32-lcms2 2.9-1
local/lib32-libaio 0.3.111-1
local/lib32-libasyncns 0.8+3+g68cd5af-1
local/lib32-libcanberra 0.30+2+gc0620e4-1
local/lib32-libcanberra-pulse 0.30+2+gc0620e4-1
local/lib32-libcap 2.25-1
local/lib32-libcups 2.2.7-1
local/lib32-libcurl-compat 7.61.1-1
local/lib32-libcurl-gnutls 7.61.1-1
local/lib32-libdatrie 0.2.12-1
local/lib32-libdrm 2.4.94-1
local/lib32-libelf 0.171-1
local/lib32-libffi 3.2.1-2
local/lib32-libgcrypt 1.8.3-1
local/lib32-libglvnd 1.1.0-1
local/lib32-libgpg-error 1.32-1
local/lib32-libice 1.0.9-3
local/lib32-libidn 1.33-1
local/lib32-libidn2 2.0.5-1
local/lib32-libjpeg-turbo 1.5.3-1
local/lib32-libldap 2.4.46-1
local/lib32-libltdl 2.4.6+40+g6ca5e224-4 (multilib-devel)
local/lib32-libnl 3.4.0-1
local/lib32-libogg 1.3.3-2
local/lib32-libpcap 1.9.0-1
local/lib32-libpciaccess 0.14-1
local/lib32-libpng 1.6.34-1
local/lib32-libpsl 0.20.2-1
local/lib32-libpulse 12.2-1
local/lib32-libsamplerate 0.1.9-1
local/lib32-libsm 1.2.2-2
local/lib32-libsndfile 1.0.28-1
local/lib32-libssh2 1.8.0-2
local/lib32-libtasn1 4.13-1
local/lib32-libthai 0.1.27-1
local/lib32-libtiff 4.0.9-1
local/lib32-libtxc_dxtn 1.0.1-5
local/lib32-libunistring 0.9.10-1
local/lib32-libusb 1.0.22-1
local/lib32-libvorbis 1.3.6-1
local/lib32-libx11 1.6.6-1
local/lib32-libxau 1.0.8-2
local/lib32-libxcb 1.13-1
local/lib32-libxcomposite 0.4.4-3
local/lib32-libxcursor 1.1.15-1
local/lib32-libxdamage 1.1.4-3
local/lib32-libxdmcp 1.1.2-2
local/lib32-libxext 1.3.3-2
local/lib32-libxfixes 5.0.3-1
local/lib32-libxft 2.3.2-2
local/lib32-libxi 1.7.9-1
local/lib32-libxinerama 1.1.3-2
local/lib32-libxml2 2.9.8-3
local/lib32-libxmu 1.1.2-2
local/lib32-libxrandr 1.5.1-1
local/lib32-libxrender 0.9.10-1
local/lib32-libxshmfence 1.3-1
local/lib32-libxss 1.2.2-3
local/lib32-libxt 1.1.5-2
local/lib32-libxtst 1.2.3-1
local/lib32-libxxf86vm 1.1.4-2
local/lib32-llvm-libs 6.0.1-1
local/lib32-lm_sensors 3.4.0-1
local/lib32-mesa 18.1.8-1
local/lib32-mesa-demos 8.4.0-1
local/lib32-ncurses 6.1-2
local/lib32-nettle 3.4-1
local/lib32-nvidia-cg-toolkit 3.1-5
local/lib32-nvidia-utils 1:396.54-2
local/lib32-openal 1.18.2-1
local/lib32-openssl 1:1.1.0.i-1
local/lib32-openssl-1.0 1.0.2.p-1
local/lib32-p11-kit 0.23.14-1
local/lib32-pango 1.42.4-1
local/lib32-pcre 8.42-1
local/lib32-pixman 0.34.0-1
local/lib32-portaudio 190600_20161030-1
local/lib32-readline 7.0.003-1
local/lib32-sdl2 2.0.8-9
local/lib32-soundtouch 2.0.0-1
local/lib32-sqlite 3.24.0-1
local/lib32-systemd 239.2-1
local/lib32-tdb 1.3.15-2
local/lib32-util-linux 2.32.1-1
local/lib32-wayland 1.16.0-1
local/lib32-wxgtk2 3.0.4-1
local/lib32-xz 5.2.4-1
local/lib32-zlib 1.2.11-1

As for logs, I'm not sure where to check for the logs.

I managed to get it working.

I had used winetricks to install dxvk in order to play Overwatch. I found out in the prior version that I had to set Agent.exe to use the builtin dxgi instead of native, but apparently in the current version of BattleNet I have to set the Battle.Net Launcher and Battle.Net.exe to use builtin dxgi, as well.

This looks similarly to the problem that user spaceman is experiencing (in the comments below). However since you use Arch you should have newest drivers, so the hypothesis about outdated packages is invalid.
Can you try installing and running the app in a clean wineprefix with no DLL overrides? Or just removing all DXGI overrides in your current prefix – what will be the result?

I think Overwatch needs the native dxgi override, so I just set Agent.exe, Battle.Net Launcher.exe, and Battle.Net.exe to have a dxgi builtin override. I know I could probably set it so Overwatch.exe has the native overrides and the other executables just have the default settings, but that's not how I ended up having it set.

But Battle.Net runs fine with this setup, as does Overwatch (or at least as good as Overwatch works in Wine so far). I may even try HotS next.

Recently the app keeps getting stick at the above message when launching. If you have the same issue please see this report: bugs.winehq.org/show_bug.cgi?id=45814

Ubuntu 18.04. Update manager updated my wine from 3.14 to 3.15.

Now Battle.net no longer starts, it just crashes. Hearthstone no longer starts because it attempts to start battle.net which is then crashes so it exits...

I deleted my ~/.wine and attempted to reinstall battle.net now fails to connect to the update agent. Internet searches are useless, because everyone else in the world uses Windows and it doesn't apply to wine. And it seems it works for everyone else in this thread, except me in the entire world.

Same distro and versions, maybe this is related?
bugs.winehq.org/show_bug.cgi?id=45764
(There are also a couple of comments below by the submitter of this bug.)

Actually I can't find the comments now… I must have mixed something up.

I use kubuntu and battle.net also did not start for me anymore after I upgraded from wine staging 3.13 to 3.15.

I reverted the upgrade and now battle.net starts again. I more or less the following command to revert the upgrade:
sudo apt-get install wine-devel-amd64=3.13.0~xenial wine-staging-amd64=3.13.0~xenial winehq-staging=3.13.0~xenial wine-staging=3.13.0~xenial wine-staging-i386=3.13.0~xenial

I didn't had to do anything else to get it working.

One thing I found is, when attempting to star StarCraft II through the Battle.net launcher, is it was trying to create a directory that it didn't have permission to create, but looked like some of the hex for "Ba" was incorrect, as it had < and then some other character that couldn't be read. Downgrading to 3.14 works for the time being.

After multiple comments it's now pretty clear that this behavior only appears on Ubuntu (and derivatives). It could be caused by some errors during build, or maybe library version incompatibility.
Could someone using Ubuntu try compiling Wine and do a regression bisection of commits between 3.14 and 3.15? wiki.winehq.org/Regression_Testing

Can anyone having this problem try what the submitter described in bug #45764 (calling the launcher with WINEDEBUG=+relay,+msgbox)?
If it doesn't help, the bug should probably be reopened.
bugs.winehq.org/show_bug.cgi?id=45764

The Blizzard App has never been particularly robust with Wine, however the current version is by far the flakiest. I know it has issues on Windows 10 (I can experience them myself in a VM if I need to), but our experience is very poor. For my own part I have to delete ~/.bnet/drive_c/ProgramData/Battle.net/Agent/product.db *every other time* I start the client just to complete an update. If I don't do this the App will wait indefinitely to complete "another update"...so I delete the product.db file | Locate the game | and then the Update button will appear *and* work.

I only use the Blizzard App to install updates, so I am very impressed with someone else's suggestion that "most people still log in through Battle.net App." I never actually use the App to launch a game because Battle.net doesn't run with dxvk (for me) so I run it in its own prefix so game performance would be awful if I did launch games. I suspect I am not alone. I have written a script to "repair" the App and killall the Battle.net / agent.exe processes, then delete product.db, however given how badly the app works I might save myself a lot of wasted time and incorporate it into a startup script that deletes the product.db before each start up, then I only have to locate the game folder and update.

I will submit Staging 3.15 test results to detail my setup so welcome suggestions and feedback. Thanks all.

> I am very impressed with someone else's suggestion that "most people still log in through Battle.net App."
But isn't it true? It's still easier to launch games from the app instead of from specific game launchers, and for some games (Hearthstone) this is the only way to run them.
I just delete product.db when I need to update, and use the app normally (fwiw) all the other time.

> Battle.net doesn't run with dxvk (for me)
In the test result you list Nvidia driver 396.24 – this version is missing quite a lot of Vulkan-related stuff. You should try updating to at least 396.45.
For example, I remember 64-bit Diablo III with DXVK didn't launch at all on 396.24 – it started working only after update to 396.45. Currently I'm on version 396.54 (on GTX 1060, so similar to yours), and I have no problems running Battle.net with DXVK, in the same wineprefix as all other Battle.net games.

(Also, it should be possible to override DXVK DLLs to "builtin" just for Battle.net app – then all games would use DXVK, but the app would not.)

All top tips, however the App also takes an age to load and it's well know it doesn't shutdown cleanly, leaving Battle.net.exe and Agent.exe running in the background. For HotS and WoW it's easier and cleaner to run the executables direct. Since I'm creating an Xfce4 launcher for Battle.net why not just create two - one for WoW one for HotS and avoid the App when I can?

I shall try your other suggestions and report back. Very many thanks.

Yeah, understandable. It's just weird to me that I'm not experiencing those issues:

> takes an age to load
For me it's 8 s from clicking the icon to fully loaded app; but I remember seeing someone else having this problem.

> doesn't shutdown cleanly
I'm seeing this, but quite rarely, and only after the update problem occurs (e.g. when I click "Check for updates" and it spins forever). In all other cases it exits cleanly (although – by design – it takes a couple of seconds for Agent.exe to shutdown).
This was happening always in Wine Staging 2.19, but starting from 3.3 it stopped occuring for me (see bug #44024, this was also confirmed by submitter to no longer occur).

Maybe those problems are distro / library version / configuration dependent? There has to be a reason for such vastly different behavior… but I guess debugging it would require quite a lot of effort.
Still, I think we should include information about (at least) distro used when describing issues we experience. Maybe we could then find a common denominator for some of the issues.

I absolutely agree, I understand that my experience my not be universal. I actually prefer to use antiX Linux Core 17 Heather Heyer, based on the Debian Testing. I lost all of yesterday trying to upgrade my Nvidia drivers (and managing to work my way around trashing six distros in an effort to upgrade one).

Today I've managed to sort my stupidity out and built antiX on a Debian Stable base with the 396.54 driver set...if I ever get Wine working again (dependency problems!) I can test Battle.net...with and without dxvk, which I simply couldn't get working on Fedora 28 for love nor money. In frustration I turned to Ubuntu, as with it's huge software repo, Windows-like weight and approach, vast community and endless wordpress guides, I thought that I should be able to get something working...I impressed myself trashing a Xubuntu 17:10 install so soundly.

AntiX Core is a minimal distro (there is no X at install) which I love because I can then build up packages on a *need only* basis. The obvious problem with this approach is not always being able to establish which packages are needed in any case. This should be easier but, of course, this is the real world.

With wine 3.15, I've managed to install the Blizzard app just fine, but I can't for the life of me log in - I always get the messed up "please reenable cookies" webpage. I've tried with 32- and 64-bit, and all sorts of Windows versions including Windows 7, Windows 10 and XP. If I try to install IE8, I get a message that there's already a newer version of Internet Explorer installed.

It seems everyone else is just logging in via some game? This doesn't seem to be an option for Hearthstone, so which game would I need to install to log in?

> It seems everyone else is just logging in via some game?
Logging in directly through games is possible for some of them, but most people still log in through Battle.net App.
Have you tried Staging 3.14/3.15? Do you have lib32-libldap and lib32-gnutls installed?

I have libldap-2.4-2:i386 2.4.46+dfsg-5 and libgnutls30:i386 3.5.19-1 installed. I use PlayOnLinux to manage my wine versions and prefixes and unfortunately they don't have newer staging builds anymore.

Had the same problem "solved" it by linking my bnet account to my google account and logged me in with that one

Hey, I found something that took me in the right direction towards getting this to work on Debian. I was getting the error that caused battle.net to close upon login saying it couldn't create a graphic context, so I installed this meta package (in 32bit, haven't tested 64bit): packages.debian.org/sid/libgl1-nvidia-glvnd-glx
and this seems to have got me past the black screen. I'm still getting errors as it stands right now, but so far I'm going to assume these are different errors as there are actual graphics now. Hope this helps people.

Sorry, I should also add that I'm (obviously) using an Nvidia card, along with the proprietary Nvidia driver. Haven't tested the open source driver at all yet.

Anyone else having problems running battle.net (or Battle.net Launcher.exe) with wine-staging-3.15?

Wine-staging-3.14 works like it use to, but 3.15 crashes with a nasty segfault for some reason.

No problems here, Battle.net runs the same on Staging 3.14 and 3.15.

Hmm.. Using default wine-3.15 (not staging) from the PoL repo, i get the error message mentioned in this page:
us.battle.net/support/en/article/18771

The two recent WINE-3.15, both devel AND staging, work, but with a new fairly dramatic bug.
The clickable area of all the side buttons is now approx two buttons lower than the displayed button.
For the top row, clickable area is now a few buttons to the right.
This forces one to resize battle.net's window vertically, dragging bottom edge down until the clickable area of the START button is within the window's border.
Virtual desktop or own windows matters not, same behaviour in both.

Happily, the main World of Warcraft game window works fine.
I hope this gets fixed soon; have been considering trying a rollback to 3.14.

4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Radeon HD-5670

Either "Agent.exe v/6383" fixed it, or "Battle.net v/10491" fixed the bug with my segfault, cos after updating with wine-3.14, i tried wine-3.15 again, and it worked :)

Did not notice any button problems tho...

Installed with wine64 3.14 staging, had the problem, none of the stated workarounds helped. What helped, however, was launching Battle.net Launcher.exe(not Battle.net.exe!) with a stable wine64, it threw a couple errors on the startup but I was able to install the game just fine. Aside from that, the app runs better all around with wine-staging. OS Kubuntu 18.04

By "stable" you mean version 3.0.2, right?

Right.
Actually, I had to reinstall the OS later that day, and now, doing exactly the same, I can't even run the app. Installed it using 3.1.4-staging, and it will refuse to run, throwing:
wine: Unhandled exception 0x40000015 in thread 30 at address 0x494f73 (thread 0030)
Any ideas?

NVM, installed IE8 and it worlked.

I dowloaded the game and all but now when I click on Play,
it gives the message Game is Running. but it doesn't start and the button returns available again

In this case try to launch Battle.net App from the terminal and see if there are any interesting logs when you click Play (please don't post all the logs here, just the ones that could signal the error, like some missing library, etc.).

There are no interesting logs, only normal lines come out in terminal.
I'am trying now to 'Scan and Repair' starcraft. Will report when possible.

I noticed that StarCraft.exe is running and consumes cpu but the window is not visible.
So it does start the program but window doesn't show up.

Are you now using vanilla or Staging Wine? I believe Staging is required to run Starcraft.
You can find more information on Starcraft's page: appdb.winehq.org/objectManager.php?sClass=version&iId=35645

That was my problem.
I had development version which I thought was the same as Staging but it is not.

The next problem was that I couldn't create a character because I didnt't have permission
to write in Starcraft directory.
SOLVED: indeed My Documents/StarCraft directory needed root permission, had to change permissions.

Now it is correctly working

I can manage to login to battle net but than when it opens the app it shows the side menu with games and when you click on it you can't see any info, nor buttons, just 2 little white boxes.

Anyone else with this problem?

I have installed dlls:
atl80
msvcm80
msvcp80
msvcr80
vcomp
api-ms-win-crt-heap-l1-1-0
api-ms-win-crt-locale-l1-1-0
api-ms-win-crt-runtime-l1-1-0
api-ms-win-crt-stdio-l1-1-0
d3d11
ucrtbase
vcruntime140

What version of Wine are you using?
I remember I've seen those 2 white boxes a long time ago on vanilla Wine. New versions, both vanilla and Staging, should work without major issues.
Also, all of those DLL overrides should not be required anymore.

I have wine-3.0.2, just installed yesterday. Should be the staging version

3.0.2 is from the stable branch and it doesn't contain multiple commits that made Battle.net work. Try the development branch, versions 3.12 or newer.

oh, you're right.
Thank you very much, indeed now I can see buttons and everything.

Now my new problem is that I'am stuck on the Installation window.
I clicked on 'Play Now' for Starcraft, it opened the installation window,
which simply has a loading logo which keeps spinning.

That's another problem that appeared lately after some Battle.net update. Try this: close BN completely (wineserver -k to make sure), delete "C:\ProgramData\Battle.net\Agent\product.db", and then start BN again.

It worked perfectly.
Thank you very much, again!

Actually I thought it was working,
but in reality it is stuck saying "Waiting..." after I said to download the game.

I waited a lot of time but it's still stuck

it started working now, sorry, can delete reply

I won't delete it, because it's actually useful information – that the issue comes and goes away randomly. It can be valuable for other people experiencing this problem.

My story here to remind me later if that happens again:
I use PlayOnLinux frontend.
In mid-July, I logged out of BlizzardApp and I was not able to log in again.
No big deal, I login via SC2 itself.
Up until version 4.5 of SC2, on August 8th.
SC2 needs an update and tells me to update it from BlizzardApp, where I was never able to log in.
I wasn't able to install corefonts. Or I don't see arial in the registry editor.

Out of despair I create a new prefix and install new BlizzardApp. No login yet.
Somehow I decided to point the new installation the data folder of SC2, the one with 28Gb of data.
And I see "Initializing" progress bar.
After some 20 minutes or thereabouts, I see the play button and a text that the version is now 4.5.
So pointing the client to a data folder forces it to update the game, even without logging in.

Now I can play SC2 again!

Hope that helps someone. Don't hesitate to drop a simple "thanks" line here.

Have installed Wine 3.13 and Battle Net setup runs fine. When launching Battle.Net client I receive the usual system survey and battlenet helper errors but I can't click on the gear (for settings) or anything else such as the change region.

Clean new WinePrefix with WINEARCH=win32.

Installed corefonts, ie8 and VC2015. No DLL overrides installed.

Updated the Battlenet config file to disable hardware acceleration but still no dice. Not sure what else to try.

Do you have Login button visible / can you login to your account?
Regarding clicking buttons, please see bug #33943; try to move your mouse down after you click, the menu should show up then.
Also make sure to set Windows version to Win 7, as installing ie8 will set it back to Win XP.

Please delete my other comment, it seems I didn't wait long enough on the region select screen (previously I was just clicking continue and not realising it was asking me to select a region). Once I waited and selected the region select (the first popup that isn't an error), then the fields and buttons were all available.

Hope this helps someone! :)

Glad it worked out in the end, happy playing!

Lately there have been problems with installing games. When clicking the Install button the installation window will show up with a spinning icon, and Start Install button will forever stay unclickable.
This can mostly be mitigated by killing Agent.exe while installation window is shown, but it doesn't seem to always work [1].
Another option is removing "C:\ProgramData\Battle.net" directory before launching Battle.net App – but this is also not permanent (the problem will reappear after restarting the app).

[1] www.reddit.com/r/wine_gaming/comments/92l58n/problems_installing_wow_with_lutris/e37aizw/

The issue also appears with updating games. Available updates are not detected automatically, and when doing it manually they hang at "Checking for updates" or "Waiting".

Regarding above workaround with deleting files: the problematic file seems to be "C:\ProgramData\Battle.net\Agent\product.db", which contains information about installed games. Moving/deleting the file makes the issue go away temporarily.
As a side effect of removing this file, information about installed games is lost. One needs to go into Settings -> Game Install/Update -> Scan for Games to detect already installed games.

Same here. Killing the agent did not change a thing. A fresh install got the same results no matter which version of wine I tried.

Finally, I got the install working. Apparently, vcrun2015 installed with winecfg did the trick. In my previous fresh install trials I had chosen vcrun2017 because newer is supposed to be better...

WINEPREFIX=/home/$USER/bnet/ winetricks
→ select default wine prefix
→ install a Windows DLL or component
→ vcrun2015

Please note that running "winetricks vcrun2015" sets Windows version to XP, which is unsupported by Battle.net.
I don't know if installing vcrun2015 and then setting the version back to Win 7 fixes the install/update issue, since it comes and goes away randomly for me.

It does not fix the issue for me. I installed vcrun2015, put the version back to Win7, tried to install a game, and I only have an unclickable "start install" button with a spinning logo.

First of, I am using wine64-development from current Debian testing/buster. This puts wine at version 3.13 . But apparently I sometimes seem unable to install too. So it looks like something else is going on. Maybe, my successful run with VCR2015 was just a lucky coincidence.

There is a hint by Maciej Stanczew two sections above:
* close BN completely (wineserver -k to make sure), delete "C:\ProgramData\Battle.net\Agent\product.db", and then start BN again.

From what I have seen on two machines, the issue appears randomly and is hard to know what is causing it. So this vcrun2015 thing could have been a lucky coincidence.
I'm trying to see any patterns here, but for now it seems that sometimes Agent.exe just "decides" to break, and that it's somehow connected to product.db (which contains information about installed games, their versions, and more).

I have added a note explaining known workarounds for this issue. As mentioned there, if anyone stumbles upon some new information related to this problem, please make a comment here.

Also one interesting thing is that I think I saw the problem on Windows when I launched BN there about a week ago. But after removing product.db once, the issue went away, and didn't return that day. I had no way to check it since then, so I can't really confirm this.

I've had issues updating the game as well, for +- the last 4 or 5 weeks. been using wine-staging 3.12 and 3.14. Battle.net would just indefinitely say "checking for updates" and nothing happens.

The workaround as described (delete product.db, then scan) works. Immediately after scanning the update was downloaded and checking for updates works again as well. Thanks!

Launch battle.net from the "Battle.net Launcher.exe" not "Battle.net.exe"

I am doing this since over a month, it changes nothing.

Follow the tip about adding the DLL
msvcp140(Native, Builtin)
vcruntime140(Native, Builtin)

Worked, took some time to load but worked just fine.

These DLL overrides should not be needed anymore. Did you have a problem without them? What Wine version are you using? And what exactly "took some time to load"?

This is the same error Storm Engineer reported earlier.

I'm running Wine 3.11-staging on Ubuntu Mate 18.04. AMD FX-8320 CPU, AMD Radeon HD 5770 video card, open source drivers. Setting "Enable_VAAPI as backend for DXVA2 GPU decoding" enabled, no winetricks config set. Wine set to Windows 7.

Some combination of the following two changes fixed it:
1. Per zen's earlier comment, I disabled hardware acceleration for Battle.net in the .config file.
2. I downgraded my kernel to 4.12.10-041210-generic (which, unfortunately, is old) but the linux-image-4.15.0-23-generic kernel installed when I upgraded to 18.04 did not work. If I can get it to work with a newer kernel, I will report back.

For a while now (I think since I switched from wine 2.21-staging to 3.x-staging) I notice that logging in takes about 75 seconds; That is: when the app starts, the login screen (with auto-login enabled) stays for about 75 seconds before the real application window opens up. The blizzard logo (the blue animated lines indicating login is in progress) very slowly changes then hangs then changes, it's not a smooth animation.

Anyone else noticed this and knows a cure?

Currently on wine 3.11-staging, on Slackware 14.2 core fonts and all winetricks outlined in the howto's are done. Eventually everything works, but it just takes very long.

Another thing I notice is the amount of cpu that is eaten by the app (and since I use AMD this becomes a thermal thing :-( I have no idea why it needs so much cpu power)

Hi I'm stuck with the same as everyone, bottom half of login screen all of a sudden stopped working (Ubuntu 16.04).

Any idea? When I try now to reinstall the battle.net client from .exe the computer freezes

Hi,

after an update, I tried to reinstall battlenet besause of a missing dll. I deleted end created a new wineprefix, installed battlenet but I had the same error

Here are my specs :
Ubuntu 16.04.01 64bit
Wineprefix 32bit 2.21-staging (with CSMT enabled)

My winecfg is set with Windows 7 version

Thx for the help

Same issue here - something must have changed in battle.net with their last update.

Upgrading to Wine staging 3.9 did the trick here. Loading up just fine again.

Had the same problem

You need to install the following libraries:
msvcp140(Native, Builtin)
vcruntime140(Native, Builtin)

After that it runs fine for me

Disabling the hw acceleration doesn't help, enabling it doesn't either. I have the lib32-libldap and lib32-gnutls installed. Fresh install in a new prefix, same deal.
The workarounds stopped working for me a really long time ago (hard to say exactly, feels like years, but months for sure).
A while ago I figured out that installing corefonts with winetricks let me log in. But the fonts then look crappy compared to using the microsoft-ttf-fonts installed on my system.

So yeah, I guess my questions are:
- anyone else having the same issue with the spinning logo and the known workarounds don't work?
- if so, would you test winetricks corefonts?

Just read bug32342, so my "great new find" is already known for about 6 years.
Anyhow, just as I said, winetricks corefonts makes the fonts look ugly on my system so I don't really want that. I've been looking into the winetricks script, seems like the installation of the fonts is copying the ttf files to $wine_dir/drive_c/windows/Fonts and then changing the path for every font in [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts] as well as [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Fonts] to the c:/windows/Fonts/fontname.
So if I backed up the corresponding keys in [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts] and [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Fonts] (or simply all of them so I don't have to manually find and export the 29 fonts wintricks installs) now, then winetricks corefonts, log into battle.net to get my magic token for the next year or so back, then manually rm the fonts from c:/windows/Fonts and use my registry backups the fonts should be completely uninstalled, right? Or am I missing something in the script? because I really want every trace from the winetricks corefonts gone when I'm done.

Ok, this worked for me:
1 I downloaded the arial32.exe and arialb32.exe (link in the winetricks script)
2 cabextracted the ttfs
3 fired up regedit in my prefix, navigated to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts and changed the values of the 5 Arial keys from "\\?\unix\path\to\font\ArialXYZ.ttf" to "ArialXYZ.ttf"
4 copied the 5 ttf files to windows/Fonts
5 started battle.net, logged in, then shut wine down
6 reverted the values in the registry so they would again point at the font files on my "host" system
7 deleted the fonts from windows/Fonts (probably optional if you want to be prepared for whenever your magic token from battle.net expires and you need to log in again)

Things to mention:
- do the regedit before you copy the ttf files! If they are present in windows/Fonts then they won't show up in the registry anymore.
- I accidentally only changed the keys in HKLM\\.......\Windows NT\... and not also in HKLM\\........\Windows\... . I meant to change the Arial keys in either location, but I forgot. The changes in Windows NT were enough in my case for the launcher log in to work.
- winetricks corefonts installs a bunch of fonts. In bug 32342 someone mentioned it's due to Arial and Times New Roman. I purposely tried only Arial (from arial32.exe and arialb32.exe) and it was enough in my case.
- if changing only Arial doesn't do the trick for you, then winetricks corefonts, start battle.net, log in, exit battle.net and kill remaining processes of it, then regedit and re-set the values of the 29 installed fonts so they point to your host system again in both HKLM\\.....Windows\... and HKLM\\...Windows NT\\..., then remove the ttf-files from windows/Fonts
- on my system the battle.net launcher starts a lot faster with winetricks corefonts. Just looks a little weird (letter spacing questionable I think), so I prefer to use the ttf from my host system.

And can someone with more knowledge please explain to me how a fricken font can have such an impact?

May my trials and errors help someone else as well.
Cheers

"winetricks corefonts" fixed it for me, thanks. The fonts look the same to me so no problem there :)

Have been horsing around abit how to get rid of some of the issues like the browser in the launcher I manged to get it to play more or less like it supposed to do.

Instead of starting the "Battle.net Launcher.exe" just start it with "Battle.net.exe". Only thing I encountered was the SystemSurvey crash, but I resolved that by just renaming it.
"Battle.net.exe" does also run with wine64.

Tested it on 2 systems,
notebook y50-70 16GB mem, nvidia gtx860m, Debian stretch 64bit, wine-staging 3.7, had to set graphics setting in game to 4 (recommended was 6, way to slow) 35-60 fps.
desktop amd fx-8320, 16GB mem, nvidia gtx1070, Debian buster 64bit, wine-staging 3.7, had to set graphics setting in game to 2 (recommended was 7, slow as hell) 27-60 fps.

All set to Windows 7 and no overrides.

If anyone can explain why the gtx1070 is slower than the gtx860m in my notebook your welcome.


Tried wine-staging 3.8 but had to revert to 3.7 due to very low fps 2-5 while I had 30-

WIne-staging 3.8 eats the CPU and down FPS to 4 - 6. Better revert to 3.7.

What games are you talking about that have the FPS drop on 3.8?

World of Warcraft. More here in comments:

appdb.winehq.org/objectManager.php?sClass=version&iId=33768

Heroes of the Storm was detroyed too. I couldn't revert to 3.7 quick enough, I didn't even test FInal Fantasy XIV...

Oh I should've added I reported a bug: 45209 Staging 3.8 crippling preformance degradation...

Hello, I've just started using wine and I wanted to play World of Warcraft, but to do it with fair FPS I saw, that I need to compile wine 3.7 with pba patch. I did it and now i have problem with installing battle.net client. When I'm using command wine64 , nothing happens. I don't see any error or something, just a new line in terminal. Can anyone help mi with that problem, please?

In a terminal create a fresh WINEPREFIX for Battle.net:
WINEPREFIX="/home/spaceman/.bnet" wine wineboot

Then launch battle.net "in that PREFIX":
WINEPREFIX="/home/spaceman/.bnet" wine "/${YOURPATH}/Battle.net/Battle.net.exe"

Might wanna put your own username in there too. :D

I've solved my issue with battle.net helper, it doens't crash anymore. I use new stable 3.6 staging wine version (64bit) for battle.net client. The trick it that i've installed new winetricks then flash (flash player14), dotnet45 and most important corefonts and ie8 with winetricks (beside other libs required for the game). Since then, battle.net helper doesn't crash anymore. I've renamed SystemSurvey.exe to exe.old and that crash is "disabled" also.

Maybe this help somebody. For me, BattleNet Client ver "9854" crashed every time on clean x64 prefix and wine-staging. Solution:
Add
"HardwareAcceleration": "false",
to "Client" section in file
$WINEPREFIX/users/$(whoami)/Application\ Data/Battle.net/Battle.net.config. You have to get something like that:
{
"Client": {
"HardwareAcceleration": "false",
"Version": {
"FirstRun": "false",
"Release": {
"FirstRun": "false",
"LastBuildVersion": "9854",
"LastSeenPatchNotesVersion": "9854"
}
},

… but it takes literally 10 minutes of Battle.net running on 100 % on two or three cores until the launcher actually shows something. After that everything works fine but it's annoying as hell.

Are you using winehq-staging-2.21?
$ wine --version
wine-2.21 (Staging)

What graphics drivers are you using? Have you tried a new wineprefix? Do you have any dll overrides, have you tried it without? "I also get a systemsurvey.exe error every time I start battle.net." I think we all do this doesn't affect performance at all.

"Battle.net Helper.exe goes full retard." I have no idea what that means. Battle.net frequently crashes on me I have kill agent.exe, Blizzard Battle.net and Battle.net Helper.exe in order to get it to launch again.

Sorry, login instructions were a bit unclear.

You have to hit the settings icon, that's where the 'continue without logging in' button is, in case anyone was having difficulties.

Like many others, Battle.net is the bane of my existence. It won't allow you to login, you just get the loading icon, then Battle.net Helper.exe goes full retard. I also get a systemsurvey.exe error every time I start battle.net.

I can log in just fine from within the game, but not through the launcher. Not really a big deal. To stop the display of these stupid error messages I just went into the install folder and appended '.cpy' to both the battle.net helper.exe file and the systemsurvey.exe file. Since both crash themselves and I can still play, they obviously aren't serving that much of a function.

No more error messages, the game works just fine. Sure, you have to hit 'continue without logging in', but it does work.

As of today I can't login anymore. The triangular loading animation just keeps spinning and the Login button never appears.

I disabled hardware acceleration but it didn't help.

Made a fresh prefix, I can now login, but then the launcher stops with this error:

"Failed to create a graphics context"

us.battle.net/support/en/article/12706

UPDATE!

Downgraded the nVidia driver and the kernel (was required for the nvidia downgrade) and the issue is fixed!


Downgraded:

nvidia-390.25-4-x86_64 > nvidia-387.34-21-x86_64
nvidia-utils-390.25-2-x86_64 > nvidia-utils-387.34-5-x86_64
linux-4.15.1-2-x86_64 > linux-4.14.15-1-x86_64


So it's a bug with the driver then?

Do you also have lib32-nvidia-utils in version 390.25? lib32- packages on Arch are often updated later than their standard 64-bit counterparts, so this might have caused the problem. For the record, I just updated my system (including linux 4.15.1-2, nvidia 390.25-4, nvidia-utils 390.25-2 and lib32-nvidia-utils 390.25-1), and I had no issues launching the app.

Sorry, I forgot to update here - indeed that was exactly the case here with the lib32 packages lagging in update, so it has been solved soon after. Thank you for your reply regardless!

Hi Storm Engineer,

I'm experiencing the same problem as you and probably everyone else (i.e. the perpetually-spinning login logo). You say you created a fresh wine prefix. Could you provide some deets? Which wine version did you install, and which architecture (i386 or amd64)? Also which distro are you running?

Thanks,

Matt

This component of Battle.net is crashing every time I load at the moment.

Battle.Net itself is extremely unstable and I would question whether this even deserves the Silver rating. It's constantly crashing, you then have kill the process, kill the Agent.exe process and relaunch. It's beyond irritating this application needs some love.

Would like to get an install working in a 64-bit prefix, given that others here and on reddit have said that they were able to do this on arch without incident. Versions/what I've tried:

Archlinux x86_64 4.14.15-1
wine-staging 2.21-1
lib32-libldap lib32-gnutls installed (and many other 32-bit libraries installed, as per randomly following advice from several other places)

Have tried with/without all combinations of

WINEPREFIX=/home/****/bnet winetricks corefonts fontsmooth=rgb
WINEPREFIX=/home/****/bnet winetricks vcrun2015
WINEPREFIX=/home/****/bnet winetricks vcrun2017

with Win 7 and Win 10 in winecfg (because some users here and on reddit have reported not needed to use winetricks at all in recent versions). Fresh wineprefix between each try. No success.

Have also tried manually added/removed certain dlls as per other older recommendations on other sites. Fresh wineprefix between each try. No success.

Fresh wineprefix for the purpose of logs for this comment. Running

WINEPREFIX=/home/****/bnet winecfg

gives: pastebin.com/i5T6FMmX

Settings Windows 10 and clicking apply, then following op and running

WINEPREFIX=/home/****/bnet winetricks corefonts fontsmooth=rgb

gives: pastebin.com/g20re9Bn

Running

WINEPREFIX=/home/****/bnet wine "/home/****/Desktop/Battle.net-Setup.exe"

Brings up the Battle.net setup and allows me to select language (I choose English EU). The client says says that it's updating, then asks me to confirm install location. Before clicking Continue with the install location, the output in the terminal seems to have many errors. The output so far is:

pastebin.com/yxR9VyQy

I uncheck "Create Desktop icon" and click continue. The app says it is installing and the progress bar reaches 100%. The full output in the terminal for the install is then

pastebin.com/1xiM4AYE

Attempting to run the client with

WINEPREFIX=/home/****/bnet optirun wine /home/****/bnet/drive_c/Program\ Files\ \(x86\)/Battle.net/Battle.net\ Launcher.exe

gives pastebin.com/Z6HUNUej and the client does not start. Similarly for using Battle.net.exe in the same folder.

Help would be greatly appreciated.

One thought: maybe the netcon errors are the problem? I am connecting from behind my university firewall, but I would've thought if it can't connect the installer would give me a "can't connect to the internet" error and still worked.

The logs I posted were with no vpn on - I normally play Blizzard games with a vpn, installing with the vpn on didn't help though, so made me think that this isn't the problem. But maybe the windows emulation doesn't know how to connect through my vpn when it's on? Just stabbing in the dark here...

It seems that since the last Battle.net update (version 9737) the client started using d3d11.
In my case, since I had d3d11 disabled in winecfg, the application wouldn't start, displaying the message "A required DLL could not be found". After enabling d3d11 it works; the only issue is that selecting Starcraft II causes "Battle.net Helper.exe" (not the app itself) to crash, and "Whoops" is displayed instead of usual news images.

Hello. I remove d3d11 disabled option in winecfg, but this does not do enything.

some logs:
pastebin.com/DMqr1Xmp

I press ctrl+c becouse nothing happend after start and wanting 10 minutes.

Do you have any other DLLs disabled? Can you check if it launches in a new, clean wineprefix, without DLL overrides?

Thank you! Clear wineprefix does the thing, without any manual adding dlls (without winetricks)!
I'm in game again after a week break.

Can you be more specific on what you did to "Enable d3d11"? I don't have any library overrides set and I was using DX11 mode in WoW before.

I just removed the dll override for d3d11 which I had earlier. If you don't have any overrides (which is the default), then d3d11 will be enabled.

$ env WINEPREFIX=~/.wine-hs primusrun wine /home/***/.wine-hs/drive_c/Program\ Files\ \(x86\)/Battle.net/Battle.net.exe
fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0x157483b, 0x15ef6d0, 0x15ef6e8) stub.
fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x15eb49a, 43) stub
fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0x1031123, 0x144f110, 0x144f128) stub.
fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x13ba3b0, 43) stub
fixme:kernelbase:AppPolicyGetThreadInitializationType 0xfffffffa, 0x5cde99c
wine: Unhandled exception 0x40000015 in thread a7 at address 0x49461e (thread 00a7), starting debugger...
fixme:ver:GetCurrentPackageId (0x32d238 (nil)): stub

wine-staging 2.21
Archlinux x86_64

i'm using wine devel 64 bit prefix
with Ubuntu 16.04
it seems working fine with older windows version but always fail on windows 7 or later. since blizzard always ask for windows version higher than 7 i cant install any game with windows xp version
is there anything i can do ?
i only did
winetricks vcrun 2017

You are using the development version of plain wine. See the notes above - plain wine will not install or run the client.
You need to install wine-staging 2.18 or better.
Wine-devel is not wine staging.

ahh i see. i thought wine devel is more latest version than the staging one.
it works now. thank you :)

hm, I guess you are correct:

wine-development --version
wine-2.20 (Debian 2.20-1)

I guess I had the mistaken view that wine-development was the staging package?

Yes. It's an easy mistake to make and I've done the same in the past.

I have the same problem also with 2.21 in Debian sid.
I suspect this [bugs.winehq.org/show_bug.cgi?id=42865#c18] is the cause, will see if it is easy to add the patches to the packages.

I'm using wine-staging 2.20 on Debian stretch (backported package).ttf-mscorefonts-installer package is installed (version 3.6). I initialize a fresh WINEPREFIX, use winetricks (version 0.0+20170101-1) to install corefonts, then start the installation. As soon as the window shows up where I need to enter my username/password, the app crashes and blizzard's error reporter pops up. I haven't been able to locate any debug information that might explain what's going on, anyone have an idea how to better debug this?

Sounds like you are running wine 2.20 not wine-staging 2.20.
Please check your active wine in a terminal by typing:

wine --version

hm, I guess you are correct:

wine-development --version
wine-2.20 (Debian 2.20-1)

I guess I had the mistaken view that wine-development was the staging package?
Comment

I have raised a wine-staging bug for this:
bugs.winehq.org/show_bug.cgi?id=44024

If you have a game that has a new version, there is no progress.
The progress bar is stuck at "init" and the console complains about stubs on MoveFileWithProgress and GetUniversalName.
It seems that it doesn't know how to read/write and find the files that need updating.
Is that part solved with the winetricks somehow?

There have been a number of people saying that they are unable to install the client and / or get it working correctly.

Please note that the recent test results that indicate everything works correctly, are based upon installation using wine-staging and not plain wine. There are a number of fixes in wine-staging that are not yet present in wine which have a huge impact on the successful installation and use of the client.

Please use the latest wine-staging when installing the Blizzard App / Battle.net client in a new, clean WINEPREFIX.

I'm trying to get 64bit Blizz App stuff going on, and when I use Windows 7 or higher, the BattleNet Helper crashes perpetually (as in, keeps crashing, over, and over, and over), and this is preventing me from being able to log into BattleNet.

This effectively means you can't play Overwatch now, as the game refuses to install when it sees you're running XP.

There's a bug report for this, and we need to get attention on it : bugs.winehq.org/show_bug.cgi?id=43910

Until then, Overwatch is not even possible, and "XP support is ending" will mean soon we won't be able to play ANYTHING Blizzard.

Hi there.

This how to is not working for me. I have an Arch distro (manjaro) and when I follow this how to step by step (a lot of times by now) the client never works. If I put it in WindowsXP, the client works, but no Diablo 3, and if I change it to Windows 7, Windows 8, Windows 2008 R2, etc no one of them works. Some clue?

Regards

There's something up for sure, I can't even install the client anymore.

Install:
wine, winetricks, lib32-gnutls, lib32-libldap, lib32-mpg123

WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks (installs mono and gecko)
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks corefonts
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks ie8
Reboot the WINE battle.net ‘system’
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 winetricks vcrun2015
I think this step changes the virtual drive to WinXP
Open winecfg. Go to Libraries tab and check libraries with default (native, builtin) setting:
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
ucrtbase.dll
vcruntime140.dll
I think these should be there already.
Under winecfg, Libraries tab:
d3d11 - disabled
WINEPREFIX=/home/kleshas/.PlayOnLinux/wineprefix/battle.net WINEARCH=win32 wine /home/kleshas/Downloads/Battle.net_Setup.exe

This worked for me under archx64. Still under WinXP, but for now the games work just with an extra warning from the battle.net client regarding out-of-support OS's. I'm not sure you need the WINEARCH=win32 every time.

If I follow the How-to but I put with wincfg that the client will launch in WinXP and the games like Diablo 3 will launch with Win7, every works fine... but when I want to install some game (like Starcraft II) I can't because the client is in WinXP:

"We can't install StarCraft II because your operatin system doesn't meet the minimum specs to run it.
Your OS: Windows XP Service Pack 3
Minimum: Windows 7"

Someone has some clue to launch the client with Win7?

Regards

The only way for me to play Heroes of the Storm
1) winecfg : choose WinXP
2) launch battle.net
3) in the same terminal : winecfg : choose Windows 7
4) then on battle.net launch the game
You will have the windows version message and it will launch

hope it will help someone else

Recently I noticed that the Blizzard App no longer kills of it's "Battle.net.exe" and "Agent.exe" processes when closed/exited.

This results in loads of "Battle.net.exe" processes running unless you manually close them after each exit of the Blizzard App.

I'm using wine-staging 2.19, also tried wine-staging-nine 2.19.

Anyone else noticed this? Is it a bug?

Yes, I've been manually killing battle.net processes for at least a couple of weeks now. archx64.

Yes, this is also happening for me.

UPDATE:

"winetricks dotnet40" + "winetricks --force ie8" fixed it.

This was a reply, no idea why it posted as comment...

Either way, my issue is NOT fixed after all. :(

So everything worked perfect with the 2008 preset until Blizz dropped 2008 support. Now for example SC2 refuses to start unless version is set to Win 7 or newer.

BUT... With Win 7 or newer, News and Chat doesn't work (Battle.net Helper.exe crashed). And I have Staging 2.18, corefonts installed and 32 bit packages installed.

Any workaround for this? Can I have wine run 2008 preset but report Win 7 towards programs to fool the system check maybe?

So nothing?

I have to chose between either the Social tab, news tab and Chat works, or the actual games work... this sucks.

I agree that would be frustrating. Are you sure you're using wine-staging?

Wine is free, opne source software, if you're not happy with any aspect of it you can always fork it and fix it yourself.

Made a bugreport: bugs.winehq.org/show_bug.cgi?id=43910

I found the problem for my previous not working battle net app. Everytime I have unread messages the app starts and the notification for messages closes the launcher...

Any ideas how to solve this?

Could you try the following, and report back:

1) Settings > Sound & Notifications: Disable "Enable Sound".

If that doesn't work, try this:

2) Settings > General: Disable "Use browser hardware acceleration when available"

And please, let me know if this works.

1. The launcher closes immediately so no time for changing. I tried disabling all sounds (set to false) in the blizz config but it didn´t solve anything

2. HW acceleration was already disabled.

This started a few versions before.

Hey, is this really Platinum? I just installed on a fresh 64-bit prefix and the login is still not 100% (mentions cookies disabled), What's New is blank, and there are no embedded videos/news due to Gecko deficiency. (winetricks ie8 would fix it, but isn't available on 64-bit prefix). I wonder how the reviewer fixed this.

Is this still an issue for anyone else? I've been waiting for wine-staging 2.18 to try before I file a bug. ;-)

Oh, winetricks ie8 does work on 64-bit prefix, despite what IE itself says. Nevermind, sorry!

This is all somewhat strange... I reinstalled using a 32 bit prefix. Now the launcher works fine but I have to set Win XP for viewing news. This should be fixed with 2.18-staging but it isn´t.

I hope anxiously wine-staging 2.18 in my repo if is how you say (feed and images loading).

By now, wine-staging 2.17 works at least to launch games (WoW) from the app without the use of wine-overwatch 2.14.

Thanks for your report.

This is to reply @Peter Anderson at post: appdb.winehq.org/commentview.php?iAppId=15365&iVersionId=28855&iThreadId=101074

Sorry for New Coment instead of Reply.

hello, i do not know but the friends list does not work. Why?

Hi!

After updating to latest version the client starts but after a few seconds it crashes everytime. I have to be quick and click on play in order to run any game. Tried several wine versions, win xp, 10 ...

Before the update all worked flawlessly. Any else experiencing this?

Yes, is the reason for use wine-2.14-overwatch to play WoW.

Didn´t change anything, now it works again. The blizz app is really annoying...

Hi!

Now after setting up a fresh wine bottle with the 2.16 staging (tried other verions) 32bit and exactly like the instructions above - I still get two annoying bugs which maybe related or not:

- everytime I launch the client the SystemSurvey.exe crashes but seems to have no effect on starting the Battlent App

The crash windows holds no information: "Waiting for detailed information, please wait..." never finishes.
Using playonlinux I can get a debug information:
p11-kit: couldn't load module: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so

- also the battlenet client window works for starting the games but doesn't show the inbuilt browser news anymore, just shows a spinning wheel forever.

Any ideas how to fix this? (Also I tried with all different windows version set in wine (XP up to W10).

thx, p.

Hi

The system survey crash happens when the MS corefonts aren't correctly installed. Make sure they are installed for the correct WINEPREFIX that the app is running in. e.g.

WINEPREFIX=/home/username/myblizzardapp winetricks corefonts

The policykit error can be caused by not having a policykit running, or sometimes two different policykits are installed and trying to run on the system. Are you using LXDE by any chance? Sometimes unticking the LXDE policykit in startup options under LXDE default applications on the start menu solves this.

Thx a lot for your help.

Corefonts are installed on arch here...

Using the command to install them into the WINEPRFIX doesn't work - "no absolute path", well I will have to recreate the folder structure of my system for that - can't do it right now.

The polkit seems to be correctly installed, do I need the 32bit or the 64bit or both (on a 64bit system)?

Using playonlinux doesn't work anymore cause of all the python updates...

Meh,. :-(
p.

Sorry, forgot to answer one of the points in your post. To get the web content displaying correctly:

Exit the app
Set windows version to XP using winecfg
Run the app and log in.
Now exit again and set win version to any version >= win 7
Next time you run the app the web content should be displayed properly.

Yes, this works.

But is a pain to do everyday.

In other hand, in October 1st (if I remember good) Blizzard delete XP version to run Blizzard (or Battle.net again in a nearly future) Launcher. The major problem is this.

If we can't change to XP to do the workaround to see web elements, we are dammned.

Regards and thank you to share the workaround.

That's sad...

Apparently, this will be fixed in wine-staging 2.18, due out shortly. Images ect. should load correctly in Win7 + mode.

Amazing!!

With wine-staging 2.18 all feed works, images and videos in all tabs!

So I'm using wine-staging 2.12, and Battle.net Helper.exe is crashing constantly. (I'm set to Windows 7.) I've got the overrides needed, and corefonts is installed. Any ideas? pastebin.com/1fsKmCAQ

So Battle.net works fine in a 32-bit prefix, but Battle.net Helper.exe crashes for me when in a 64-bit. Anyone have any ideas? (Same error as previous message.) Assuming something isn't installed in the 64-bit one that is in the 32-bit?

ETA: completely clean 64-bit prefix, and it works. Go figure. (Aside from the aforementioned oddities with html.)

But it hasnt for me. Under what you said, I deleted the application data seeming as it was working for you but not for me.

This didn't fix it. So, its still bugged for me.

Specs: Wine 2.4 Staging [Win 7]
Issue: Blizzard App Fails to Recognize Password Upon Switching Regions. The default "password" area isn't recognised when typed into. There is an override in place for US logins but not for EU logins.
Images: [with override under US] imgur.com/zZHUtPN [failing to override for EU] imgur.com/h6z3IWQ

Tried fixes:
> Changing the Launcher.db codes for both WoW and Blizz App to enEU from enUS to see if the override is just for the defaulted region. Does load the launcher by default as "europe", though still does not give the override.
> Typing in the password like 100 times to see if the override was something that proc'd from failed attempts on US. Hasn't worked.

When occured:
The Blizzard App ran an update about a week or so ago, it bugged out around this time. It threw all users of the application "out" of being signed in. Both on US and EU after the update. Upon signing back in I received this error, I assume from a GUI override update. A new game has been introduced to the application, which is not directly linked to Blizzard Entertainment, so I assume the integration of the new Destiny PC players accounts, put an issue in the coding for Wine under EU?

Currently, using the Blizzard App on US works fine. Though after a week of trying, waiting to see if it just fixed itself, I still cannot use it to sign into the EU interface.

I can still sign onto my EU WoW account through the US interface. So there is no rush, its just a minor hindrance. Does not affect gameplay of any of Blizzard's games. Just stops me talking to my EU friends when I am signed onto US WoW.

I experienced this problem a week or two ago, exactly as you described it but now I checked and it all works fine.
Even when the system is set to windows 10, even the blizzard news work.

I thought it would fix in a bit, but it hasnt for me.

Under what you said, I deleted the application data seeming as it was working for you but not for me.

This didn't fix it. So, its still bugged for me.

After Launching HS it crashes. BTW when I set win 7 in winecfg the battle net app doesnt launch.Only works with windows xp.

I'm running ParrotSec OS (I have no choice right now) but I can run a lot of Debian based programs and I've installed the latest Wine but every time I click on the Blizzard App it will pull up the little blue box stating that it's "Starting the Blizzard App" but then it goes away and I got nothing. I can't figure out what I'm doing wrong or how to fix it.

I managed to fix the login form being non-fancy by installing internet explorer (by running `winetricks ie8`).

I still, however, cannot see patch notes, update, "breaking news" and other type of "cards", once the app opens - I have two small white rectangles instead. That said, this problem can definitely be fixed, as it worked fine before I updated wine and purged my wine prefix, breaking my setup :P

Good call on ie8, I'll do some testing with that.

I have had luck with the News/Patch cards by using "winetricks dotnet40", then setting windows version back to 7. This appears to work from my testing yesterday but I haven't added it to the installation guide yet. Wanted to mess around a bit more. Maybe a different .NET version won't require a weird version hack?

I've just found out that *reinstalling* ie8 with `winetricks --force ie8` after it is already present fixes the cards for me.

I can confirm that using `winetricks dotnet40` fixes the cards. For me it *also* fixes the login screen in the absence of ie8.

For reference: wine-2.9 (or 2.1 - both work), staging (doesn't work with vanilla for me), 64-bit prefix, gentoo.

Weird, dotnet40 definitely doesn't fix the login screen for me on wine-2.9 staging, 32 bit or 64 bit. Do either of these fix the Shop for you?

> Do either of these fix the Shop for you?

dotnet40 does not fix. Force-installing ie8 fixes it. I haven't tried actually buying anything, but navigation certainly works just fine.

In case the issue lies within winetricks (ie8 installation being different or something):

$ winetricks --version
20170517 - sha256sum: 0461b25e833fd242b65addc72a5195c0047d3aaa91136b768d37102acb829a8e

Thanks! This fix is needed to play Diablo III without Rise of the Necromancer, as you need to close a splash screen that does not show unless HTML is rendered properly.

This only works when i use the windows xp setting witch is fine but blizzard is starting not to support win xp plz make it compatible wine win 10
setting plz. (I can't play "overwatch" of because of that)

Have a look at this: appdb.winehq.org/commentview.php?iAppId=15365&iVersionId=28855&iThreadId=100261

See my latest test results and installation information to see if this helps you get the Blizzard app with Windows 7 specified, although I can't promise good results with Overwatch, I haven't gotten to debugging a 64-bit prefix which Overwatch requires.

With latest blizzard app patches I can´t see patch notes and news anymore. The shop doesn´t load properly. Tried with and without acceleration and so on. No dll overrides used, games just run fine

using ubuntu 16.04 and wine 2.9 and 64 prefix (im sure it wont count as battle net is 32 bit app CMIIW)
get this error when running on every version except win xp

fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:wininet:InternetSetOptionW Option 77 STUB
fixme:wininet:InternetSetOptionW Option 77 STUB
err:wininet:open_http_connection create_netconn failed: 12029

Same here except my Operating system is Opensuse 42.2
Maybe not the same error code though.

Have a look at this: appdb.winehq.org/commentview.php?iAppId=15365&iVersionId=28855&iThreadId=100261

I was able to get the Blizzard App to install correctly following this guide, but I cannot get past the login prompt. The prompt asks for username and password, but does not have a login button. I've tried pressing ENTER after entering my information and nothing happens. I've also tried TAB+ENTER to find and press an invisible button but that hasn't worked either. Pressing the "Continue without logging in" button takes me to the game selection screen, but I am unable to login using the "Go online" button. Anyone else encounter this?

System Details:
Linux Mint 18
Wine 2.8

Issue resolved by forcing wine to run in 32 bit mode (set WINEARCH to win32 and reinstall)

The Blizzard app claims that windows XP will not be supported soon, which to me means they have intentions of breaking something. Does anyone have success running this in a more recent Windows version setting?

The Battle.net launcher works fine when setting Wine to a newer Windows version.

No success running the Blizzard App after setting Wine to "Windows 7".

What happened:
1. Loading bar shows up
2. Crash before login window opens

Successfully ran the Blizzard App on a 32-Bit and 64-Bit Wine, while version was set to "Windows 7". Used this Wine-Staging build on a openSUSE 42.2 (x86_64) system:
download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.2/x86_64/wine-staging-2.8-665.1.x86_64.rpm
download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.2/x86_64/wine-staging-32bit-2.8-665.1.x86_64.rpm

Only problem: There where two "E-Mail" and two "Password" fields in the login window and I had to enter my login data in the lower ones.

Have you successfully run any game though?

Yes, everything works fine! (campaign, multiplayer)

Confirmed working on funtoo with wine 2.3 after enabling the staging USE flag. Only tested 32-bit profile.

I guess it's running with Wine-Staging because of this patches.
(I wasn't able to do exact tests until now)

dev.wine-staging.com/patches/99/

dev.wine-staging.com/patches/103/

dev.wine-staging.com/patches/104/

dev.wine-staging.com/patches/107/

With wine staging 2.9 (CSMT on, of course) and version set to "Windows 7" on openSUSE 42.2 (x86_64) runs OK.

Only 2 errors.

1 - Two e-mail and passwords fields. Only type in the lower ones and uncheking (every day) the "no close session" option.

2 - Don't feed anything in Games panels (other tabs as Shop and News works OK). I can't see players on games nor Frame of news or eventually frames of warnings of problems or semanal maintenances. In SC and OW not appear the buttons Try free.

The point what bothers me the most is the second Point. The first point is annoying but passable.

This is for correct myself. In tabs Shop and News I only see text. 0 images.

Running wine 2.6 on Manjaro, I've been following the directions on the page. After setting the prefix to Windows XP, and installing ttf-ms-corefonts and vcrun2015, I ran the installer. It seems to work well until the progress bar is half-full, and the text reads "Updating Blizzard Agent..." The console from which I launched the installer reads "fixme:wininet:InternetSetOptionW Option 77 STUB." Has anyone else had this problem?

Yep, this was an issue for me as well, and yep, have it solved.

Now it runs well, however it literally takes AGES to start up (almost 10 minutes from $wine Battle.net Launcher.exe to the logged-in & working program.)

intended to be the comment in the "archlinux now works" thread.

Also if somebody else would not be patient enough, update to the games themselves sure take a while to initialize on wine-2.6; it took the launcher about solid 20 minutes to switch from "waiting.." to "initializing" and installing the patches. Not sure what it does when its "waiting" though.

I think something is missing if that takes that long.

I remember that launching Battle.net took 2 minutes for me year ago, then they updated it with new Qt and that fixed it.

Also remember that updating was stuck for me on Waiting if I didn't install vcrun2015, doing so fixed it.

Try winetricks vcrun2015 or disabling browser acceleration in settings if you have not tried it already.

Also consider starting from fresh WINEPREFIX and installing it with new Blizzard App installer if that was not the case.

Just tested this on the similiar computer with same wow/bnet version and same OS version etc etc.

Took much faster to start, yet at the moment its stuck at "Waiting" pre-update, which I hope would pass at some point and update would apply itself. :-S

Also if you have VPN, Tor or other network shenanigans setup that explains why it takes so long.

Nope, not using any of those.

A few days ago Blizzard rolled an update for the Battle.net launcher, version 1.7.1.8423.

I installed the required update and ever since then i have been experiencing performance issues. The client seems heavy now, and every game I run with it is even heavier to handle, making it impossible to play comfortably (even HS has minor lag issues, not to mention Heroes of the Storm or Diablo 3, which I can run but not play smoothly with a group of people) . Unfortunately we don't have the option to use an older version of the launcher,

Anyone has noted this issue now or in the past? Does someone have a workaround maybe in the form of some library override?

I am running Ubuntu 16.04 in a Intel i7 8x 2.5GHz with 8Gb RAM and 1Gb Graphic card running from a SSD Disk. It is a laptop but a decent one and i have not suffered performance issues in the past within this system.

Any suggestion would be appreciated.

Thanks :)

Experiencing a similar issue, although starting Hearthstone is not "minor lag" for me, it burns at 100% on all cores and is extremely sluggish. It was working fine a week ago but because I was trying to debug other games, I did a fresh WINEPREFIX, reinstalled the latest Blizzard app, and now it's completely awful. I have now cleared out the WINEPREFIX multiple times and followed the installation steps but no dice.

I wonder if this has something to do with us.battle.net/forums/en/wow/topic/20753178086