still having the same issue
Well guys i did something that works for me… i have two disk’s on my pc disk C that is small but have all my operative system and another one the disk D with more memory… i just move my wow carpet from D to C and the game fix by it self… now im playing like always.
I used the work around changing hotfix file to read only and it worked for me. No more freezing for a second when turning in quest, killing a rare, opening chest etc. Pretty unbelievable they haven’t fixed this yet. I laughed my butt off at the rogue stabbybabys comment. Yeaaaaaa sure you did.
I am experiencing the same issues and it frustrates me every single day.
However, I keep telling myself that if this issue is an easy fix, Blizzard would have fixed it days ago.
The workaround is just a bandaid. Blizzard might have discovered much more related issues that might require a whole lot more coding fix than just the bandaid fix.
So have some patience and more if needed. I rather Blizzard completely fix the underlying issue than to keep applying simple but bandaid fix everytime and later down the road, the core issues cause a lot more issues than our current problem.
I’m not being the devil advocate here, but speaking as a Software Quality Engineer, for simpler that the fix and the bug looks for us, hundreds of features, trackers and mechanics can be linked to the issue, making it hard as hell to fix even though the users found a quick-win way to play without it.
It can be linked to loggers as the partial fix suggests, it can be linked to bot detection system, and other things that we have no idea that runs server-side writing stuff client-side.
Always remember the complexity of WoW mechanics and all data the game provides that has to be gathered by the development team…
Too bad this is still an issue, but it is what it is. Meanwhile, the temporary fix (as mentioned in this thread) works brilliantly. Just remember that you have to launch from the wow.exe and not from the BNET app. I’m sure it’ll get fixed soon. Y’all hang in there.
Still not fixed just like as everyone here is reporting.
The fix to ‘‘read only’’ don’t work for me anymore. Trying to launch the game from the exe.file, instead of the battlenet app, just boot me instantly when I manually type my password after hitting login(BLZ51914001).
I’m really getting angry and …anxious for my pc.
You may have to temporarily revert the changes. Launch Bnet app and let it run an update/hotfix. Close Bnet, then redo the changes. I’ve had to do that.
Thats probably because there was an update yesterday. You should login on Battlenet, update the game and do the workaround again after this. What is happening with you is normal when your client is not updated to the last version of the game and you try to launch it from the exe.file.
It’s sadly all up to date… /sigh.
Waiting for the real fix that will really work until then.
You could try to restart your PC, login on Battlenet, update the game if theres one, after that you do the workaround and launch it from the Battlenet instead of the exe.file. If that does not work I have no clue.
So, I tried the workaround (setting the hotfix file to read only) and launched the game from the .exe file. It runs smoothly. Hope they find a official fix soon™.
13K plus views on this thread. Lets keep up the pressure until this issue is fixed. That is the best thing we can do. The more eyes, the more resources they will divert to fix this quickly.
still no fix for me. oct 2 2019
If I find out Blizzard’s been developing new content instead of fixing the current content I’m gonna be angry.
The war campaign is over. That one raid can wait a month if it means better quality control.
I fear they’re messing with us at this point. Giving us false hope only to crush our hearts.
Funny how this bug is still happening even when we are so close to Blizzcon, imagine how bad would be to Blizz reputation if they were asked how this bug could harm our PCs during said event.
“Do you guys not have SSDs?” or something like that.
“I’d like this bug fixed soon.”
“You THINK you do! But you don’t.”
Any chance this will be fixed soon? It’s really disruptive when doing multiple quests.
I literally just uninstalled and reinstalled the whole game and it is still happening.