How to fix the “player is in a different version of Overwatch” error in Overwatch 2

Get on the same level.

Image via Blizzard Entertainment

Overwatch 2 is best enjoyed with a group of people you can rely on. A team that can accurately communicate together can often turn the tide of battle in their favor. That is why it is great to play Overwatch 2 with friends. However, you may run into an issue where when you try to invite them, the game lets you know that they’re playing on a different version of Overwatch 2 than you. Here is how to fix that.

Related: What are Legacy Credits in Overwatch 2, and how do you get them? Answered

How to fix the “player is in a different version of Overwatch” error in Overwatch 2

If you are trying to get into a party with someone in Overwatch 2 and a message pops up saying player is in a different version of Overwatch, that means that likely one of you needs to update their game. While most of the time you should get a notice to update your game when one is available before playing, odd things can happen. Both you and them should start by closing the game down and checking to make sure you are on the latest version of Overwatch 2.

  • On Nintendo Switch, press the plus button on the Overwatch 2 tile, select Software Update, and choose Via the Internet.
  • On PC, click the gear icon next to the play button in Battle.net and select Check for Update.
  • On PlayStation, press the Options button on the Overwatch 2 tile and select Check for Updates.
  • On Xbox, open My Games & Apps, scroll down to Manage, and click Updates.

If none of the above methods have revealed an update for your game, we recommend fully shutting down your system and restarting it before trying again. You might also want to check to make sure that there are no issues with the party system in the game through the Blizzard Customer Support Twitter.

Another possible method is to send an invite through the game’s console commands. Bring up the chat and type /invite [their Battle.net tag]. To join them, type /join [their Battle.net tag].

If you are playing at launch, this is a common server issue and will be resolved with time.