WineHQ

Hearthstone

Game itself

For installer help and issues see Blizzard App on AppDB

Application Details:

Version: Game
License: Free to use
URL: https://battle.net/hearthstone...
Votes: 19
Latest Rating: Gold
Latest Wine Version Tested: 3.12

Maintainers: About Maintainership

Free Download Hearthstone

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

Everything

What does not

Workarounds

What was not tested

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

At first, get a lot of errors when trying to launch Battle.net, whether from PlayOnLinux or in my own Wine container. Command line reveals several lines similar to: [h2]Object moved to [a href="http://www.blizzard.com/404"]here[/a].[/h2] [/body][/html] (I changed angle brackets to square to prevent HTML-stripping.) This has something to do with a missing 32-bit library, even when using a 32-bit Wine container on CentOS 7. One of the following fixed it, I didn't isolate which one: yum groupinstall "Compatibility Libraries" (This alone didn't, but I followed it up with:) yum install glibc-devel.i686 dbus-devel.i686 freetype-devel.i686 pulseaudio-libs-devel.i686 libX11-devel.i686 mesa-libGLU-devel.i686 libICE-devel.i686 libXext-devel.i686 libXcursor-devel.i686 libXi-devel.i686 libXxf86vm-devel.i686 libXrender-devel.i686 libXinerama-devel.i686 libXcomposite-devel.i686 libXrandr-devel.i686 mesa-libGL-devel.i686 mesa-libOSMesa-devel.i686 libxml2-devel.i686 libxslt-devel.i686 zlib-devel.i686 gnutls-devel.i686 ncurses-devel.i686 sane-backends-devel.i686 libv4l-devel.i686 libgphoto2-devel.i686 libexif-devel.i686 lcms2-devel.i686 gettext-devel.i686 isdn4k-utils-devel.i686 cups-devel.i686 fontconfig-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686 pkgconfig.i686 libtiff-devel.i686 unixODBC.i686 openldap-devel.i686 alsa-lib-devel.i686 audiofile-devel.i686 freeglut-devel.i686 giflib-devel.i686 gstreamer-devel.i686 gstreamer-plugins-base-devel.i686 libXmu-devel.i686 libXxf86dga-devel.i686 libieee1284-devel.i686 libpng-devel.i686 librsvg2-devel.i686 libstdc++-devel.i686 libusb-devel.i686 unixODBC-devel.i686 qt-devel.i686 There's a lot of vague (to me) info on the net about how CentOS doesn't support 32-bit wine, and that some 32-bit libraries are required for Battle.net. Most places mentioned a 32-bit ldap library was required, so that might be the only one of all the above that was required? I installed them all because I was going to build my own Wine, but tried it after the last big install of all those 32-bit libs and it worked. I think this is probably technically a Battle.net issue rather than a Hearthstone-specific issue.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowArch Linux x86_64Jul 14 20183.12Yes Yes YesGoldMaciej Stanczew 
ShowFedora 28 x86_64May 17 20183.8Yes Yes YesGoldOlof Sjodin 
ShowArch Linux x86_64Apr 24 20183.5Yes Yes YesGoldOzan 
ShowLinux Mint 18.3 "Sylvia" x86_64Feb 01 20183.0Yes Yes YesGoldAmosar 
ShowGentoo Linux x86_64Jan 20 20183.0Yes Yes YesGoldJohn Haverkamp 

Known Bugs

Bug # Description Status Resolution Other apps affected
23807 Unsupported texture formats: DF16, DF24, RAWZ: format unrecognized(909198916) NEW View
35291 setcap on wine-preloader causes application problems (Hearthstone) NEW View
38916 Hearthstone fails with 'GLOBAL_ERROR_ASSET_LOAD_FAILED' when using Wine from Ubuntu PPA (broken package?) REOPENED View
39754 Multisample resolve is not implemented for typeless resources (EVE Online, Hearthstone, Just Cause 2, Outcast Second Contact, VRChat) UNCONFIRMED View
42845 Hearthstone crashes at loading screen NEW View
44457 Hearthstone crashes on exit in d3d9 mode RESOLVED INVALID View
45492 Can't run Hearthstone on Ubuntu 18.04 NEEDINFO View

Show all bugs

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Saturday June 2nd 2018, 21:16
With intel and Ubuntu 16.04, the game runs very well - but after upgrading the hardware to AMD (details of new hardware here: pastebin.com/WukBAhhv ), I cannot make this game run in recent distros (with kernel 4.15+, maybe?), like Ubuntu 18.04 or Manjaro 17.1.10: I'm stalled in a black screen after game launch, with or without the "-force-d3d9".

