Box art - Call of Duty: Black Ops Cold War

Call of Duty Modern Warfare Warzone dev error 5573 fix

It’s another day, another error code for Call of Duty fans. The latest in a long string of unfortunate bugs is dev error 5573, which results in crashes for both Modern Warfare and Warzone. This error seems closely related to Activision accounts, and typically appears during matches of online multiplayer. Here’s everything we know about how to fix dev error 5573.

Call of Duty | How to fix dev error 5573

How to fix dev error 5573 in Call of Duty Modern Warfare and Warzone

Dev error 5573 seems to have numerous causes. It appears most frequently after Call of Duty games have been given new updates. In nearly every instance, code 5573 results in a disconnect or crash during online multiplayer. The only proven way to fix it is to play the game under a different Activision account.

Like so many other error codes, dev error 5573 has not been formally defined. As such, only the developers truly know what it means — and so far, they haven’t really said anything. Nearly everything we know about this error stems from user reports on the Modern Warfare subreddit, the Warzone subreddit, and the Activision support forums.

Most of the reports come from players who were either booted out of online multiplayer or experienced an outright crash. This happens in Call of Duty: Warzone as well as Modern Warfare, and could even affect Black Ops Cold War.

Curiously, several players have reported getting around this error by switching to another Activision account. Some even went so far as to play the game on another PC that hadn’t yet experienced the error. When they played under their own Activision account, dev error 5573 came back. For better or worse, it seems 5573 is a problem closely linked to users’ individual accounts.

As such, the only surefire way to fix dev error 5573 is to play Call of Duty under a different Activision account. Otherwise, this error code seems to appear most frequently after the game has been updated. There’s a chance that whatever bug causes the problem will be fixed in a future patch.