Call of Duty: Modern Warfare 2 has launched and although it went on to make a staggering $800 million in three days, the game hasn’t been without its issues. Like many other new games, bugs are expected during the first few days and even weeks of release and CoD MW2 is no exception.

The game’s initial post-launch came with its own issues which were mainly crashing and despite several updates to fix the crashes and other related bugs, some players are still encountering issues with CoD MW2 with the latest being a Dev Error 356. So in this guide, we’ll be showing you how to fix Dev Error 356 for CoD: MW2.

How To Fix Dev Error 356 for COD: MW2

Despite the developers stating that the game’s latest update which was released on November 4 should “provide additional stability in terms of crashing”, sadly this is not the case as a number of players have reported being kicked out of matches due to Dev Error 356.

This new error can prove very frustrating especially since it’s not something you can control or even predict when it’ll happen. It could happen when you’re on a fantastic killing streak in a match and cause you to lose the match entirely. And although some sites have suggested that the Dev Error 356 is only affecting players that change their language packs, that doesn’t seem to be the case as even those who haven’t changed their packs are being affected as well.

Right now there is no working way to fix the Dev Error 356 in CoD MW2, at least not from a player’s end. The issue seems to come from the developer’s side of things so players will have to be patient until Infinity Ward fixes the problem.

It doesn’t usually take long for Activision or Infinity Ward to acknowledge a problem and release an update to fix it, and since this is a relatively new title with many affected players, a more permanent update will be on the way soon enough.