How a Marathon Pre-Order Accidentally Installed Destiny 2

When players head to Steam to pre-order a new game, they usually expect one of two things to happen: either nothing downloads until launch day, or a clearly labeled pre-load begins. What almost nobody expects is an entirely different game quietly installing in the background. That is exactly what happened when some PC players pre-ordered Marathon, Bungie’s upcoming extraction shooter, only to see Destiny 2 begin downloading instead.

This odd bug quickly caught the attention of PC players, Destiny fans, and industry watchers. It was funny, confusing, and a little bit revealing about how digital storefronts handle complex bundles and entitlements. Bungie has since fixed the issue, but the story behind it is worth unpacking.

The Glitch: Pre-Ordering One Game, Installing Another

The issue surfaced when players who pre-ordered Marathon on Steam noticed their client immediately kicking off a large download. Given that Marathon is not out yet, some initially wondered whether they had stumbled into an early technical test or pre-load.

Instead, they discovered that Steam was actually installing Destiny 2. Players who did not previously have Destiny 2 on their PC suddenly found the looter-shooter taking up space on their storage drives, triggered solely by the act of pre-purchasing Marathon.

What Players Actually Saw

• Steam library entries for Destiny 2 appearing or being re-queued.
• Automatic downloads starting without any explicit confirmation dialog for Destiny 2.
• Confusion over whether this meant bonus access, a beta, or a mistake.
• Jokes circulating on social media about Bungie “making Destiny 2 install itself.”

The situation quickly spread via screenshots, short clips, and posts on community hubs. While some were annoyed by an unexpected multi-gigabyte download, many treated it as a bizarre and mildly hilarious accident.

Bungie’s Response: Quick Acknowledgment and Fix

Bungie addressed the incident publicly through official channels. The Marathon account on X (formerly Twitter) confirmed that the development team had identified and resolved the bug that triggered Destiny 2 installs after a Marathon pre-order. According to Bungie, the behavior was unintentional and should no longer occur for new purchases.

In parallel, the studio also referenced another issue related to Steam activation for certain Marathon editions, indicating that multiple backend and storefront entitlements were being adjusted. That broader set of updates likely shared the same general root cause: Marathon’s complex tie-in with existing Destiny 2 content.

Valve did not publish a separate statement, but Bungie’s messaging and the disappearance of the behavior from user reports suggest that the fix involved both Bungie-side configuration and Steam-side entitlement logic, which is typical for integrated bundles and DLC on the platform.¹

Why Destiny 2 Was Involved in a Marathon Pre-Order

This was not a case of Bungie secretly giving away Destiny 2. The more mundane explanation lies in how the pre-order was structured. Marathon pre-orders on Steam include a Destiny 2: Marathon Pack, a cosmetics bundle that grants Marathon-themed items inside Destiny 2.

Because those cosmetics are designed to be used in Destiny 2, Steam and Bungie needed a way to associate the entitlement with the base Destiny 2 application ID. That connection appears to be the core of the glitch: somewhere in the configuration, granting access to the Destiny 2 cosmetic bundle was treated as a trigger to install the associated base game for users who did not already have it installed.

How Bundled Content Can Confuse a Storefront

On digital platforms like Steam, content is typically structured around a few technical concepts:

• App IDs: The base game or main application (e.g., Destiny 2) has a unique identifier.
• DLC/Packages: Cosmetic packs, expansions, and bundles are linked to that base app ID.
• Ownership vs. Installation: Owning a license for an app is separate from whether it’s installed on your device.

In a perfect setup, buying a cosmetic bundle for Destiny 2 gives you ownership of the DLC, but it does not initiate a download unless you specifically request the game itself. In the Marathon pre-order case, the entitlement logic seems to have crossed that line, treating ownership as a cue to install the base game—an outcome that surprised players and irritated a few with limited bandwidth or storage.

Community Reaction: Humor, Memes, and Mild Frustration

Because the bug was relatively harmless and quickly resolved, the wider response leaned heavily toward humor. The idea that Bungie’s previous live-service epic would “force” its way back onto PCs when people were trying to move on to Marathon fit neatly into a meme-friendly narrative. Many players joked as if Destiny 2 had become a clingy ex, popping back into your life the moment you tried something new.

At the same time, some users expressed legitimate annoyance at:

• Unwanted large downloads eating into data caps.
• Storage space being used without explicit consent for that game.
• The possibility of similar bugs affecting other bundles, especially for players with slower connections.

The overall tone, however, remained relatively light, especially compared with more serious issues such as account lockouts or progress loss that can sometimes accompany live-service changes.

What This Reveals About Digital Storefront Complexity

Under the surface, this incident highlights how complicated modern game ecosystems have become. Between cross-game cosmetic tie-ins, pre-order bonuses, battle passes, and live-service expansions, a single purchase can involve multiple entitlements across different apps.

Industry reports and developer commentary over the last decade have repeatedly noted that the shift to digital, and especially to live-service models, has increased operational complexity for studios and platforms alike. Platforms such as Steam provide extensive tools for bundling and DLC management, but they also rely heavily on developers to configure packages correctly.²

