Bungie’s Identity Crisis: Why Pre-Ordering Marathon Installed Destiny 2

The Bottom Line: In a bizarre Steam backend blunder, players who pre-ordered Bungie’s upcoming extraction shooter, Marathon, found their libraries automatically triggered a download for Destiny 2 instead. While Bungie has since deployed a hotfix, the incident highlights a hilarious, yet telling, technical overlap between the studio's legacy live-service giant and its futuristic newcomer.

We’ve seen some messy launches in our two decades covering this industry, but rarely do we see a "phantom" game installation of this scale. For a few hours this week, Marathon wasn't just a highly anticipated revival of a classic IP—it was a delivery vehicle for a game many players were already trying to take a break from. The community reaction was swift, with the prevailing joke being that Destiny 2 has become a "persistent virus" that refuses to leave your SSD.

The Anatomy of a Steam Backend Glitch

The error wasn't just a visual bug; it was a functional forced installation. Steam users reported that as soon as the Marathon transaction cleared, the Destiny 2 client began its massive download. Our analysis suggests this likely stems from shared AppID tags or a misconfigured bundle ID in the Steamworks backend. When you're a studio as large as Bungie, managing two massive live-service ecosystems often leads to these "spaghetti code" moments where the new project accidentally calls upon the old one's assets.

Beyond the main glitch, Bungie had to squash two specific bugs:

• The Forced Install: Destiny 2 no longer hijacks Marathon pre-orders.
• Collector’s Edition Validation: A separate issue preventing CE owners from redeeming their Steam codes has been resolved.

Marathon Launch Intelligence

Despite the technical hiccups, Marathon is currently defying the "extraction shooter fatigue" we’ve seen hitting the market lately. It is currently sitting in the Top 5 best-sellers on Steam, proving that the Bungie pedigree still carries immense weight, even after the internal restructuring and layoffs that plagued the studio last year.

Our Take: A Symptom of the "Forever Game"

We believe this glitch is a perfect metaphor for where Bungie is right now. They are desperately trying to pivot to something new with Marathon’s high-octane, futuristic aesthetic, yet they are still tethered—technically and culturally—to the Destiny engine. This isn't the first time we've seen "code bleed" in major franchises, but it is a reminder that the transition from one flagship to another is never clean.

The real test won't be whether they can fix a Steam download error, but whether Marathon can offer enough Information Gain to the genre to keep players from retreating back to the familiar grind of the Tower. If the game launches with the same level of polish we saw in Halo: Reach or The Taken King, this "virus" meme will be forgotten. If it’s rocky, the jokes about Marathon just being a Destiny 2 skin will become the narrative.

For those looking to dive in, pre-orders are officially "safe" again. Just keep an eye on your storage space—Bungie seems very eager to make sure you have a copy of their FPS catalog, whether you asked for it or not.