Got a New 4G Xbox Slim? You Can’t Play Halo: Reach Co-op Then
Microsoft’s newer, slimmer Xboxes that don’t come with the 250GB hard drives (but do come with 4GB of internal memory) cannot play certain Halo: Reach gametypes because of an apparent lack of storage available to cache levels and other game code.
Tests by Nukezilla show that the Xbox slim 4GB brings up an error message when attempting to join a co-op campaign mission.
Surprised? Well you should’t be, it’s a known feature (not a bug), as is apparent by the issue being the number one FAQ on Halo: Reach‘s Xbox page.
Q1: The error “One or more players do not have an Xbox 360 Hard Drive. An Xbox 360 Hard Drive is required to play co-op on Xbox LIVE or system link” occurs when I try to play. Why?
A1: One or more players do not have a certified Xbox 360 hard drive attached to their Xbox 360 console. Some multiplayer aspects of Halo: Reach require an Xbox 360 certified hard drive.
This means that console owners who bought the game and have a brand new slim 4GB Xbox have a huge chunk of the game’s functionality missing. A forum post on Bungie.net dated from back in August describes similar problems with Halo 3: ODST, with the issue left unresolved.
So to be clear:
- This only affects the new slim 4GB Xbox 360s.
- Adding extra storage through USB sticks etc. doesn’t seem to fix the problem.
- Standard multiplayer isn’t affected by this issue.
- It’s only a problem on co-op, although we’re currently trying other modes.
- It appears to be a problem on every Halo game. We’ve seen reports saying there’s issues with Reach and ODST.
- If you have a 4GB Xbox Slim and you’re in the UK, you’re going to have to wait until the end of September to the be able to buy the £80 hard drive you need.
- US gamers can get a 250 GB hard drive from Amazon for $129.99 here.
Update: Amusingly the UK retailer Comet are selling an Xbox 360 4GB Slim bundled with Halo: Reach.
Update 2: Brett’s been able to reproduce this on a US Xbox 360 4GB Slim with identical results.
Update 3: Eurogamer contacted Microsoft this morning who responded by saying that “We are aware of the issue and are quickly working to resolve it.” There’s no word when that will happen, but at least they’re doing something.