Small lag on quest turn ins and WQ completed

Indeed it fixes the issue but still there is some lag here and there but at least the issue with the quests is ok now with this workaround.

Blizz are fixing the fix, if you deny the access as suggested the log is redownloaded and over written

Permission changes made to these files are reverted if you run the battle.net launcher.

The game didn’t cause any damage until now, hence I won’t use the unoffical fix. It might cause some overdrive or something… I have enough to pay already.

Blizz generally release a fix when it is wednesday, I will be waiting.

TFW you miss the entire week of TW because the game hard-freezes a lot

Does it freeze that much because I could easily complete a +11 key with my warrior. I suppose it is on different level for everyone, mine is still disturbing but it also doesn’t make the game unplayable.

Launch WoW from the program files and it works fine, just don’t open Battlenet

2 Likes

The unofficial fix won’t cause any problems, it’s just a permissions change, Blizz are only advising against it as a general precaution but it won’t ‘damage’ anything.

I know dude, it is just a procedure stuff. So they can say “we warned you” and they probably do this for every editing related to the game files. Thanks for the answer tho.

1 Like

I have same lag on arenas on raids and m+ since 8.2.5 I try to change resolution and turn off addons also reinstall game but didn’t work my friends also have this problems

You must be kidding. If you [snip] up we don’t have to move anything anywhere or do anything. Stop looking for excuses and lame [snip] fixes that don’t work. If this many people are telling you this is happening, you can’t be telling people that they are like [snip] using wow on a regular HDD and [snip] just for your own god damn convenience, you do realize that people are tired of your [snip]???

3 Likes

I’ve edited your post Helliana to make it a bit less code-of-conduct-violating, be sure to keep the Code of Conduct in mind in the future

As a reminder to folks in this thread, we are aware of the problem, and a fix is being worked on by our developers. There have been some workarounds shared that can help as short-term improvements while that fix is developed, but the advice is just that, short-term, while a more permanent fix is in progress

is fix gonna come out anytime soon? do i have to be scared of what i read about dmg hard drives? should i try the fix ppl say at hotfix file and open game just from folder? is 5 days now…

They may not recommend that fix, but other option would be not playing. in my opinion. Only annoying thing is that this has to be done every time you open wow client after initial shut down.

It should work shutting down the bnet client before launching from the directory or make a copy of your game which will be disconnected from the bnet client and play from that so the client doesn’t restore the file every time you exit.

Ah. I have to try this. Because I normally have had bnet client running (I have whole bundle of these :P)

I say again i am not mad at Blizz for issues happening (stuff happens to all of us), and I am thankful for community offering those detours. You are Elune’s sent here :blush:

Same here, very annoying but hoping for a fix soon (-:

I was on US forum too and saw custom fix how they do, but its not working for me. Then i think about it and what they doing. It comes shrt after that.
I was changed properties to READ ONLY of Hotfix.log file which is in World of Warcraft/retail/Logs folder. Try this. Working for me. Have done it 10 min ago and come here to spread the word. Thanks for US players for BIG hint.

1 Like

Just remember if you set your file to read only, whenever you play with your battlenet client open, when you exit the game the client will restore your log permissions to default and you most likely have to apply the changes for every time you want to play. So make sure you do not have your client running in the background.

Anybody who can tell me how to do this in Danish? I found the Hotfix.log, but I am unsure how to proceed next on my Danish client.