According to the Blizzard Hearthstone Technical Support Forum, many people are experiencing this issue. I tried posting this solution on that forum, but my posts kept getting taken down [edit: the post has been restored!].
I have only tested this solution on Windows 10, but it may or may not work on Windows 7 and 8.
Lately, I noticed that Hearthstone.exe was consuming more system resources and was causing programs that were running concurrently to lag. I also noticed that Hearthstone.exe would consistently hang when closing. It seems that these symptoms were both introduced with the "Windows 10 Creators Update".
The following are the steps to address this issue on Windows 10 (steps are different and may or may not work for Windows 7 and Windows 8):
Before beginning, run "Windows Update", then search for and install the latest update(s). You may need to restart the computer after installing update(s) before a search yields additional result(s). (Search => Install => Restart => Repeat until there are no additional updates available.)
Close "Hearthstone.exe".
Right-click on the "Windows/Start Button".
Click on "File Explorer".
Copy and paste "C:\Program Files (x86)\Hearthstone" (without quotations) into the "address bar", and then press "Enter".
Click/Check the "box" next to the words, "Override high DPI scaling behavior.".
(This option is only available with the "Windows 10 Creators Update".)
(For Windows 7 or Windows 8, try checking/clicking the "box" next to the words "Run this program in compatibility mode for:", then click on the "drop-down menu" immediately below and select an earlier version of Windows, then skip to "Step 10".)
Ensure that the "selection" in the "drop-down menu" under the words, "Scaling performed by:", is set to "Application".
Click "OK".
Open Hearthstone.
After I took these steps, Hearthstone now quits without hanging (sometimes it hangs briefly, but it eventually closes; I tested this many times), and programs running concurrently are no longer lagging.
* Always play aggro crew * Accept all friend request crew * Don't mind/care if they rant crew * Find it funny that they rant crew * Google translate non english rant crew * Most friends on my friends list are people I've beaten crew Join my crew guys
I don't have the "Override high DPI scaling behavior" toggle on my Compatibility tab. There's a "Disable display scaling on high DPI settings" which is currently unchecked. I'm running Windows 10.
^Same here. Just posting to be notified if there is an update on the matter. While it is annoying the application closes after a bit for me much like SmartCardTerminal's.
if you're experiencing this problem even though you do not have the Creators Update, then you may have a different issue
perhaps try disabling streaming in the battle.net/blizzard app options
try visiting the blizzard hearthstone technical support forums, there is a stickied thread there relating to this issue that lists other possible solutions, although with varying success
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
According to the Blizzard Hearthstone Technical Support Forum, many people are experiencing this issue. I tried posting this solution on that forum, but my posts kept getting taken down [edit: the post has been restored!].
I have only tested this solution on Windows 10, but it may or may not work on Windows 7 and 8.
Lately, I noticed that Hearthstone.exe was consuming more system resources and was causing programs that were running concurrently to lag. I also noticed that Hearthstone.exe would consistently hang when closing.
It seems that these symptoms were both introduced with the "Windows 10 Creators Update".
The following are the steps to address this issue on Windows 10 (steps are different and may or may not work for Windows 7 and Windows 8):
After I took these steps, Hearthstone now quits without hanging (sometimes it hangs briefly, but it eventually closes; I tested this many times), and programs running concurrently are no longer lagging.
Report back here if this works for you!
Or don't close Hearthstone.
Er... I meant, thanks for the tip OP.
=)
* Always play aggro crew
* Accept all friend request crew
* Don't mind/care if they rant crew
* Find it funny that they rant crew
* Google translate non english rant crew
* Most friends on my friends list are people I've beaten crew
Join my crew guys
oh my god you're right. i must repent for ever closing hearthstone. hearthstone is life
not sure if it helped you, but if it did, you're welcome! i'm so happy i could help!
Thanks for the info! I've been having this problem on both my desktop and laptop. Will try the fix when I get home this evening.
How long does it normally get stuck for you? For me it's about 20 seconds so i guess i don't have an issue? Allthough it used to close instantly.
oops, i assume you did it correctly, but i just fixed the instructions to include "click on Properties" after right-clicking on Hearthstone.exe
if it doesn't work for you, then perhaps next week (tuesday?) blizzard will issue a fix.. hopefully!
I don't have the "Override high DPI scaling behavior" toggle on my Compatibility tab. There's a "Disable display scaling on high DPI settings" which is currently unchecked. I'm running Windows 10.
^Same here. Just posting to be notified if there is an update on the matter. While it is annoying the application closes after a bit for me much like SmartCardTerminal's.
So you thought only Mage had an exodia combo eh
if you do not have this option, then you may not have Windows updated to the most current patch with the Windows 10 Creators Update
thx. that update recently arrived to my laptop. Downloading it
Weird, worked for me yesterday but not anymore.
It does seem to work to activate compatibility mode for Windows 7, though. EDIT: This doesn't work anymore, I don't know what's happening xD
if you're experiencing this problem even though you do not have the Creators Update, then you may have a different issue
perhaps try disabling streaming in the battle.net/blizzard app options
try visiting the blizzard hearthstone technical support forums, there is a stickied thread there relating to this issue that lists other possible solutions, although with varying success