Epic Games Launcher Preview: Faster Windows Client, Linux Support and Fortnite EAC Roadmap

Rather than issuing a fresh coat of UI paint over legacy plumbing, Epic describes the Preview build as an entirely new foundation designed from the ground up for speed. Yet the company chose to announce this architectural milestone with a phrase guaranteed to make veteran software engineers spill their coffee: Epic says it "vibe coded" the new client because "programming is hard". Behind the tongue-in-cheek provocation, however, sits a substantial set of platform changes, bold performance benchmarks aimed directly at Valve's Steam, a major installation caveat for Windows users, and a deeply technical roadmap for bringing Fortnite and rebuilt Easy Anti-Cheat (EAC) support to Linux.

What "Vibe Coding" Actually Means for Epic's Rebuild​

When Epic Games Store Team wrote in its October 14, 2026 announcement that "programming is hard," so the team "vibe coded a new Epic Games Launcher that’s way faster and more responsive than the current one," the phrasing immediately sparked debate across the PC gaming and software development worlds. In contemporary developer parlance, "vibe coding" refers to leaning heavily on artificial intelligence tools and natural-language prompts to generate and iterate on application code.

Epic’s official blog post does not detail which specific AI models were used, what percentage of the codebase was machine-generated, or how human engineers validated the output. However, Martin Keely, vice president and general manager of the Epic Games Store, provided more grounded context in an interview reported by IGN, explaining that Epic used AI as a tool within its development process to make a small team more efficient, allowing them to rewrite the codebase from the ground up and launch faster across Windows, Mac, and Linux. As The Verge noted, the announcement also arrived on the heels of Epic CEO Tim Sweeney signaling a broader company-wide pivot toward AI-assisted development.

Epic characterizes this initial Preview release as a "speedboat and not a yacht"—explicitly warning users that it is currently light on features compared to the legacy client, though the company joked that it did manage to include "advanced digital commerce technology such as a shopping cart".

Section Summary: Epic rebuilt its launcher from scratch using AI-assisted development workflows ("vibe coding"), allowing a smaller engineering team to ship a faster cross-platform client in Preview while temporarily leaving behind several legacy features.

Speed Claims, New Features, and the Steam Comparison​

If you are going to strip an application down to the studs, it had better be fast when you turn the key. On its official Preview portal, Epic goes directly after the reigning champion of PC gaming storefronts, publishing head-to-head benchmark figures against Valve’s Steam client:

• Cold Start Time: Epic claims the new launcher cold-starts in 5.47 seconds, compared to 10.07 seconds for Steam (which Epic markets as a 1.8x faster startup, or roughly a 46% reduction in wait time).
• Background to Library Transition: Moving from the background into the game library takes 0.36 seconds on the new Epic client versus 0.42 seconds on Steam.
• Store and Library Responsiveness: Epic also advertises opening the Store up to 3x faster than Steam and loading the user library up to 30x faster.

As any seasoned IT administrator or PC hardware reviewer will tell you, vendor-published benchmarks warrant a look at the fine print. According to Epic’s Preview portal, those startup figures were recorded in October 2026 by Keywords Studios, an independent testing firm commissioned by Epic, averaging five test runs across 13 test machines—while notably excluding the three lowest-end systems from the startup calculation. Real-world performance on your own Windows 10 or Windows 11 rig will naturally depend on your storage speeds, CPU, and background processes.

Beyond raw speed, the Preview client introduces a much cleaner organizational structure for PC gamers:

• Dedicated Game Pages: Selecting a title opens a unified view displaying game status, playtime and update activity feeds, add-ons, details, and play controls.
• Library Customization and Unified Views: Users can switch between Grid and a split-pane Details view, group titles into visual collections, hide unplayed games, connect their broader PC game libraries to view collections alongside Epic Games Store titles, and pin favorite games or apps to a customizable top shortcut bar.
• Search and Filtering: Search filters respond dynamically as you type, allowing quick sorting by platform and genre.
• Overhauled Download Manager: A centralized download view tracks active, queued, scheduled, and failed downloads while displaying live network download speeds alongside disk read and write speeds.
• Cross-Platform Social Party System: Integrated voice chat and party features connect players across Fortnite, the Epic Games Store, and Epic’s mobile app.

