# Blizzard Battle.net App

Current version of the app

Application Details:

 Version: Current License: Free to use URL: https://www.blizzard.com/apps/... Votes: 6 Latest Rating: Bronze Latest Wine Version Tested: 5.12-staging

Maintainers:

## Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

• Installation in a 64-Bit Prefix
• Windows version has been to Windows X
• Entering the shop
• Logging in with user name and password
• Using additional Authentication codes using hardware authenticator.
• Installing and launching World of Warcraft
• Installing Hearthstone
• Changing online status from Online to AFK.

What does not

• Everything seems to work

Workarounds

What was not tested

• Launching Hearthstone
• Watching news videos inside the Blizzard Application

Hardware tested

Graphics:

• GPU:
• Driver:

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 02)

selected in Test Results table below
 Operating system Test date Wine version Installs? Runs? UsedWorkaround? Rating Submitter Show Arch Linux x86_64 Jul 14 2020 5.12-staging Yes Yes Yes Bronze Sergej Show Ubuntu 19.10 "Eoan" (+ variants like Kubuntu) Apr 05 2020 5.5 Yes Yes No Platinum Andrew Fischer Show Manjaro Linux 19.0 Mar 26 2020 5.4-staging Yes Yes No Platinum Jus de Patate_ Show Debian GNU/Linux 10.x "Buster" x86_64 Dec 29 2019 5.0-rc3-staging Yes Yes No Platinum Matthew Show Gentoo Linux x86_64 Nov 03 2019 4.19-staging Yes Yes Yes Gold nva

 Bug # Description Status Resolution Other apps affected 27168 chromium-based apps can't load https sites CLOSED FIXED 32340 View NX2 does not launch CLOSED FIXED 32342 Multiple applications and games using 'Webkit' or 'Blink' web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation) STAGED 33943 Battle.net client dropdowns do not appear until you hover its options STAGED 33947 Battle.net desktop app crashes after 15 seconds CLOSED FIXED 35150 Battle.net App drop-down for realm list doesn't show right after the click CLOSED DUPLICATE 35181 Path of Exile crashes at startup CLOSED FIXED 35902 Certificates signed using ECDSA signature can not be verified (>= Win Vista - affects EA Origin, Uplay, Blizzard App, MoonBot, Steam) CLOSED FIXED 35920 Battle.net app - Drop down menus don't work when clicked CLOSED DUPLICATE 36525 Ctrl+C does not copy in the Battle.net chat scrollback CLOSED FIXED 37343 Battle.net requested update produces error after restarting to allow the update CLOSED DUPLICATE 37347 Battle.net update 2014-10-01 results in black screen or distorted graphics with Intel drivers CLOSED NOTOURBUG 37354 Battle.net launcher does not start in Windows 7 mode: "Cannot load Qt platform plugin Windows" (FindFirstFileExW needs info level 'FindExInfoBasic' support) CLOSED FIXED 37618 Battle.net agent spams console with 'wbemprox:enum_class_object_Next timeout not supported' every 4 seconds CLOSED FIXED 37885 Battle.net launcher fails to set permissions on WoW files NEW 38260 Battle.net client show Traditional Chinese or Simplified Chinese is dot when into news page and shop page CLOSED INVALID 38845 Battle.net launcher shows white screen with WINEPREFIX Windows version > 'Windows XP' and builtin d3dcompiler_47.dll REOPENED 38953 Linux kernel version 4.2 will prevent Battle.net App from launching in Wine CLOSED NOTOURBUG 38960 Multiple applications need 'kernel32.SetFileCompletionNotificationModes' implementation (Steam 'steamwebhelper.exe' and Blizzard Battle.net desktop app CEF v3.2+/Chromium v44+ crash in Win7 mode, Sony Xperia Companion 1.7.x) CLOSED FIXED 39069 Battle.net launcher requires multiple click to focus tabs in Openbox NEW 39261 Battle.net launcher 1.12.0.2500 sometimes fails to start, reporting 'Battle.net requires the Windows Secondary Logon service to be enabled.' (error code BLZBNTBTS00000025) CLOSED INVALID 39642 Battle.net crashes when you try to resize the window when "allow the window manager to decorate the windows" is unchecked. CLOSED FIXED 40432 Battle.net crashes CLOSED DUPLICATE 40757 GOG Galaxy crashes with unimplemented function api-ms-win-crt-stdio-l1-1-0.dll.__stdio_common_vsnwprintf_s CLOSED FIXED 40857 Battle.net drop-down menus lack border NEW 40905 Multiple applications need api-ms-win-crt-runtime-l1-1-0.dll._get_narrow_winmain_command_line (PCSX2 1.4.0, Battle.Net Launcher) CLOSED FIXED 40917 Right click doesn't work on systray icons (e.g. Battle.net) CLOSED DUPLICATE 40930 Battle.net App: Windows versions higher than XP draw GTK decorations UNCONFIRMED 40931 Battle.net: Shop not working on Win7+ CLOSED DUPLICATE 41033 Unimplemented function api-ms-win-crt-runtime-l1-1-0.dll.set_terminate need by Battle.net CLOSED FIXED 41037 Unimplemented function vcruntime140.dll.__std_type_info_name is needed by Battle.net CLOSED FIXED 41054 Multiple applications fail to start when MSVCP140 is set to native (Battle.Net, Photoshop CC 2015.5) CLOSED FIXED 41061 Unimplemented function msvcp140.dll._Mtx_init_in_situ needed by Battle.net CLOSED FIXED 41074 Unimplemented function msvcp140.dll.__crtInitializeCriticalSectionEx needed by Battle.net CLOSED FIXED 41078 Unimplemented function msvcp140.dll.__crtCreateEventExW needed by Battle.net CLOSED FIXED 41084 Unimplemented function msvcp140.dll.__crtCreateSemaphoreExW needed by Battle.net CLOSED FIXED 41085 Unimplemented function msvcp140.dll._Thrd_id needed by Battle.net CLOSED FIXED 41086 Unimplemented function msvcp140.dll.??0?$codecvt@_WDU_Mbstatet@@@std@@QAE@I@Z needed by Battle.net CLOSED FIXED 41409 Battle.net crashes at launch CLOSED FIXED 41547 Blizzard Battle.net crashes on startup (CEF v3.2+/Chromium v44+ crash in Win7 mode, needs 'kernel32.SetFileCompletionNotificationModes' implementation) CLOSED DUPLICATE 41573 Battle.net: SystemSurvey.exe and Battle.net helper.exe crash (GUI process can't attach to parent process console, 'AttachConsole' is a stub) CLOSED FIXED 41599 Battle.net and Hearthstone play loud static when receiving messages CLOSED FIXED 41746 batle.net crashes CLOSED DUPLICATE 41948 Battle.net Helper.exe crashes repeatedly before login (winetricks corefonts is a workaround) CLOSED DUPLICATE 42000 Battle.net: invisible window elements with Win7+ mode CLOSED DUPLICATE 42359 Battle.net Helper.exe crashes at login dialog CLOSED DUPLICATE 42865 Battle.net: Crash on starting the application CLOSED DUPLICATE 42874 Battle.net App is unable to update games CLOSED FIXED 43349 Blizzard App Fails to Recognize Password Upon Switching Regions UNCONFIRMED 43901 battle.net login screen broken UI elements CLOSED DUPLICATE 43910 "Battle.net helper.exe" [NOT BLIZZARD APP!] crashes with Win 7 or higher CLOSED DUPLICATE 44024 Battle.net application does not exit cleanly when version >= Win7 CLOSED FIXED 44220 Battle.net client crashes moments after launch CLOSED DUPLICATE 44479 Battle.net "Failed to create a graphics context. " CLOSED INVALID 44576 QtWebEngineProcess.exe (Origin) crashes ('Webkit' based web browser engine, 'Arial' and 'Times New Roman' font face name validation) CLOSED DUPLICATE 45017 Battle.net Helper.exe crashes at login dialog CLOSED DUPLICATE 45061 Battle.net Helper.exe crashes at login dialog CLOSED DUPLICATE 45565 Battle.net Helper.exe crashes when trying to play videos UNCONFIRMED 45764 Unhandled exception in Battle.net CLOSED WORKSFORME 45814 Blizzard agent went to sleep. Attempting to wake it up... CLOSED ABANDONED 45837 Battle.net Launcher dropdown menu cant be opened, no icon to click UNCONFIRMED 46836 Battle.Net UI freezes when downloading big games after a period of time UNCONFIRMED 46932 Battle.Net crashes with wine 4.4 due to winhttp CLOSED INVALID 47207 Battle.net crashes with 4.8 Staging CLOSED ABANDONED 47479 Many D3D11 games show black or white screen with Wine 4.12.1 (Darkula by Locomalito, Magic the Gathering Arena, Battle.net, EVE Online, World of Warships) CLOSED FIXED 48293 Battle.net App lags when clicking UI elements CLOSED FIXED 48405 Battle.Net Launcher Beta crashes with Windows version set to 10 CLOSED FIXED 49590 Battle.net Agent.exe hang/crash CLOSED FIXED ## HowTo / Notes Installation Wine version If possible, use Wine Staging (any reasonably new version will work). Starting from version 3.12 vanilla Wine should also work, but it can have minor problems, so use it only if there is no option to install Staging. Libraries Ensure that your system has 32-bit libraries for libldap and gnutls installed (lib32-libldap and lib32-gnutls on Arch, but names may vary on other distros). Wineprefix configuration 64-bit prefix is recommended, since Blizzard is discontinuing 32-bit support for some of their games. Windows version should be set to Windows 7 or above. Winetricks "corefonts" should be installed, otherwise some pages will have incorrectly rendered text. The easiest way to do this is through winetricks: $ winetricks corefonts

