Heard about false bans, never thought it would happen to me. Let alone be rejected by Activision on a automated support ticket that clearly was sent too fast to even be reviewed.

I pre-ordered after playing the Beta in September since the game seemed alright. Then release day happens and I play the game for only 23 hours and then my game crashed, after my game crashes, I log back in to MW2 and I'm BANNED. I have not once cheated in a Call of Duty title and have been playing Call of Duty religiously since COD 4 on Xbox 360.

So after this happened and I was rejected on an appeal by Activision the first time. I read up about how there's false detections due to Motherboard Software etc so I decided to Re-Install Windows with nothing but my Logitech GHUB and my Lian-Li Fan Software.

Welp, 2-3 days go by and AGAIN I have been banned on the SECOND copy of this game. On a fresh Installation of Windows.

I quit Warzone and I quit streaming Warzone due to cheaters, and was waiting to come back to Call of Duty at a later state in time when there anti-cheat was better, and when there was a new Call of Duty title out.

Guess I'm done with Call of Duty for good now and they'll never get another penny from me as long as I live. So I am now out ( $79.99 x2 ) and highly quite frankly upset I lost valuable time as well trying to progress on the game on both accounts. My KD on the account was also average since I haven't been playing COD enough to be a GOD so I just don't understand what I was banned for, let alone a detailed reasoning on why I was banned.

Welp, GG gamers. Guess I won't be playing this COD micro-transaction franchise ever again. You release an incomplete game, 70% finished and are banning your most loyal players and most loyal customers to the franchise. Last straw for me, and I hope anyone else who was banned for NOTHING takes their hard earned money elsewhere.

I want to add this note, never have been banned from any Call of Duty title except for Modern Warfare 2 2022. Never banned on MW2019 or Warzone so NOPE couldn't be the issue either.