hot  /  reviews  /  video  /  blogs  /  forum

4GB Xbox 360 slim owners can't play Halo: Reach co-op

Sep 15 // Jim Sterling
   @JimSterling

Do you have an Xbox 360 Slim? Are you using the internal memory and not the hard-drive? Want to play co-op? Tough shit, apparently. For reasons not known to logical humans, Halo: Reach's co-op is not playable without a hard-drive, meaning 4GB 360 Slim users can't access a much-lauded part of the game.

Trying to access co-op with the cheaper option 360 Slim get the following message: "One or more players do not have the hard drive required for this game type." Using a memory stick doesn't work, meaning that only a hard-drive will let you play co-op. 

Microsoft claims it will be resolving the situation, but quite why this happened in the first place is beyond me. There's no way the company couldn't have known about this since the error message was put in by someone. If Microsoft and Bungie are going to be arrogant enough to call Reach the "biggest shooter of the year", the least it could do is make sure the game's finished properly.

Got a New 4G Xbox Slim? You Can’t Play Halo: Reach Co-op Then [Nukezilla]


 Reblog (or) Blog Reply




Jim Sterling, Former Reviews Editor
 Follow Blog + disclosure JimSterling Tips
Destructoid reviews editor, responsible for running and maintaining the cutting edge videogame critique that people ignore because all they want to see are the scores at the end. Also a regular f... more   |   staff directory

Get more destructoid:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

 Setup email comments

Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.
advertisement:




Back to Top