You can also have the fonts installed through your package manager:

Installation

After everything described above is configured, run (from the terminal):

$wine Battle.net-Setup.exe and follow instructions in the installer. Troubleshooting Blizzard App icon keeps spinning forever, can't login • Click the little gear in top right, move mouse down to click "Settings" • Go to "Advanced" tab and check "Disable browser acceleration" Installer does not work on Arch Linux x86_64 • Install lib32-libldap and lib32-gnutls Battle.net window is all white • Add ucrtbase (native, builtin) to the list of library overrides for Battle.net.exe Cannot install or update games Lately there have been problems with Agent.exe, which result in users not being able to install and update games. The issue seems to appear randomly, but once it does, it will not go away without applying a workaround. 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: 1. Close Battle.net App (make sure that wineprefix is closed completely, e.g. by running "wineserver -k") 2. Delete "C:\ProgramData\Battle.net\Agent\product.db" file 3. Relaunch Battle.net App 4. 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. Unverified workarounds: • Installing vcrun2015 through winetricks; • Changing Windows version from 7 to 10. If anyone has new information on this topic, please let others know in the comments. ## Comments The following comments are owned by whoever posted them. WineHQ is not responsible for what they say. Black Screen on Battle.net by Panos on Monday March 16th 2020, 16:30 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? Window is invisible by MikeTechno on Thursday October 17th 2019, 23:37 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 RE: Window is invisible by MikeTechno on Saturday October 19th 2019, 14:16 I'm also on Staging 4.17. If someone could help that would be greatly appreciated. RE: Window is invisible by Maciej Stanczew on Sunday October 20th 2019, 2:52 Have you tried workarounds for the "white screen after login" issue? RE: Window is invisible by MikeTechno on Sunday October 20th 2019, 9:58 I added the libraries to Battle.net.exe and then it crashed after login. RE: Window is invisible by MikeTechno on Sunday October 20th 2019, 10:13 It actually only crashed once but after adding the libraries nothing changes workaround for "white screen after login" with Battle.net.11537 by Frank on Friday October 11th 2019, 12:49 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. RE: workaround for by sh0gunai on Saturday October 12th 2019, 15:14 Thank you very much for posting the fix here this fast. RE: workaround for by Pawel Wiecha on Tuesday October 15th 2019, 14:38 In my case only ucrtbase was needed. Anyway, thanks a lot for the fix! RE: workaround for by Maciej Stanczew on Sunday October 20th 2019, 3:02 Same for me, overriding just ucrtbase fixes the problem. I've added this info to Troubleshooting Notes. RE: workaround for by Maciej Stanczew on Sunday December 8th 2019, 16:48 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. Battle.net black window by JimB on Saturday July 27th 2019, 12:17 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. RE: Battle.net black window by JimB on Saturday July 27th 2019, 14:49 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. RE: Battle.net black window by Christian Widmer on Monday July 29th 2019, 11:17 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/ RE: Battle.net black window by Niklas HambÃ¼chen on Tuesday August 6th 2019, 18:03 Wine staging 4.13 fixed that problem for me. Battle.net crashes with wine-4.0-rc4 (Staging) and latest DXVK by illich on Sunday January 6th 2019, 8:34 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. RE: Battle.net crashes with wine-4.0-rc4 (Staging) and latest DXVK by Maciej Stanczew on Sunday January 6th 2019, 15:15 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 RE: Battle.net crashes with wine-4.0-rc4 (Staging) and latest DXVK by chlenorub on Monday January 7th 2019, 8:41 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) RE: Battle.net crashes with wine-4.0-rc4 (Staging) and latest DXVK by chlenorub on Monday January 7th 2019, 9:55 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 RE: Battle.net crashes with wine-4.0-rc4 (Staging) and latest DXVK by spaceman on Friday April 26th 2019, 12:58 Create a wineprefix for battle/net without DXVK and one with for WoW etc...Simples. Authentication using Blizzard Mobile Authenticator by Markus Linnala on Tuesday September 18th 2018, 10:33 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. RE: Authentication using Blizzard Mobile Authenticator by Maciej Stanczew on Tuesday September 18th 2018, 16:38 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. BattleNet app version 10532 broken in Wine-Staging 3.15 by Brandon on Thursday September 13th 2018, 20:39 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. RE: BattleNet app version 10532 broken in Wine-Staging 3.15 by Maciej Stanczew on Friday September 14th 2018, 1:52 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? RE: BattleNet app version 10532 broken in Wine-Staging 3.15 by Brandon on Friday September 14th 2018, 2:19 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-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.
RE: BattleNet app version 10532 broken in Wine-Staging 3.15
by Brandon on Saturday September 15th 2018, 3:34
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.
RE: BattleNet app version 10532 broken in Wine-Staging 3.15
by Maciej Stanczew on Tuesday September 18th 2018, 16:48
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?
RE: BattleNet app version 10532 broken in Wine-Staging 3.15
by Brandon on Friday September 21st 2018, 18:38
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.
Blizzard agent went to sleep. Attempting to wake it up...
by Storm Engineer on Wednesday September 12th 2018, 9:24
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
3.15 completely killed it
by Calmarius on Thursday September 6th 2018, 17:52
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.
RE: 3.15 completely killed it
by Maciej Stanczew on Thursday September 6th 2018, 18:24
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.)
RE: 3.15 completely killed it
by Maciej Stanczew on Thursday September 6th 2018, 19:08
Actually I can't find the comments nowâ€¦ I must have mixed something up.
RE: 3.15 completely killed it
by Florian on Saturday September 8th 2018, 10:07
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.
RE: 3.15 completely killed it
by FlagDUDE08 on Monday September 10th 2018, 15:08
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.
RE: 3.15 completely killed it
by Maciej Stanczew on Monday September 10th 2018, 15:26
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
RE: 3.15 completely killed it
by Maciej Stanczew on Wednesday September 12th 2018, 11:18
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
Flaky af
by spaceman on Thursday September 6th 2018, 6:32
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.
RE: Flaky af
by Maciej Stanczew on Thursday September 6th 2018, 12:34
> 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.)
RE: Flaky af
by spaceman on Thursday September 6th 2018, 12:47
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.
RE: Flaky af
by Maciej Stanczew on Thursday September 6th 2018, 14:56
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.
RE: Flaky af
by spaceman on Saturday September 8th 2018, 8:16
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.
by Michael Goetze on Wednesday September 5th 2018, 19:00
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?
RE:
by Maciej Stanczew on Wednesday September 5th 2018, 19:14
> 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?
RE:
by Michael Goetze on Wednesday September 5th 2018, 19:22
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.
RE:
by Finn Brinkmann on Thursday September 20th 2018, 8:41
Had the same problem "solved" it by linking my bnet account to my google account and logged me in with that one
Fixing 'Graphic Context' error
by muke on Sunday September 2nd 2018, 15:49
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.
RE: Fixing 'Graphic Context' error
by muke on Sunday September 2nd 2018, 15:50
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.
Wine-staging-3.15
by Sveinar Søpler on Sunday September 2nd 2018, 14:17
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.
RE: Wine-staging-3.15
by Maciej Stanczew on Sunday September 2nd 2018, 14:23
No problems here, Battle.net runs the same on Staging 3.14 and 3.15.
RE: Wine-staging-3.15
by Sveinar Søpler on Sunday September 2nd 2018, 14:59
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
RE: Wine-staging-3.15
by Adrian Demarais on Wednesday September 5th 2018, 11:42
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
RE: Wine-staging-3.15
by Sveinar Søpler on Wednesday September 5th 2018, 16:32
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...
Got another workaround on installing/updating problem
by dopella on Wednesday August 22nd 2018, 19:59
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
RE: Got another workaround on installing/updating problem
by Maciej Stanczew on Thursday August 23rd 2018, 2:29
By "stable" you mean version 3.0.2, right?
RE: Got another workaround on installing/updating problem
by dopella on Friday August 24th 2018, 8:28
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?
RE: Got another workaround on installing/updating problem
by dopella on Friday August 24th 2018, 8:34
NVM, installed IE8 and it worlked.
Game doesn't Play after clicking the button
by feliks on Sunday August 19th 2018, 14:35
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
RE: Game doesn't Play after clicking the button
by Maciej Stanczew on Sunday August 19th 2018, 19:46
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.).
RE: Game doesn't Play after clicking the button
by feliks on Tuesday August 21st 2018, 7:26
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.
RE: Game doesn't Play after clicking the button
by feliks on Thursday August 23rd 2018, 8:17
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.
RE: Game doesn't Play after clicking the button
by Maciej Stanczew on Thursday August 23rd 2018, 12:19
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
RE: Game doesn't Play after clicking the button
by feliks on Monday August 27th 2018, 10:44
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
Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by feliks on Saturday August 18th 2018, 6:33
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
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by Maciej Stanczew on Saturday August 18th 2018, 6:45
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.
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by feliks on Saturday August 18th 2018, 12:31
I have wine-3.0.2, just installed yesterday. Should be the staging version
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by Maciej Stanczew on Saturday August 18th 2018, 13:55
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.
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by feliks on Sunday August 19th 2018, 7:27
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.
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by Maciej Stanczew on Sunday August 19th 2018, 7:50
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.
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by feliks on Sunday August 19th 2018, 8:52
It worked perfectly.
Thank you very much, again!
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by feliks on Sunday August 19th 2018, 9:57
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
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by feliks on Sunday August 19th 2018, 10:52
it started working now, sorry, can delete reply
RE: Showing only 2 white boxes instead of text, buttons or anyting. Can't start games
by Maciej Stanczew on Sunday August 19th 2018, 19:51
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.
Not able to login and my own workaround for SC2 update
by Aleks on Thursday August 9th 2018, 3:59
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.
Ubuntu 18.04 + Wine
by Angus on Friday August 3rd 2018, 19:47
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.
RE: Ubuntu 18.04 + Wine
by Maciej Stanczew on Friday August 3rd 2018, 20:07
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.
RE: Ubuntu 18.04 + Wine
by Angus on Friday August 3rd 2018, 21:00
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! :)
RE: Ubuntu 18.04 + Wine
by Maciej Stanczew on Saturday August 4th 2018, 4:01
Glad it worked out in the end, happy playing!
Cannot install games
by Maciej Stanczew on Tuesday July 31st 2018, 15:17
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).