This is making me stick with Ubuntu 16.04, but are tons of improvements for AMD hardware in kernels 4.15+, I'm trying to use distros that support recent kernels...
RE: I can't make it work in recent distros after changing to AMD hardware
by Glenn on Friday July 20th 2018, 12:39
Same here.

Arch Linux - black screen with pointer ( with and without -force-d3d9 )
RE: I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Friday July 20th 2018, 13:13
An old installation on Xubuntu 16.04 still working after the kernel 4.15 backport: the issue seems not related with the kernel itself, but with the AMD hardware (I even tried to put an NVIDIA GT710 in it, but the issue persisted...)

I will try to reinstall the game in this distro (Xubuntu 16.04) to see if the issue persists
RE: I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Friday July 20th 2018, 13:41
The re-instalation on Xubuntu 16.04 works (only tested with NVIDIA VGA)
RE: I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Friday July 20th 2018, 18:04
Tried again to install on Xubuntu 18.04 without success (even with other, intel-only, hardware) - Manjaro gave me similar results a while ago: I will try actually Arch now :P
RE: I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Friday July 20th 2018, 18:59
Installation failed on Debian stretch too...
RE: I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Saturday July 21st 2018, 15:29
no luck with Arch or Ubuntu either: I will file a bug
RE: I can't make it work in recent distros after changing to AMD hardware
by Felipe Braga on Saturday July 21st 2018, 15:43
Test without -force-d3d9 and CPU usage
by Stepan Vanzuriak on Saturday February 3rd 2018, 2:03
As say Gruik Hearstone use alot CPU and even disabling hardware accceleration not help me. But I test it without -force-d3d9 (use less CPU) and with -force-d3d10 (use same as -force-d3d9 but without graphics).

If not use -force-d3d9 you get no graphics but sound, pointer and you can click on buttons on black screen
Missing library + CPU usage
by Gruik on Sunday January 21st 2018, 8:05
There are missing steps in the installation procedure (or is it because i use PoL ?) : the game crashed on startup.
After searching a little, i realized it may be caused by missing libraries (possibly .NET). So, using PoL configuration, i installed randomly dotnet40 and vcrun2013 ; and then it worked. Note that it switched windows version to XP, so i had to switch it back to windows 7.

Then there was another "problem" : the game was really nice and smooth graphically but CPU usage was real high (53% and more only for the hearthstone process, which is more than 2 full cores), it felt like my laptop was going to die with fan full speed and temperatures really high.
After searching a little, i thought it was due to the absence of vsync (a lot of topics exist on how to disable it but not on how to enable it), i tried various configurations in the games' "options.txt" but didn't change anything.
Then, i found a solution given by blizzard itself when there was a similar problem on mac months ago : just disable hardware accceleration on the blizzard launcher (launchers' settings > general settings tab). After restarting the launcher, now hearthstone has a reasonable CPU usage
Battle.net 9737
by Oliver Sperke on Wednesday January 10th 2018, 2:58
There is a new problem with the latest battle net version. It seems like Blizzard thought it was a good idea to make DirectX11 now mandatory for the Blizzard app. However this leads to huge problems in hearthstone. The only temporary solution is to delete the Battle.net.9737 and just load the old version. Does anyone have a better solution?
RE: Battle.net 9737
by Drew Feragen on Wednesday January 10th 2018, 13:29
In wine configuration don't disable d3d11, this will allow the Battle.net launcher to start.

Then within the blizzard app, set the Game Settings for hearthstone to have the additional command line argument "-force-d3d9"
instruction
by urgo on Tuesday December 26th 2017, 11:58
DON'T follow the instruction made by puargs.
Especially this line is bad "rm -r ~/.wine" You will lost all Windows applications that you have already installed via wine. Don't do it. It is not necessary.

Here is the right instruction.
1. Install the newest wine:
sudo dpkg --add-architecture i386
sudo add-apt-repository 'dl.winehq.org/wine-builds/ubuntu/'
sudo wget dl.winehq.org/wine-builds/Release.key && sudo apt-key add Release.key
sudo rm -f Release.key
sudo apt update
sudo apt install --install-recommends wine-staging
2. download installation file from playhearthstone.com.
3. go to the folder with your instalation file.
4. install Heartstone to a separate folder like .wine-heartstone:
env WINEPREFIX=~/.wine32-heartstone WINEARCH=win32 /opt/wine-staging/bin/wine Hearthstone-Setup.exe
5. open winecfg for wine32-heartstone:
env WINEPREFIX=~/.wine32-heartstone WINEARCH=win32 /opt/wine-staging/bin/winecfg.
6. in libaries tab add:
d2d11 and change to disabled,
locationapi and change to disabled.
7. in staging tab enable all options besides the last one.
8. run it and enjoy.
RE: instruction
by urgo on Tuesday December 26th 2017, 12:02
There is a mistake in point 6.
It should be:

d3d11 and change to disabled,
What worked for me
by rodrigo4821 on Saturday November 25th 2017, 20:38
In 4.9.63-1-MANJARO

I installed lib32-libldap lib32-gnutls samba

To install battle.net
wine-2.20 (Staging), staging is important
winetricks corefonts

To pass the game intro
winetricks vcrun2015
How to install on 64-bit Linux 2017-11-13
by puargs on Monday November 13th 2017, 11:50
Here's what it took to install on Ubuntu 17.04 x64 with an Intel graphics chipset on 2017-11-13:

Be careful following these steps - they are intended for brand new installations only. If you already have wine, don't delete your whole .wine folder as in the steps below.

1) install wine staging (wiki.winehq.org/Ubuntu)
2) download winetricks (wiki.winehq.org/Winetricks)
3) run from terminal:
rm -r ~/.wine
env WINEARCH=win32 winecfg