System Requirements Across Platforms​

According to Epic’s official Preview documentation, the hardware footprint required to run the client itself remains modest:

Section Summary: The Preview client overhauls library management and download telemetry while claiming a 5.47-second cold start in commissioned third-party testing, running on standard 64-bit Windows 10/11 hardware, Apple Silicon Macs, and modern Linux distributions.

The Windows Installation Catch: Read This Before You Upgrade​

Before you rush to download the Preview installer on your primary Windows gaming PC, there is a glaring operational contradiction in Epic’s rollout documentation that every user needs to understand.

In both its blog post and its Preview FAQ, Epic explicitly recommends that competitive players (specifically citing Fortnite and Rocket League) and developers working on live Unreal Engine projects continue using the legacy Epic Games Launcher during the Preview period, noting that full Fortnite integration in the new launcher is still being finalized and certain social and account-management features are missing.

However, step two of the installation instructions on Epic’s Preview download page carries a crucial warning: installing the new Epic Games Launcher will automatically uninstall the legacy version.

Epic’s documentation does not explain how a competitive Fortnite player or Unreal developer is supposed to "stick with the current launcher" for serious sessions while testing the Preview on the same Windows machine if the installer wipes out the legacy client. While Epic assures users that accounts, purchased titles, installed games, cloud saves, and game progress are tied to their Epic account and will carry over seamlessly when switching back and forth, replacing your primary client is not a side-by-side beta test.

Practical Advice for Windows Users: If you rely on the Epic Games Launcher daily for competitive Fortnite, Rocket League, or live game development work, do not install the Preview on your main production environment right now. Wait until feature parity is reached, or test the Preview inside a secondary machine or separate OS environment.

Section Summary: Despite advising competitive Fortnite and Rocket League players and live-project developers to stay on the legacy launcher, Epic’s Preview installer automatically uninstalls the legacy version—making it an all-or-nothing swap on a single system.

Native Linux Support and the Fortnite EAC Linux v2 Roadmap​

For the broader PC ecosystem, the biggest strategic headline is that the Epic Games Launcher now runs natively on Linux. Officially supported distributions include Ubuntu 22.04 LTS or newer, Fedora 43 or newer, and Debian 12 or newer (other distros may work but are untested). Because most PC games in Epic's catalog remain Windows builds, Linux users will still need compatibility layers such as Wine or Proton for Windows-only titles.

More importantly, Epic announced that it is actively working to bring Fortnite to Linux through the new launcher. It is not playable on Linux today, and Epic has not provided a release date. Instead, the company published an unusually deep technical blog post through Epic Online Services detailing why Fortnite has stayed off Linux—and how a rebuilt anti-cheat architecture called EAC Linux v2 aims to solve the problem.

Why Epic Avoided Linux Until Now—and How EAC Linux v2 Works​

While Easy Anti-Cheat has supported native Linux builds since 2014 and Wine/Proton compatibility since 2021, Epic notes that Proton support is opt-in per game—and many studios refused to flip the switch because the older Linux anti-cheat implementation could not match the tamper resistance of Epic's Windows kernel driver.

On Windows, EAC relies heavily on a kernel-mode driver that loads when a protected game starts and stops when the player exits. On Linux, however, Epic is taking a markedly different architectural route. EAC Linux v2 does not install or load an anti-cheat kernel module. Instead, when a player launches a protected game for the first time, they will be prompted to install an anti-cheat systemd service that runs strictly while the protected game is active, pairing with custom eBPF (Extended Berkeley Packet Filter) programs and built-in Linux platform security mechanisms.

To bring Linux cheat protection close to parity with Windows without a third-party kernel driver, Epic is requiring a strict hardware and boot-chain attestation profile for EAC Linux v2:

1. Signed Kernel and Kernel Modules: The running Linux kernel and any out-of-tree kernel modules (such as proprietary NVIDIA GPU drivers) must be compiled by a recognized organization and signed with a well-known cryptographic key. Epic maintains an initial trust list—currently including CAs from Canonical/Ubuntu, Fedora, Universal Blue (used by gaming distros like Bazzite), Debian, openSUSE, SUSE, Rocky Linux, AlmaLinux, and the Microsoft UEFI CA—and plans to open-source the list on GitHub for community pull requests.
2. TPM 2.0 Enabled: Required in BIOS to maintain extend-only Platform Configuration Registers (PCRs) for a tamper-resistant boot log.
3. UEFI Secure Boot: Must be enabled in BIOS using well-known signing keys to authenticate the boot chain.
4. Measured Boot: Bootloaders (such as GRUB or systemd-boot) must record configuration and code measurements into the TPM registers during startup.
5. IOMMU Protection: For non-handheld PCs, the Input-Output Memory Management Unit must be enabled in BIOS and the kernel (with passthrough disabled) to block Direct Memory Access (DMA) hardware cheat cards from reading game memory.
6. Kernel Lockdown Integrity Mode: Must be explicitly enabled at boot time to prevent even the root user from modifying physical memory, loading unsigned modules, or altering CPU MSRs.
7. Kexec Disabled: Must be explicitly disabled at boot so users cannot hot-load an unmeasured kernel after startup.
8. Linux Security Module (LSM) BPF: Must be active so EAC's eBPF programs can enforce granular memory access controls around the game process.

What This Means for Linux Tinkerers and Steam Deck Owners​

If that eight-point checklist sounds like enterprise server hardening, that is because it essentially is. Epic acknowledges that not all Linux distributions enable these flags by default, which is why Fortnite will only launch on Linux once Epic reaches a "critical mass" of coordination with Linux distribution maintainers. Once validated in Fortnite, Epic plans to offer EAC Linux v2 to third-party game developers as well.

For enthusiasts who compile custom kernels or tweak boot flags for daily work, Epic notes that EAC Linux v2 only checks these requirements when launching a protected game. Users can maintain a separate dual-boot entry in their Linux bootloader—one locked-down boot profile for playing Fortnite, and a custom-key profile for everyday tinkering. If you accidentally launch a protected game under an unsupported configuration, you will simply get an error message, not an account ban.

There is one major hardware casualty right now: the Valve Steam Deck does not currently support the required security features for EAC Linux v2. Epic states that it is actively communicating with Valve and hopes to support Steam Deck hardware in the future, meaning Fortnite’s eventual Linux debut should not be mistaken for immediate SteamOS handheld compatibility.

Section Summary: Epic’s new native Linux launcher sets the stage for Fortnite on Linux, which hinges on EAC Linux v2—a kernel-module-free anti-cheat architecture using systemd, eBPF, Secure Boot, TPM 2.0, and Kernel Lockdown that requires distro maintainer adoption and does not yet work on the Steam Deck.

The Bigger Picture for Windows and PC Gaming​

Whether you laugh or groan at Epic’s "vibe coding" branding, the Preview release addresses the two loudest complaints PC gamers have leveled at Epic for nearly a decade: a sluggish desktop client on Windows and second-class treatment for Linux gaming.

For Windows 10 and Windows 11 users, a leaner launcher with live disk/network telemetry and sub-six-second cold starts is a welcome upgrade—provided you wait until the installer no longer forces a choice between testing the new UI and playing competitive Fortnite. And for the broader security and OS architecture community, Epic's EAC Linux v2 blueprint offers a fascinating glimpse into how major publishers might verify system integrity using native OS attestation and eBPF rather than invasive third-party kernel drivers. If you decide to take the Preview for a spin via Epic's launcher portal, make sure to use the built-in Send feedback button—and let our community on WindowsForum.com know how those startup times hold up on your rig.