Implications for Player Trust and UX

Even a lightweight glitch like this can chip away at player confidence if it becomes part of a pattern. People expect digital purchases to behave predictably: what you buy should be what gets installed, nothing more. When that contract is broken—even in a humorous way—it raises questions about transparency and control.

Key UX Concerns Raised by the Bug

• Clarity of Downloads: Players want to know exactly which game is being installed and why.
• Granular Control: The ability to opt out of auto-installs for associated titles is important, especially when data caps and SSD space are involved.
• Predictable Bundles: Cross-game rewards should be clearly labeled so players understand when another title is required or affected.

Broader digital distribution research has highlighted that perceived control and transparency are central to user trust in online services and platforms.³ While a one-off mistake is unlikely to drive players away from Steam or Bungie, it underscores why UX and backend logic must be tightly aligned.

Marathon’s Context: A New Extraction Shooter, Old Legacy

Marathon is not just another release in Bungie’s catalog; it represents both a return to an older IP name and a step into the increasingly crowded extraction-shooter space. The title is planned for PC and modern consoles, with an emphasis on competitive runs, squad-based play, and persistent progression.

Bungie has framed Marathon as a key pillar in its future lineup, especially after its acquisition by Sony and the ongoing need to diversify beyond Destiny 2’s long-running lifecycle.⁴ The decision to link Marathon pre-orders with Destiny 2 cosmetics fits into a broader strategy of cross-pollinating audiences, where fans of one live-service game are encouraged to try another through rewards and themed gear.

What Players Get from the Destiny 2: Marathon Pack

While item names and visuals are subject to change, the pack is designed to:

• Provide Marathon-themed cosmetics inside Destiny 2.
• Highlight Marathon’s visual identity to existing Destiny players.
• Create a sense of continuity between Bungie’s past and future titles.

That same entanglement is precisely what paved the way for this bug. The more interconnected live-service ecosystems become, the more closely studios and platforms must monitor how entitlements, ownership flags, and install logic interact.

What Players Should Do If They Were Affected

With Bungie reporting that the bug has been fixed, future pre-orders should not trigger Destiny 2 downloads. If your system was affected earlier, there are a few straightforward steps to take:

• Check Your Steam Library: Verify whether Destiny 2 is installed or queued.
• Cancel or Pause the Download: In the Steam Downloads panel, stop any unwanted Destiny 2 installation.
• Uninstall If Needed: If the game completed its download, uninstall Destiny 2 from the library to recover space.
• Review Auto-Update Settings: Consider disabling auto-updates or auto-install for games you don’t intend to play soon.

If your purchase entitlements for Marathon or its associated cosmetic items appear incorrect, Bungie directs players to its official help site and support channels, which include detailed troubleshooting guides for Steam-related issues.⁵

Lessons for Developers and Platforms

From a development and platform operations perspective, this incident offers several practical takeaways:

• Test Edge Cases for Bundles: QA should include scenarios where users do not own the linked base game, especially for cosmetic tie-ins.
• Separate Ownership from Installation: Storefront rules must keep these concepts distinct and require explicit consent before large downloads begin.
• Improve Messaging: If a purchase affects another title (through cosmetics or add-ons), players should see clear, upfront messaging about what will happen.
• Monitor Community Channels: Swift detection often comes from social media and community forums, making monitoring and rapid response critical.

For players, the situation serves as a reminder that modern game ecosystems are heavily interconnected, and even simple actions like a pre-order can have unexpected knock-on effects when store logic, bundles, and live-service content converge.

Frequently Asked Questions

Did Bungie give away a free copy of Destiny 2 with Marathon pre-orders?

No. The installation of Destiny 2 was the result of a configuration bug tied to the Destiny 2: Marathon Pack cosmetic bundle. Players did not receive a separate, intentional full-game giveaway; they simply had the base application trigger an unwanted install.

Is the bug still happening for new Marathon pre-orders?

Bungie has publicly stated that the issue causing Destiny 2 to install after Marathon pre-orders on Steam has been resolved. New pre-orders should no longer trigger Destiny 2 downloads automatically, though players can always verify their download queue in the Steam client.

Will my Marathon pre-order still include Destiny 2 cosmetics?

Yes. The fix targeted the improper auto-install behavior, not the entitlement to cosmetic items. The Destiny 2: Marathon Pack remains part of eligible pre-orders, granting in-game items for Destiny 2 without forcing the game to install itself.

Could similar bugs happen with other cross-game bundles?

In theory, yes. Any time multiple games and DLC are bundled together, especially across live-service titles, there is potential for misconfiguration. However, incidents that reach this level of visibility tend to prompt both developers and storefront operators to tighten testing for future bundles.

Do I need to own Destiny 2 to benefit from the Marathon Pack?

You need access to Destiny 2 to actually use the Marathon-themed cosmetics, but not necessarily at the time of purchase. The entitlement is attached to your account, and you can install Destiny 2 later if you choose. The bug incorrectly assumed installation should happen right away, which is what Bungie and Steam have since corrected.