4) (we are now inside winecfg)
set windows version to windows xp
go to graphics tab, uncheck "allow the window manager to decorate the windows"
go to libraries tab, add "d3d11" and edit it to "DISABLED".

5) install battle.net "wine Battle.net-Setup.exe"

6) run from terminal:
winetricks corefonts vcrun2015 forcemono
winecfg
(change windows version to windows 7 and close)

7) make sure wine isn't running - run from terminal (you can skip step 7 if you're not comfortable - just reboot your computer instead, then proceed from step 8):
sudo ps -aux | grep wine
sudo kill 1234 1235 1236 1237

(replace 1234 1235 1236 1237 with the process numbers of any running wine processes found above)

8) FINALLY, open battle.net application and hearthstone and it should run fine.
Fireside gatherings
by Andrew Kis on Thursday October 19th 2017, 3:49
Wine 2.19:
Fireside gatherings work, but my location is wrong. I managed to log into one from home, and get Nemsy Necrofizzle.
Deck copying
by Andrew Kis on Sunday July 2nd 2017, 8:51
The feature crashes my game. Verification, needed.
RE: Deck copying
by jarao on Monday July 3rd 2017, 15:13
This is very new (1 June) so I'm not surprised that there are problems.
A recent patch from 13 June shows this:
* Fixed issues that could prevent Deck Importing from functioning on mobile devices.
* Fixed an issue that could cause a player to get stuck in their Collection Manager after copying a deck.

It's possible there are still more bugs or maybe you checked before this patch.
Personally, I did a simple test (with windows set to xp, 7 and 10) copying and then creating a deck, even edited the clipboard and it all worked.
Black screen fix by forcing d3d9
by Sean Pryor on Tuesday June 6th 2017, 10:29
So, I hit the black screen in game, as well as several other performance issues on wine-stating-2.9. I hunted around the internet a bit and it turns out just like WoW, hearthstone supports a CLI option to force a specific d3d API
us.battle.net/forums/en/hearthstone/topic/20742385137
as expected, -force-d3d9 resolved the issues. Temporary workaround until the d3d11 support gets better
Hearthstone exits after the start.
by Alexey on Tuesday June 6th 2017, 4:21
Since the update introducing the fireside gathering Hearthstone launches, establishes connections to servers then shuts down. I am pretty sure it's due to the network configuration detection. See the wineconsole output before it shuts down:
...
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:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
RE: Hearthstone exits after the start.
by jarao on Monday June 12th 2017, 21:44
I had a similar problem and solved it.
My problem was a crash only when connecting to the server (Europe) where I used "fireside gathering"; the game worked fine when connecting to the other servers.
This problem might be the same as bugs.winehq.org/show_bug.cgi?id=42845 but I used a different solution than suggested there.

Solution:
winetricks forcemono

This sets:
mscoree native
mscorsvw.exe disabled
fixed for me
by davep on Saturday June 3rd 2017, 6:08
same issue, seems fixed when i switch to low graphics quality in game options.
RE: fixed for me
by Spence on Saturday June 3rd 2017, 16:42
I read that elsewhere too but it did not work for me.
RE: fixed for me
by Real Name on Saturday June 3rd 2017, 23:56
Just tried this without any luck - same problem, game remains completely unplayable.

