The Finish Line Leak: Revisiting Forza Horizon 6's Pre-Launch Breach

Forza Horizon 6 crossed its own finish line on May 19, 2026, and it crossed it fast — nearly five million copies in the first week and one of the best-reviewed games of the year. But for roughly ten days before that, the entire game was already sitting on the open internet. This is the story of the leak, not the launch: how a 155GB build escaped ahead of release, why Playground Games reached for the biggest ban hammer in its arsenal, and what the whole episode actually amounted to now that the dust has settled.

What Actually Leaked

Roughly ten days before launch, the complete PC version of Forza Horizon 6 surfaced online. According to TweakTown, a full 155GB repository appeared through Steam's backend, listed openly on SteamDB with close to 5,000 files, including the DLC packages, the media folder, and forzahorizon6.exe itself. GameSpot called it a "massive leak," and it was: because the build reportedly shipped without Denuvo or comparable DRM, it did not need cracking. Players had it running offline within hours.

Datamining did the rest. The files reportedly exposed the full map, a near-complete car list, and late-game content Playground Games had not shown. Treat those specifics as speculative — the studio's own line was that anything pulled from an unfinished, unauthorized build could be wrong — but the exposure itself was real.

A Self-Inflicted Wound

This was not a heist. Nobody breached a server. The files went out through Steam's own preload pipeline — the system that pushes a game to your drive early so it unlocks at midnight — and they went out, reportedly, unencrypted. Normally preloaded files stay locked and a decryption key flips at release. Here that protection was simply absent, which is why multiple outlets traced the leak to the publisher's side rather than to pirates.

It was also not unique. This was reportedly the third pre-load leak of 2026 alone, after Death Stranding 2 and Pragmata met the same fate. Steam's preload window has become a recurring soft spot; Forza just happened to be the highest-profile game to fall through it.

"Not a Preload Issue"

Here the official story and the evidence diverge. When Microsoft responded, it pushed back on the preload framing directly — Windows Central reported Xbox's position as flatly "not a preload issue." Yet the SteamDB depot, the unencrypted files, and the timing all pointed the other way. Months on, that gap has never been fully reconciled. Whatever the internal cause, the practical result was identical: the finished game was public, and it was playable.

The 8,000-Year Ban Hammer

Playground Games acknowledged the leaked build and promised strict enforcement. The threats escalated fast. The studio warned that accounts touching the unauthorized build could face franchise-wide bans across the entire Forza series, with hardware-ID (HWID) bans held in reserve for the people spreading it. Wccftech reported ban screenshots dated to December 31, 9999 — the "nearly 8,000 years" figure that made headlines, reportedly landing on a YouTuber who posted leaked footage.

Worth a grain of salt. As Game Rant flagged, the legitimacy of specific ban screenshots was never confirmed, and that 9999 date is just Forza's standard sentinel for a permanent ban — the same "8,000-year" number a Horizon 5 player once caught for a cosmetic violation. In other words, it was a permaban dressed up for maximum deterrent effect. And pirated copies were locked out of online play, DLC, and updates regardless.

The messaging was the point. A number that reads like science fiction travels further than "permanent ban" ever could.

What HWID and Account Bans Actually Do

An account ban costs you an account. An HWID ban goes after the machine: anti-cheat fingerprints your hardware, blacklists that fingerprint, and flags any new account created on the same PC. Swap one component and the fingerprint often still matches.

That bluntness is the controversy. Hardware bans are notorious for false positives — players have been flagged over RGB lighting drivers, Cheat Engine installed for single-player games, a swapped motherboard read as ban evasion, or second-hand hardware carrying someone else's history. Appeals rarely succeed, because studios treat hardware bans as final. Hardware-level enforcement is now routine across competitive games — and it lands on the wrong people often enough that reaching for it over a leak, rather than active cheating, drew fair criticism.

Why Pre-Launch Builds Keep Escaping

The uncomfortable truth is that preloads are a business decision with a built-in risk. Publishers want millions installed and ready at launch minute, so they ship the files days early and trust encryption to hold the line. The window between "the game is on your disk" and "the key unlocks" is the vulnerability, and every mishandled key or missing layer blows it open.

DRM decides what happens next. A protected build that leaks is inert; a DRM-free one, like Forza's reportedly was, is instantly playable. That is why the standard playbook — acknowledge, fire off DMCA takedowns, gate the online features that actually matter, and wait it out — is damage control, not prevention. Forza Horizon 6 was close to a worst case: self-inflicted, unencrypted, and unprotected all at once.

The Verdict: A Leak That Barely Registered

And then it didn't matter. Forza Horizon 6 sold roughly 4.9 million copies in its first week, drew more than six million players once Game Pass was counted, peaked above 273,000 concurrent on Steam, and holds a 91 on Metacritic — by July the top new Steam release of 2026 by revenue.

That is the real retrospective lesson. The breach was genuinely embarrassing and the enforcement genuinely aggressive, but neither the leak nor the pirates left a mark on the numbers. For a Game Pass flagship, a pre-launch leak is a PR fire, not a financial one — which reframes the 8,000-year theatrics as exactly that: a signal to the next leaker as much as a punishment for this one. Forza crossed the finish line comfortably. The only lasting casualty was the myth that a preload is a safe place to keep a finished game.