I was sure that I was the only one with this problem, welp, good to know that the addons aren’t screwing wow up, I hope they fix this fast.
Not necessarily. I prefer to just do the read only workaround everytime I login on BN. I usually close the game together with BN anyways. As long as you launch the game before the update button appears the Unlimited Workaround Works.
Happens to me too since the last patch, every time I turn in a quest, get experience, end a flight path, and any time I kill an enemy. My machine sits comfortably at 90+ FPS even in the most taxing situations in WoW or any other game I’ve played, and the temperature never goes above 32c. But ever since that last patch, I’ve been getting 2-3 seconds’ worth of freeze after every one of these events. This is without any addons, after resetting my UI, after trying a repair install, and in any zone, on any character, with or without war mode.
Yes actually. Have you tried it? If you click World of Warcraft Launcher.exe, you get sent to the BNET app. Where it does the update check to fix permissions. You still pass login info this way. If you click Wow.exe from the _retail_ folder, you can start the game bypassing the BNET app, but must enter your credentials.
Right, but as my comment said, I don’t want to have to open the properties to do all this manually. Running a little script is faster. Since you’re having to do this every-time.
So now i’m getting paranoid. Every time i turn in a quest it sounds like my pc is going into overdrive. I’m afraid if this keeps up it might become serious.
Can we please get a fix for this? it’s approaching two weeks now and i’m not sure if it’s worth risking damage to my computer.
1 Like
I could have used your script if it changed the files to read only with 1 click. I’d still launch from BN anyways. I understand its the same effect tho, I just dont want to mess with the permissions if I can.
Just to educate, that’s where your understanding breaks down. The read only tick box is a permission. MS just put it there for the sake of ease so people don’t have to use the Security tab.
Read, Write, and Execute are all permissions every OS has. By ticking that box, you’re just marking the file permissions as read-only to all groups (Denying the ability to write). Since you can’t modify the Read only tick box from a command prompt, you have to use traditional permission commands. Which is exactly what my script does. It denies certain groups the ability to Read, Write, or Execute it.
No, they aren’t going to refund game time and I don’t necessarily think they should. In fact, I’m not 100% confident in this, but I can’t recall a time when they have ever credited time on accounts because of issues like this. It just comes with the territory. It’s very untrue that I am “blindly white-knighting”, as you say; I’m just not losing my mind over it. I’m using the temporary fix (which works brilliantly) and playing as usual.
I used to play on a Mac (I know…) and this kind of junk happened more often than not. It sucked then. It sucks now. But hey, at least there’s a workaround.
1 Like
Blizzard, if you are reading this:
People are having bad performance problems with the game due to LOG FILES.
You haven’t fixed the problem in two weeks.
Just disable logging to those two files until you fix it. This cannot be hard to do if you handle logging in any way remotely like any other developer.
Then again you’re leaving your file stream open with the files locked all session which is generally considered bad form, so maybe I’m wrong.
3 Likes
Nah, people are entitled to their opinions and their frustrations are valid. I just don’t get the extreme responses when there’s an available workaround.
1 Like
I hear ya, I didn’t do the fix because I’ll forget to undo it once it’s fixed and I don’t want any more issues, so for now I’ll just deal with it lol
Amayna you can do the work around and when you open battlenet it will undo it
1 Like
Yeah, as stated below, all you have to do is run the game via BNET and it’ll fix the files. That’s why in order to use this particular workaround, you have to start WoW straight from the .exe file.
1 Like
Thanks 
i thought the hotfix from today was going to fix it… looks like blizz fails yet again.
2 Likes
Let us take some bets. When shall this actually get fixed? Next Tuesday? The following Tuesday? 8.3? Next expansion? HELLO?
5 Likes
Don’t hold your breath.
They’ll get it fixed - lets just be patient. It’s not all doom and gloom, at least we have the work-around that seems to work great.
Keep that Orc chin up pal!
I understand, but I still prefer doing it my way. Thanks.
They have like 4 weeks to fix it before this bug ends being asked at Blizzcon 
1 Like
I’ve got 5g says it takes them 2 more weeks 
1 Like