RE: Cannot install games
by Maciej Stanczew on Thursday August 2nd 2018, 16:26
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.
RE: Cannot install games
by K-M. Knaak on Sunday August 12th 2018, 13:56
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 RE: Cannot install games by Maciej Stanczew on Sunday August 12th 2018, 14:39 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. RE: Cannot install games by evilny0 on Friday August 17th 2018, 13:51 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. RE: Cannot install games by K-M. Knaak on Sunday August 19th 2018, 18:27 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. RE: Cannot install games by Maciej Stanczew on Sunday August 19th 2018, 20:14 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. RE: Cannot install games by aaahaaap on Wednesday August 22nd 2018, 12:44 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! RE: Cannot install games by Josh R Raymond on Tuesday August 28th 2018, 17:26 Launch battle.net from the "Battle.net Launcher.exe" not "Battle.net.exe" RE: Cannot install games by Maciej Stanczew on Wednesday August 29th 2018, 0:46 I am doing this since over a month, it changes nothing. Working by spiritsc on Monday July 30th 2018, 20:51 Follow the tip about adding the DLL msvcp140(Native, Builtin) vcruntime140(Native, Builtin) Worked, took some time to load but worked just fine. RE: Working by Maciej Stanczew on Tuesday July 31st 2018, 15:00 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"? Also saw the "failed to create a graphics context" error. by Mike Swi on Tuesday July 10th 2018, 9:00 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. Logging in takes ages by Michiel on Friday July 6th 2018, 4:17 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) by asasaa on Wednesday June 13th 2018, 15:21 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 error with missing dll after intallation by Carbone on Tuesday May 29th 2018, 16:27 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 RE: error with missing dll after intallation by Jeff Hoogland on Tuesday May 29th 2018, 18:56 Same issue here - something must have changed in battle.net with their last update. RE: error with missing dll after intallation by Jeff Hoogland on Tuesday May 29th 2018, 19:07 Upgrading to Wine staging 3.9 did the trick here. Loading up just fine again. RE: error with missing dll after intallation by Lukas on Friday June 1st 2018, 13:32 Had the same problem You need to install the following libraries: msvcp140(Native, Builtin) vcruntime140(Native, Builtin) After that it runs fine for me blizzard logo keeps spinning despite the workarounds by Stefan on Saturday May 26th 2018, 5:36 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? RE: blizzard logo keeps spinning despite the workarounds by Stefan on Saturday May 26th 2018, 6:55 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.
RE: blizzard logo keeps spinning despite the workarounds
by Stefan on Saturday May 26th 2018, 12:53
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
RE: blizzard logo keeps spinning despite the workarounds
by Roland D on Tuesday July 3rd 2018, 17:43
"winetricks corefonts" fixed it for me, thanks. The fonts look the same to me so no problem there :)
Battle.net Launcher solved some issues with it
by DeeDee Ranged on Monday May 14th 2018, 7:27
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-
RE: Battle.net Launcher solved some issues with it
by Alberto on Tuesday May 15th 2018, 3:56
WIne-staging 3.8 eats the CPU and down FPS to 4 - 6. Better revert to 3.7.
RE: Battle.net Launcher solved some issues with it
by Maciej Stanczew on Tuesday May 15th 2018, 11:34
What games are you talking about that have the FPS drop on 3.8?
RE: Battle.net Launcher solved some issues with it
by Alberto on Tuesday May 15th 2018, 11:38
World of Warcraft. More here in comments:

