Can't play due to mandatory, yet unavailable update

Technical Support
1

When I launch WC3 I see the closed gates in the game and this messages shows up:

“A new update is available for download. Please download it now. ‘2.0.4.23745’”

After clicking on download the game closes and nothing happens. If I select “Check for updates” next to the play button of WC3 in the Battle.net launcher, then it does the check and writes: “Up to date”. The current version is 2.0.4.23556.

I tried it yesterday at around the same time with the same result.

After it occurred again today, I reinstalled the battle.net client and WC3, but the same download prompt is shown in-game and the same “up to date” message when checking for updates.

I’m playing in region Europe on Win11 25H2 if that matters. I also submitted it as a bug.

Do you have any ideas how to solve that problem?

2

Just wait a little bit few hours, then open again Battle Net and let it update.

3

you don’t have the editor open do you

4

There appears to be some glitch preventing the download from actually starting for many users. Open the task manager and terminate everything that is related to bnet, warcraft etc. And try again. Or “have you tried turning your PC off and on again”.

5

I tried to play SC2 instead, but got a “Version Mismatch” prompt when launching it, without any available update from the Battle.net client. Same problem, different game. I can’t remember having changed anything when I played WC3 a few days ago. But I have read, that there is a new WC3 update, and from other sources than battle.net, that there’s a new version of the Battle.net client .

The little amount of views here were quite obvious, that it is my individual problem.

If others or my future me have to deal with it (again), I eventually found a solution after stumbling over an eight year old post on reddit about the version mismatch for SC2.

That worked for me:

  • Uninstall the battle.net client from the Windows settings → Apps.
  • Delete all battle.net folders in C:\ProgramData\. These were: Battle.net, Battle.net_components, Blizzard Entertainment.
  • Delete the same folders in C:\Users\yourusername\AppData\Local and C:\Users\yourusername\Roaming.
  • Restart your computer.
  • Then install the Battle.net client again.
  • After that, I got the WC3 update and could play the game.

I mentioned in my previous message, that I reinstalled Battle.net and WC3, but I did so without deleting these folders and without a system restart. The system restart was necessary as the new installation of the Battle.net client would get stuck at some percentage instead of completing.

6

Why is this marked as a solution? Sure, a clean re-install should work.
For me, it also worked to leave Battle.net open for 3 minutes, let it update, and then it was fine.

7

???

That’s quite a daft question.

Is your solution the correct solution? The only solution? Is it inconceivable that your reality isn’t everybody’s?

:roll_eyes:

1 Like
8

I disagree that it’s a “daft question”. It’s valid to ask why a specific post is marked as the solution when multiple fixes are mentioned in the thread.

9

Because only one can be marked at a time. O.o
That’s as daft as it gets.

10

it’s a daft question because the answer is obious. The original poster marked it as a solution because it worked for them. No one said it was the ‘best’ or ‘only’ solution, only that it was a solution. and that’s all that matters really.

11

a Re-install seems like the most likely solution while others can be found, this is probably the best method.

I’d tried waiting a day for a similar issue and nothing fixed it minus a re-install.

12

I am trying everything but the issue still exist, I can’t start it even when I purchase standard Reforge version?
Please I really need support on this.

Edit:
After the third times clear and install like the solution, it’s seem to fixed the issue.
I have to question Blizzard for optimize problem.

13

No need for it to become personal. The point is simply that different users may have different working solutions for the same “version mismatch” issue.

14

That’s not how you presented it when you asked why someone else’s solution was recognized instead of yours.

15

Leviathan, I’m addressing the technical point that multiple solutions can work for the same issue.
I’m not questioning anyone personally, please focus on the discussion, not on me.

16

Sorry Cat, once you enter a thread what you say is fair game, especially when your contribution is questionable.

And as you’re fully aware, you don’t decide how people post. That’s Bliz’s jurisdiction, not moderation wannabes.

17

Point already clarified. This is a technical discussion about possible solutions.
I’m not responding to personal commentary or off-topic framing.

18

YOU’RE the only who does that, and have the audacity to tell people how to post in the process.

Perfect. Hopefully you keep your word going forward.

19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.