Basically as the title says. When I close the game, the play button goes straight to UPDATE. Nothing is downloaded, nothing is updated, no change to the build number…
Been doing this for like 3 months now on ALL versions.
Sometimes it will even say something broke restart Battle.net
Ive already done fresh installs of all games and the client. Happens on MAC and on PC. My guild says it happens to them too for some reason.
It’s likely an issue with broken folder permissions.
can you elaborate? Ive reinstalled the launcher numerous times, and it still does it.
You’re reinstalling the wrong app. The game needs an update, not the Bnet launcher (as you mentioned the Play button becoming an Update button). Run Scan & Repair on the game or reinstall it.
Ive reinstalled the whole game due to errors with professions tabs, nothing changed before and after that.
This is because many people are experiencing issues with prof tabs and we have tried everything to get them to work in game… My games (all of them keep trying to update. even after reinstalling the game and launcher.
Are you using an External Harddrive? I’ve been having the exact same issue since I moved Wow to my External harddrive a few months ago. I have hearthstone installed on my internal SSD and it does not have this issue.
Generally, externals are very slow since they rely on the USB, the motherboard, and then off to the CPU and GPU.
No, im not. On my Mac Mini, I am using the stock Storage SSD that comes with the system which is supposed to be pretty darn good. On my PC I have NVME that I am using as my primary HD.
I again this morning ran Scan and repair, and uninstalled the launcher and game, and it is still doing it. Now, after running the scan a repair I have a new error that will pop up and require a system restart to get past and that is:
“We’re having a problem transferring data. Please check your internet connection just in case and try again.”
And, clearly this only happens when I am relogging or was not logged.
I want to reiterate this is not a internet issue, it has to be a client / launcher issue. Especially if I am seeing the same error on two separate types of machines running two difference OS