appdb.winehq.org/objectManager.php?sClass=version&iId=33768
RE: Battle.net Launcher solved some issues with it
by spaceman on Wednesday May 16th 2018, 3:57
Heroes of the Storm was detroyed too. I couldn't revert to 3.7 quick enough, I didn't even test FInal Fantasy XIV...
RE: Battle.net Launcher solved some issues with it
by spaceman on Wednesday May 16th 2018, 4:13
Oh I should've added I reported a bug: 45209 Staging 3.8 crippling preformance degradation...
Cannot run installer using wine 3.7 + pba patch
by Xantek on Friday May 4th 2018, 14:25
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?
RE: Cannot run installer using wine 3.7 + pba patch
by spaceman on Wednesday May 9th 2018, 15:12
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" RE: Cannot run installer using wine 3.7 + pba patch by spaceman on Wednesday May 9th 2018, 15:14 Might wanna put your own username in there too. :D Battle.net crashing by UniMaX on Saturday April 21st 2018, 12:36 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. Start BattleNet Client by zen on Monday February 26th 2018, 12:44 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" } }, The launcher still starts for me by Oliver Sperke on Saturday February 24th 2018, 7:15 â€¦ 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. Staging by spaceman on Sunday February 11th 2018, 7:57 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.
edit
by Scottie on Thursday February 8th 2018, 6:42
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.
Sort of a workaround
by Scottie on Thursday February 8th 2018, 6:27
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.
by Storm Engineer on Tuesday February 6th 2018, 11:20
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.
RE: Can't login anymore
by Storm Engineer on Tuesday February 6th 2018, 11:31
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
RE: Can't login anymore
by Storm Engineer on Tuesday February 6th 2018, 13:32
UPDATE!

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

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?
RE: Can't login anymore
by Maciej Stanczew on Tuesday February 6th 2018, 13:49
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.
RE: Can't login anymore
by Storm Engineer on Saturday February 10th 2018, 6:29
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!
RE: Can't login anymore
by Matt Spraggs on Sunday February 11th 2018, 7:06
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
SystemSurvey.exe
by spaceman on Tuesday February 6th 2018, 10:00
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.
Can't get the 64-bit client to install on Arch (but others say they can?)
by Jon Rayner on Wednesday January 31st 2018, 1:26
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.
RE: Can't get the 64-bit client to install on Arch (but others say they can?)
by Jon Rayner on Wednesday January 31st 2018, 6:45
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...
The client now requires d3d11
by Maciej Stanczew on Thursday January 11th 2018, 12:26
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.
RE: The client now requires d3d11
by lu on Friday January 12th 2018, 11:31
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.
RE: The client now requires d3d11
by Maciej Stanczew on Monday January 15th 2018, 23:49
Do you have any other DLLs disabled? Can you check if it launches in a new, clean wineprefix, without DLL overrides?
RE: The client now requires d3d11
by lu on Tuesday January 16th 2018, 11:22
Thank you! Clear wineprefix does the thing, without any manual adding dlls (without winetricks)!
I'm in game again after a week break.
RE: The client now requires d3d11
by Tom B on Saturday March 10th 2018, 2:29
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.
RE: The client now requires d3d11
by Maciej Stanczew on Saturday March 10th 2018, 4:28
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.
Won't start after 10.01.2018
by lu on Thursday January 11th 2018, 11:09
$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 dbghelp_dwarf:eval_expression Couldn't read memory at fffffff0 and crash on windows 10 by asembus on Sunday November 26th 2017, 4:06 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 RE: dbghelp_dwarf:eval_expression Couldn't read memory at fffffff0 and crash on windows 10 by Peter Anderson on Monday November 27th 2017, 4:02 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. RE: dbghelp_dwarf:eval_expression Couldn't read memory at fffffff0 and crash on windows 10 by asembus on Thursday November 30th 2017, 0:41 ahh i see. i thought wine devel is more latest version than the staging one. it works now. thank you :) by Hase on Tuesday November 21st 2017, 16:34 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? RE: by Peter Anderson on Tuesday November 21st 2017, 16:40 Yes. It's an easy mistake to make and I've done the same in the past. 2x patches by alfadir on Tuesday November 21st 2017, 3:31 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. Not getting it to work by Hase on Sunday November 19th 2017, 16:35 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? RE: Not getting it to work by Peter Anderson on Tuesday November 21st 2017, 16:26 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 RE: Not getting it to work by Hase on Tuesday November 21st 2017, 16:35 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 Battle.net.exe and Agent.exe not closing properly. by Peter Anderson on Monday November 13th 2017, 14:20 I have raised a wine-staging bug for this: bugs.winehq.org/show_bug.cgi?id=44024 Updates seem broken by Chiro on Sunday November 12th 2017, 4:24 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? Battle.net installation. by Peter Anderson on Sunday November 5th 2017, 12:12 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. Helper Crashes in Win 7 or higher, only Win XP "Fixes" it, making Overwatch not possible by BloodyIron on Sunday November 5th 2017, 12:09 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. How to is not working for me by CromatDragon on Thursday November 2nd 2017, 12:59 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 RE: How to is not working for me by sykhro on Thursday November 2nd 2017, 14:52 There's something up for sure, I can't even install the client anymore. RE: How to is not working for me by kleshas on Friday November 3rd 2017, 17:11 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. RE: How to is not working for me by CromatDragon on Saturday November 4th 2017, 5:04 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 RE: How to is not working for me by Jean-Michel on Tuesday November 21st 2017, 16:17 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 App no longer kills it's child processes by Dan (Strit) Johansen on Tuesday October 31st 2017, 15:57 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? RE: App no longer kills it's child processes by kleshas on Thursday November 2nd 2017, 11:34 Yes, I've been manually killing battle.net processes for at least a couple of weeks now. archx64. RE: App no longer kills it's child processes by Peter Anderson on Sunday November 5th 2017, 12:19 Yes, this is also happening for me. by Storm Engineer on Saturday October 21st 2017, 10:58 UPDATE: "winetricks dotnet40" + "winetricks --force ie8" fixed it. RE: by Storm Engineer on Saturday October 21st 2017, 11:04 This was a reply, no idea why it posted as comment... Either way, my issue is NOT fixed after all. :( Games need Win 7 or newer - Chat doesn't work with Win 7 or newer by Storm Engineer on Monday October 16th 2017, 12:39 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? RE: Games need Win 7 or newer - Chat doesn't work with Win 7 or newer by Storm Engineer on Friday October 20th 2017, 11:31 So nothing? I have to chose between either the Social tab, news tab and Chat works, or the actual games work... this sucks. RE: Games need Win 7 or newer - Chat doesn't work with Win 7 or newer by spaceman on Thursday December 21st 2017, 12:34 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. RE: Games need Win 7 or newer - Chat doesn't work with Win 7 or newer by Storm Engineer on Friday October 20th 2017, 20:37 Blizzard app crashed while having unread messages by mioc on Wednesday October 4th 2017, 8:33 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? RE: Blizzard app crashed while having unread messages by Dox on Thursday October 5th 2017, 9:59 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. RE: Blizzard app crashed while having unread messages by mioc on Thursday October 5th 2017, 10:59 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. Platinum and HTML content by Tod Jackson on Tuesday October 3rd 2017, 15:26 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. ;-) RE: Platinum and HTML content by Tod Jackson on Tuesday October 3rd 2017, 15:34 Oh, winetricks ie8 does work on 64-bit prefix, despite what IE itself says. Nevermind, sorry! RE: Platinum and HTML content by mioc on Thursday October 5th 2017, 11:52 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. by Alberto on Tuesday October 3rd 2017, 10:09 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. RE: by Alberto on Tuesday October 3rd 2017, 10:11 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. no friends list by diego on Thursday September 28th 2017, 15:57 hello, i do not know but the friends list does not work. Why? Crash with newest blizz app v9397 by mioc on Sunday September 24th 2017, 4:41 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? RE: Crash with newest blizz app v9397 by Alberto on Monday September 25th 2017, 4:13 Yes, is the reason for use wine-2.14-overwatch to play WoW. RE: Crash with newest blizz app v9397 by mioc on Sunday October 1st 2017, 10:36 DidnÂ´t change anything, now it works again. The blizz app is really annoying... The battlenet Client doesn't show the inbuilt browser images, movies etc... by pk on Thursday September 14th 2017, 10:24 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. RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by Peter Anderson on Monday September 18th 2017, 8:29 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. RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by pk on Monday September 18th 2017, 14:54 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. RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by Peter Anderson on Monday September 18th 2017, 8:33 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. RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by Alberto on Monday September 18th 2017, 13:17 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. RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by pk on Monday September 18th 2017, 14:48 That's sad... RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by Peter Anderson on Tuesday October 3rd 2017, 10:02 Apparently, this will be fixed in wine-staging 2.18, due out shortly. Images ect. should load correctly in Win7 + mode. RE: The battlenet Client doesn't show the inbuilt browser images, movies etc... by Alberto on Friday October 6th 2017, 14:09 Amazing!! With wine-staging 2.18 all feed works, images and videos in all tabs! Battle.net Helper.exe crash by Jen on Wednesday July 12th 2017, 11:03 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 RE: Battle.net Helper.exe crash by Jen on Friday July 14th 2017, 14:47 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? RE: Battle.net Helper.exe crash by Jen on Friday July 14th 2017, 14:55 ETA: completely clean 64-bit prefix, and it works. Go figure. (Aside from the aforementioned oddities with html.) I thought it would by Siren Watcher on Saturday July 8th 2017, 3:39 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. Blizzard App Fails to Recognize Password Upon Switching Regions by Siren Watcher on Friday June 30th 2017, 11:26 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. RE: Blizzard App Fails to Recognize Password Upon Switching Regions by jarao on Monday July 3rd 2017, 15:37 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. RE: Blizzard App Fails to Recognize Password Upon Switching Regions by Siren Watcher on Saturday July 8th 2017, 4:05 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. Hearthstone crashes after launching by Nikita on Monday June 19th 2017, 16:44 After Launching HS it crashes. BTW when I set win 7 in winecfg the battle net app doesnt launch.Only works with windows xp. Pulling My Hair Out by CiciBean on Thursday June 15th 2017, 21:13 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. A fix for login form being non-graphical by moxian on Wednesday June 14th 2017, 12:16 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 RE: A fix for login form being non-graphical by AdamTheGrump on Wednesday June 14th 2017, 12:22 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? RE: A fix for login form being non-graphical by moxian on Wednesday June 14th 2017, 12:40 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. RE: A fix for login form being non-graphical by AdamTheGrump on Wednesday June 14th 2017, 12:43 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? RE: A fix for login form being non-graphical by moxian on Wednesday June 14th 2017, 13:39 > 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
RE: A fix for login form being non-graphical
by FranÃ§ois Warnet on Tuesday June 27th 2017, 21:29
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.
Operating systems
by Nate Clark on Saturday May 27th 2017, 7:02
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)
RE: Operating systems
by kolAflash on Sunday June 4th 2017, 13:21
RE: Operating systems
by AdamTheGrump on Sunday June 11th 2017, 12:52
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.
News/Updates/shop not showing up
by mioc on Saturday May 27th 2017, 2:46
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
failing to run in other version than win xp
by asembus on Friday May 26th 2017, 21:01
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
RE: failing to run in other version than win xp
by Nate Clark on Saturday May 27th 2017, 10:12
Same here except my Operating system is Opensuse 42.2
Maybe not the same error code though.
RE: failing to run in other version than win xp
by kolAflash on Sunday June 4th 2017, 13:18
Blizzard App installs correctly, but login is broken
by pyr0man99 on Thursday May 25th 2017, 14:39
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
RE: Blizzard App installs correctly, but login is broken
by pyr0man99 on Tuesday May 30th 2017, 19:03
Issue resolved by forcing wine to run in 32 bit mode (set WINEARCH to win32 and reinstall)
impending release issues
by AdamTheGrump on Wednesday May 24th 2017, 1:08
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?
RE: impending release issues
by Zeke Sonxx on Wednesday May 24th 2017, 12:35
The Battle.net launcher works fine when setting Wine to a newer Windows version.
RE: impending release issues
by kolAflash on Wednesday May 24th 2017, 13:44
No success running the Blizzard App after setting Wine to "Windows 7".

