Stop Replacing Your Only Epic Games Launcher with the Preview - 2026
Stop replacing your only Epic Games Launcher with the preview that opened on October 14, 2026. The preview site puts the hazard in the install step. Trying the new Epic Games Launcher automatically uninstalls the legacy version. If that computer is the one that opens Unreal, Unreal Editor for Fortnite, or the store build you patch tonight, the click is the outage.
The speed, the Linux client, and the Fortnite plan are real, and they belong in what the preview changed. This page is the refusal. One machine that must keep working stays on the launcher already installed. Curiosity gets a second machine, a second OS install, or a hard stop.
Why this matters now
Epic’s store post tells you to download, install, sign in, and explore. The updated note says that once you are inside a game or a developer tool, nothing there would prevent development or casual and competitive play. The Verge quotes Martin Keely, VP and GM of the Epic Games Store and Epic Online Services, saying the old launcher remains available and that Epic has no date when everyone must move.
Those sentences are easy to hear as permission. They are not permission to retire the only install. “Play is fine once you are in the tool” starts after the tool has launched. “The old version remains available” means Epic still offers the legacy product. “Switching should not affect your data,” which is the preview FAQ, is an account claim about purchases, installed games, cloud saves, and progress. None of those lines say the legacy shortcut survives the installer.
A studio of three people often has one PC with the engine cache, the antivirus exceptions, and the project on a local disk. Replacing that launcher on a Tuesday afternoon is how Wednesday’s build becomes a scavenger hunt. The stuck-percent install guide already exists because the legacy app can freeze on its own. Adding an uninstall on top of that, on the same disk, is an unforced error.
Direct answer: If this PC is the only place the Epic Games Launcher is installed for your team’s shipping work, do not install the October 14 preview on it. Send the download to a spare computer. If you have no spare, wait.
Who this refusal is for
| Audience | Use it to… |
|---|---|
| Beginners | Decide in ten minutes whether the PC in front of you is allowed to run the preview installer |
| Developers | Keep Unreal and UEFN on a launcher path the runbook already names |
| Creators | Paste one rule into Discord before someone “just tries” the new client on the build PC |
| Companies | Stop a preview image from becoming the studio standard before Epic calls the build stable |
Time: ten minutes to classify the machine. Installing on a spare box is a later sitting, and it is optional.
Prerequisites: you know which computer opens the editor today. You do not need a new engine version, a Linux distro, or an opinion about vibe coding.
The rule, in one table
| Decision | When it is the right call | What you do |
|---|---|---|
| ONLY_PC | This machine is the only installed Epic launcher your game, editor, or UEFN project depends on | Refuse the preview installer. Leave the legacy app where it is |
| SPARE_OK | A second computer, or a second OS you can wipe, can take the preview without touching the shipping install | Send the download link there. Sign in. Write down what is missing |
| HOLD | You cannot tell which machine is the only one, or someone already started the installer | Stop further installs. Inventory every PC before anyone else clicks |
ONLY_PC is the default for a solo developer on a laptop. SPARE_OK is the default for a team that still has an old tower in the corner. HOLD is the default the moment the answer to “where else is the launcher installed?” is a shrug.
The preview can be interesting and still be the wrong binary for the disk you ship from. Those are separate judgments. Epic’s own page puts “Preview” before “Stable release.” Keely told The Verge the full launch waits until the update feels stable and has parity in the places Epic needs. Your shipping PC does not have to volunteer as that test fleet.
How to tell that a machine is the only one
Answer these out loud before the installer runs. A single “yes” on the first three is enough to choose ONLY_PC.
- Is this the only computer where Unreal Engine or UEFN is installed for the current project?
- Is this the only computer that has completed a successful cook, package, or UEFN upload in the last month?
- If this launcher disappeared at 4 p.m., would someone be blocked until a reinstall finished?
- Do your notes, antivirus exclusions, or firewall rules name this machine’s launcher folders?
- Is the project, the Derived Data Cache, or a large Vault cache living on this disk and nowhere else?
- Does a build script, a scheduled task, or a teammate’s muscle memory double-click a shortcut on this desktop?
If you answered yes to 1, 2, or 3, the preview does not belong here this week. Questions 4 through 6 explain why a reinstall is not a five-minute undo. The UEFN setup lesson still starts with “install the Epic Games Launcher, then the editor.” That sentence assumes the launcher you install is the one the lesson can find again tomorrow. A preview uninstall breaks the assumption on that PC even when the lesson text stays correct.
Write the classification in the channel where people will see it.
machine: build-pc
launcher_today: legacy
decision: ONLY_PC
reason: only Unreal install, only successful cook this month
preview_allowed_here: no
spare_target: none yetA laptop that only plays a store game, with the editor living on a desktop across the room, can be SPARE_OK for the laptop and ONLY_PC for the desktop. Classify machines, not people. The person who is excited about Linux is allowed to be excited. The disk that cooks the build is not the experiment.
Three sentences that are not a yes
People quote Epic in the direction of the download button. Put the quotes back in their scope.
| What someone repeats | Where it is from | What it actually covers |
|---|---|---|
| Trying the new launcher uninstalls the legacy version | Preview site, install step | The copy of the legacy app on the computer running that installer |
| Once you are in a game or developer tool, nothing prevents development or competitive play | Store post, updated note, and the FAQ on Fortnite | The session after launch. It assumes you got in |
| The old version remains available, and there is no forced move yet | The Verge, citing Keely | Epic’s product lineup and calendar. It is not a side-by-side install on your PC |
| Switching between the legacy launcher and the preview should not affect your data | Preview FAQ | Account-tied purchases, installs, cloud saves, and progress |
| The first release is light on features | Store post | Known gaps, including some social features and account-management options in the FAQ |
Read the first row as the action. Read the others as limits on how bad the aftermath might be, not as a reason to ignore the first row.
“Data carries over” is the sentence that tricks careful people. Your Epic account still owns the games. Cloud saves that actually synced should still be cloud saves. A local editor install, a custom cache path, a per-machine antivirus exception, and a shortcut on a taskbar are not account fields. The FAQ tells you to use Send Feedback if something looks missing. Send Feedback is a bug report. It is not a same-day restore of the shortcut your build script clicks.
What you lose when the only install goes away
The installer removes an application. The pain is everything that application was the front door for.
The editor path. Unreal and UEFN are launched from the launcher by a lot of small teams because that is how the Unreal setup path and the UEFN course teach it. A Start menu entry you pinned in 2024 may point at a binary the preview uninstalled. Opening the editor from a raw .exe you happen to remember is a workaround you discover under pressure, and it may skip the sign-in state the project expected.
Account screens the FAQ already marks as incomplete. Epic says some legacy account-management options are not in the preview yet. If the only remaining launcher is the preview, the afternoon you needed to fix a seat, a payment method, or an organization setting is the afternoon those options are in the “not yet” bucket. Do that class of work on a legacy install you still have, which means you must still have one.
Caches and exclusions. Teams that already fought a stuck install often have exclusions on launcher folders, downloaded engine zips, and a specific cache directory. Those paths were written for the legacy layout. A new client can use new folders. Your exclusions do not migrate themselves. The help page for a frozen percent bar is still the right repair for the legacy app. It is the wrong document to discover after you have deleted the app it repairs.
Scheduled and shared habits. A producer who remotes into the build PC and clicks Library is using a UI, not an API. The preview’s Library, Details view, and download panel may be better, and they are also different. The first time you need a failed-download row at 11 p.m., you want the panel you have already used, or you want a spare machine’s notes that say where the new panel is. You do not want both to be true on the only PC, discovered live.
Linux curiosity on a Windows build box. The native Linux client is a reason to boot a Linux disk. It is not a reason to replace the Windows launcher that cooks your Windows target. The preview FAQ is clear that the launcher can be native while many games remain Windows builds that may need a compatibility layer. Your editor PC does not need to host that experiment.
A spare machine is the whole workaround
SPARE_OK is specific. It is not “I’ll be careful.” It is a second place the uninstaller can run.
A spare machine qualifies when all of these are true:
- The shipping project does not live only on that disk.
- Unreal or UEFN on the shipping PC will still launch if this spare box is wiped tonight.
- You can sign into the Epic account, or into a separate test account if your studio rules require that, without making the spare box the only signed-in editor.
- You are willing to reinstall the operating system or the user profile if the preview misbehaves.
- Nobody’s muscle memory uses this box for the daily cook.
Epic’s preview site includes a control to send the download link to another computer. That control is the product version of this rule. Use it. Installing “just to look” on the build PC, with a plan to reinstall the legacy app later, is ONLY_PC with extra steps. The Verge reports that the old launcher remains available, so a later reinstall is a plausible recovery, and it is still a reinstall. Plausible is not the same as free.
If the spare box is a Linux machine, keep the scope small. Confirm the distro is one Epic named for the launcher (Ubuntu 22.04 LTS or newer, Fedora 43 or newer, Debian 12 or newer) before you treat a crash as a preview bug. Other distros may run and are not officially tested. Fortnite on Linux is a separate plan, documented on the store post and in Epic’s EAC Linux v2 note. The what-changed article walks through that plan. This refusal does not need you to configure Secure Boot to decide that the build PC stays untouched.
An Intel Mac is simpler. Epic says the macOS preview is Apple silicon only and that Intel Macs are not supported. An Intel Mac that is your only editor machine stays on the legacy launcher because the preview is unsupported there, not because you failed a courage test.
If someone already clicked
HOLD starts the moment the installer has been opened on a machine you have not classified. Do this in order. Do not install the preview on a second important PC “so we have a backup launcher.” That second click can uninstall the legacy app there too.
- Ask which computer ran the installer. One hostname. Write it down.
- On every other computer, leave the legacy launcher installed. Say so in chat, in one line, so a second person does not “help.”
- On the computer that already ran it, see whether the legacy shortcut is gone. If it is gone, believe the preview site. The uninstall happened.
- Sign in if the preview is what remains, and check whether purchases show up. Epic says they carry over. A missing row goes to Send Feedback inside the launcher, which is the path Epic repeats, along with Discord, the Epic Developer Community forums, or Player Support.
- Try to open the editor or the game you needed today. The store note says that once you are in, development and competitive play should not be blocked by the preview itself. If you cannot get in, you are in a reinstall problem, not a “wait for the speedboat to grow a yacht” problem.
- Reinstall the legacy launcher from Epic’s ordinary download if this PC must return to the old UI and Epic still offers that download. The Verge’s report that the old version remains available is the reason this step is legitimate. Do it on the broken machine. Do not “standardize” the preview across the office while you wait.
- After the legacy app is back, confirm the editor opens and a trivial local launch works before anyone queues a full cook. Then write ONLY_PC on that hostname so the same click does not happen on Friday.
What this recovery list refuses to pretend: there is no documented one-click undo in the sources above. Cloud saves are not a snapshot of your engine cache. Send Feedback is not a remote desktop session from Epic that puts Thursday’s shortcut back. If the only copy of an unpushed project lived on that disk and the disk is fine, the project is still on the disk. The launcher is the thing the installer removed. Protect the disk. Do not reformat it because the launcher icon changed.
Who is allowed to click
Write the permission in a place a new teammate will find. A Discord pin is enough for a team of five. A company needs the same sentences in the machine policy.
| Role | May install the preview on | May not |
|---|---|---|
| Whoever owns the build or cook PC | A spare machine they do not cook from | The build PC |
| An artist with a local editor | Their spare, or not at all | The only PC that has their scene |
| A producer without an editor install | A personal laptop that does not remote-desktop into the build PC as the daily path | Any shared workstation |
| Whoever images office PCs | Nothing this week | A studio image, a golden laptop, a new-hire laptop |
| A Linux volunteer | Their own Linux box on a named distro | The Windows cook PC, “while I test Proton” |
The company version of ONLY_PC is an image. If the preview becomes the image, every new laptop uninstalls the legacy path on first setup. Epic has not announced a forced cutover. Adopting the preview as the image is a cutover you would be choosing. Wait until you can point at Epic’s stable release, or until a spare fleet has a written list of missing account screens and a reinstall path you have actually used.
Contractors and playtesters get the same rule in one sentence. “Do not update the launcher on the machine we sent you.” A playtest laptop that can be wiped is SPARE_OK only if losing it does not lose the build. A playtest laptop that is also the only signed build is ONLY_PC.
Ten minutes on Monday
Do this before standup if the preview has been in anyone’s group chat since October 14.
- List every computer that has the Epic Games Launcher. Hostnames, not “my PC.”
- Mark the one that last cooked, packaged, or uploaded. That mark is ONLY_PC even if other laptops also have the store installed for playing.
- Paste the decision table into the channel. Ask anyone who already installed the preview to reply with the hostname and nothing else.
- If a reply names the cook PC, switch to the recovery list above. Cancel other launcher experiments for the day.
- If no reply names the cook PC, send the preview link to one spare machine and stop. One spare is an experiment. Three spares are a rollout.
- On the spare, fill in the Epic Games Launcher preview lab worksheet. Keep the cook PC untouched.
- Leave the cook PC’s legacy launcher pinned. If a shortcut looks unfamiliar, do not “repair” it by downloading the preview.
The shareable version, for a creator who does not want a policy doc, is one sentence. The October 14 preview uninstalls the Epic launcher already on that PC, so it does not go on the only PC that can open the project.
What this refusal will not settle
It will not tell you whether the preview’s cold start is faster than Steam on your laptop. Epic published a Keywords Studios comparison on the preview site, and the what-changed article shows how to read the footnote. A benchmark is not an install decision.
It will not configure EAC Linux v2, Secure Boot, or a Steam Deck. Fortnite on Linux is not a shipped client. Replacing your Windows launcher does not move you closer to that pilot.
It will not review Epic’s AI briefing. The Verge has Keely on the record about agents, supervision, and a launcher team that has not adopted a ban on hand-written code. Interesting for a devlog. Irrelevant to whether your only shortcut should be uninstalled tonight.
It will not fill in a click-by-click lab with gates and a receipt. That sitting wants a spare machine already chosen. This page ends when the shipping machine is marked off limits.
Common mistakes
“I’ll install it and uninstall the preview if I hate it.” The legacy app is what the installer removes. Your exit is a reinstall of the legacy product, if Epic’s download still offers it, plus whatever local state did not travel with the account. That is a rollback project, not a toggle.
“The note says competitive play is fine.” Fine begins once you are in the game. It does not keep the legacy launcher installed, and it does not fill in account-management screens the FAQ still lists as missing.
“The Verge said the old launcher is still available, so my PC will keep both.” Availability is Epic’s catalog. The preview site describes the disk in front of you. Both can be true, and the disk still loses the legacy app.
“Our saves are in the cloud, so the machine does not matter.” Cloud saves cover games that sync them. They do not cover the editor install, the DDC, or the only copy of an unsynced scene on the desktop.
“The Linux build is the point, and this Windows PC is what I have.” Then you do not have a spare. HOLD until you do. Dual boot can be a spare only if the Windows side that cooks the game is a different install the preview installer will not touch. If you are unsure which disk the installer will see, you are unsure. Stop.
“Everyone else in the group chat already updated.” Their group chat is not your cook PC. One spared laptop in a friend group is SPARE_OK for them. Your only editor laptop is still ONLY_PC.
Standardizing the office image because the UI looks cleaner. Cleaner is a preview goal Epic states. Parity is the gate Keely described for the full release. An image is a forced move. Epic has not required one.
What to say when you are the person who wanted to try it
You can try it. The refusal is about the disk, not about your curiosity. Book the old tower, a cloud VM you can delete, or a Linux box that does not cook the shipping target. Sign in. Use Send Feedback for anything that blocks you. Bring three notes back. Leave the build PC’s shortcut alone.
If you are the only person on the team and you have one laptop, the honest schedule is to wait, or to borrow a second machine for an evening. There is no third option in which the preview uninstalls the legacy app and your Tuesday cook is guaranteed. Epic’s carry-over language is the best assurance they published, and it is about account data. Your cook is a local toolchain.
Key takeaways
- The October 14, 2026 preview installer uninstalls the legacy Epic Games Launcher on the PC where you run it.
- ONLY_PC means refuse the preview. SPARE_OK means a second machine you can wipe. HOLD means stop until every hostname is classified.
- “Once you are in the game, play is fine” describes the session after launch, not the installer.
- “The old launcher remains available” is Keely’s product statement to The Verge, not a side-by-side install on your disk.
- Purchases, cloud saves, and progress are supposed to follow the account. Editor caches, shortcuts, and antivirus exclusions do not.
- Some account-management options are still missing in the preview, according to Epic’s FAQ. Keep one legacy install if you still need those screens.
- One spare machine is an experiment. Putting the preview in a studio image is a cutover Epic has not scheduled.
- If someone already installed it on the cook PC, stop every other install, then recover that one hostname.
- Intel Macs are unsupported for the preview. That machine stays on the legacy app when it is your only Mac.
- Linux launcher support and Fortnite-on-Linux are different announcements. Neither one requires replacing the Windows cook PC.
- Send Feedback is the bug path. It is not an undo button.
FAQ
Should I replace the Epic Games Launcher on my only PC with the preview?
No. The preview site says trying the new launcher automatically uninstalls the legacy version. If that PC is the only place you open Unreal, UEFN, or the build you ship, leave the legacy app installed.
Does Epic say the old launcher is going away this week?
The Verge quotes Martin Keely saying the old version remains available and that there is no specific timeline for a forced move. The full launch waits on stability and parity. You do not have to move a shipping PC to stay current with Epic’s calendar.
Will my purchases and cloud saves survive if I ignore this and install anyway?
Epic says purchases, installed games, cloud saves, and progress carry over with the account, and that switching between the legacy launcher and the preview should not affect that data. If a row is missing, use Send Feedback. Local editor installs and unsynced files are a separate problem the FAQ does not restore for you.
What counts as a spare machine?
A computer or OS install you can wipe without blocking the next cook, package, or UEFN upload. A second user account on the build PC is not a spare if the installer uninstalls the launcher the other account also uses. When you are unsure, treat it as the same machine and choose ONLY_PC.
Can I install the preview on a playtest laptop?
Only when that laptop is disposable and is not the only signed build. A shared test laptop that artists also use to open the project is ONLY_PC until you know another machine can do that work.
What if the preview is already the only launcher left on the build PC?
Stop other people from installing it anywhere else. Check whether you can still open the editor. If you cannot, reinstall the legacy launcher from Epic’s download, since The Verge reports that the old version remains available, and confirm a trivial launch before the next cook. Then mark that hostname ONLY_PC.
Does this apply to Intel Macs?
Yes, and the preview is unsupported on them anyway. Epic says the macOS preview is Apple silicon only. An Intel Mac that is your only editor machine should not be the test.
Is a faster startup a reason to switch the build PC?
No. Speed numbers on the preview site are Epic’s commissioned comparison, with a footnote, and they do not reinstall your toolchain. Read them in the what-changed article if you need the clocks. Decide the disk with the uninstall sentence.
Where to leave the build PC
Pin the legacy launcher. Tell the channel the hostname is off limits. Point anyone who wants the new client at a spare machine and at what the October 14 preview actually changed. The download can wait. The cook cannot.