The Warzone Dev Error 5573 is one issue that many players seem to be running into on both console and PC that forces their game to crash, or not even load up at all.
For those looking to spend less time on the error screen and drop back into Verdansk '84 and Rebirth Island, here's what you can do to fix the Warzone Dev Error 5573.
How to Fix Warzone Dev Error 5573
On the official Warzone developer Trello Board, Dev Error 5573 is actually one of the issues that Raven Software and co. list as already have had a fix released for, and that they are continuing to monitor it.
According to its description, various issues were causing players to experience their game crash, including, but not limited to, the CARV.2.
Additionally, on the Call of Duty Season 4 Reloaded patch notes, the devs listed that they "fixed several issues that resulted in players crashing due to Dev Error 5573."
As such, for those unfortunately still running into the error, it seems that it stems from having a specific weapon or blueprint in their custom loadout. Players in the community have reported that removing the MG 82, CARV.2 and even a specific Hauer 77 blueprint from their loadouts did the trick for them.
If this doesn't work, feel free to try to:
- Check Activision Support's Twitter to see if they've released a new Warzone patch, are investigating the issue or are performing server maintenance
- Close the application, ensure that Warzone is fully updated to the latest patch and start the game back up
- Clear Warzone's cache from the PlayStation, Xbox or PC