What happened:
2. Crash before login window opens
RE: impending release issues
by kolAflash on Wednesday May 24th 2017, 14:44
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:

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.
RE: impending release issues
by Pacane on Friday June 2nd 2017, 14:25
Have you successfully run any game though?
RE: impending release issues
by kolAflash on Sunday June 4th 2017, 13:18
Yes, everything works fine! (campaign, multiplayer)
RE: impending release issues
by Marc Grondin on Sunday June 4th 2017, 14:15
Confirmed working on funtoo with wine 2.3 after enabling the staging USE flag. Only tested 32-bit profile.
RE: impending release issues
by kolAflash on Monday June 5th 2017, 7:56
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/
RE: impending release issues
by Alberto on Monday June 5th 2017, 4:35
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.
RE: impending release issues
by Alberto on Monday June 5th 2017, 5:01
This is for correct myself. In tabs Shop and News I only see text. 0 images.
Installer hangs on
by Thomas Woltjer on Monday May 8th 2017, 21:20
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?
Created account just to say thanks!
by Mike on Friday April 28th 2017, 7:54
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.)
RE: Created account just to say thanks!
by Mike on Friday April 28th 2017, 8:04
intended to be the comment in the "archlinux now works" thread.
RE: Created account just to say thanks!
by Mike on Friday April 28th 2017, 8:51
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.
RE: Created account just to say thanks!
by Svito on Friday April 28th 2017, 10:24
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.
RE: Created account just to say thanks!
by Mike on Friday April 28th 2017, 18:42
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
RE: Created account just to say thanks!
by Svito on Friday April 28th 2017, 10:26
Also if you have VPN, Tor or other network shenanigans setup that explains why it takes so long.
RE: Created account just to say thanks!
by Mike on Friday April 28th 2017, 18:41
Nope, not using any of those.
Performance since version 1.7.1.8423
by Jose on Tuesday February 28th 2017, 11:38
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 :)
RE: Performance since version 1.7.1.8423
by AdamTheGrump on Tuesday April 18th 2017, 12:22
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