nvidia gpu + driver, arch linux, wine 2.8-staging
Patch 8.2.0.19506
by Oliver Sperke on Friday June 2nd 2017, 5:04
The latest patch from yesterday breaks the game for me. When ever an animation or a popup appears the whole game goes black. Can anyone confirm this behaviour? I tried different settings but nothing seems to work. See i.imgur.com/5I2R8Y6.png
RE: Patch 8.2.0.19506
by Real Name on Friday June 2nd 2017, 5:24
Can confirm. Tested tonight on 2.8-staging in a 32 bit prefix with wine configured as both XP and Win7 and behaviour was reproduced. Strangely it only came up after the end of the first full game I played but I think the update came in during the game and kicked me. Once I reconnected the problem popped up at the end of the game.
RE: Patch 8.2.0.19506
by Brandon Closson on Friday June 2nd 2017, 8:27
I can confirm this happens to me as well. A small workaround I found to make the game 'playable' is to change graphic settings to low.
RE: Patch 8.2.0.19506
by Martin Ramke on Friday June 2nd 2017, 9:01
Also easy to reproduce by hovering over the played card history, which is now completely black before it would just darken/desaturate the board.
RE: Patch 8.2.0.19506
by Spence on Friday June 2nd 2017, 9:15
Experiencing the same. on this patch version. Ubuntu 17.04 w/nvidia 630M (driver v.375.66). I've attempted switching wine versions between v1.9.18 - 2.9 along with various DLL overrides without success.
RE: Patch 8.2.0.19506
by Jordan Metzmeier on Friday June 2nd 2017, 19:22
Same here, looks like the patch is causing hearthstone to use directx11. Tested with with 2.7.
RE: Patch 8.2.0.19506
by Jordan Metzmeier on Saturday June 3rd 2017, 13:54
I also tested with 2.9 and installing dirextx11 via winetricks. I was able to get a game to work, but every time since, I still just get the black screen.
RE: Patch 8.2.0.19506
by Eugene Kee on Saturday June 3rd 2017, 2:27
The same issue. Nvidia 381.22, Wine 2.9.
Someone with AMD GPU with the issue?
RE: Patch 8.2.0.19506
by Martin Ramke on Sunday June 4th 2017, 3:32
When the screen goes black the following gets logged to console:

fixme:d3d11:d3d11_immediate_context_ResolveSubresource iface 0x14ba2c, dst_resource 0x11937968, dst_subresource_idx 0, src_resource 0x8a36cb0, src_subresource_idx 0, format DXGI_FORMAT_R8G8B8A8_UNORM stub!
RE: Patch 8.2.0.19506
by Martin Ramke on Sunday June 4th 2017, 3:58
RE: Patch 8.2.0.19506
by Fer on Monday June 5th 2017, 3:54
I just found a workaround for this issue: In wine config > Libraries, add: "d3d11" and then, deactivate it. This will make the game work again without any issues.
RE: Patch 8.2.0.19506
by Drefetr on Monday June 5th 2017, 4:24
Can confirm that this works w/ Wine 2.7 in a 32-bit prefix: Game works as it did prior to the patch.
RE: Patch 8.2.0.19506
by Fer on Monday June 5th 2017, 4:34
Yeah, sorry, I forgot to say I'm using wine 2.9 staging in a 32bit prefix.
RE: Patch 8.2.0.19506
by Oliver Sperke on Monday June 5th 2017, 7:32
That is so weird because that was the first I tested because of the DirectX11 errors and after the patch it did not work. Now it works!?
RE: Patch 8.2.0.19506
by Spence on Monday June 5th 2017, 11:16
I can also confirm that this works for my config as well.

Ubuntu Mate 17.04, Wine v2.7, nVidia 630M GPU w/ driver v375.66.

If you've already installed 'd3d11' and other things and then cleaned up all those tested configs add it back in and set it to 'disabled'.

The only things remaining in my Wine Configuration -> Libraries -> Existing Overrides are:
-- mscoree - Native
-- d3d11 - disabled
-- dbghelp - disabled
RE: Patch 8.2.0.19506
by Emily Banc on Monday June 5th 2017, 19:55
can also confirm, just added d3d11 - disabled to my config

deb jessie x64, amd r9 285 with amdgpu
Back