Epic Games Launcher Preview First Indie Lab Worksheet 2026

This epic games launcher lab is one sitting on a spare computer. You download the October 14, 2026 preview, sign in, and write down what you actually see. The computer that already opens Unreal or Unreal Editor for Fortnite does not run the installer.

Epic’s preview site says trying the new launcher automatically uninstalls the legacy version. That sentence is why the lab has two hostnames before it has a download. The store post still says your account, purchases, installed games, cloud saves, and progress carry over, and that once you are inside a game or a developer tool, nothing there would prevent development or casual and competitive play. You check those claims on the spare box. You do not check them by deleting the launcher you ship with.

Read what the preview changed if you need the feature list, the Linux distro line, or the Fortnite anti-cheat plan. Read why the only PC stays on the legacy app if you are still arguing about the disk. This page is the sheet you fill in after that argument is over.

Why this lab exists now

Epic’s how-to is three steps. Download, install and sign in, explore, then Send Feedback. A three-step how-to does not name which computer is allowed to lose its launcher. Teams lose an evening when the excited person and the build PC are the same machine.

The lab takes about 45 minutes if the spare computer is already on and you already know its hostname. It takes longer if you have to find a second machine. Finding the second machine is part of the lab. Skipping it is a failed sheet, not a faster one.

Direct answer: Write two hostnames. Install the preview only on the spare. Confirm the shipping PC’s legacy shortcut still exists when you are done. Sign in on the spare and record purchases, one game row, one screen you expected and did not find, and whether you filed feedback. Latch the sheet LAB_SPARE only when those lines are filled. Otherwise latch ONLY_PC or HOLD.

Who fills this in

Prerequisites: an Epic account you can sign in with, and a second computer or a second OS install you can wipe. One laptop is not enough. The stuck-percent help page is for the legacy app you are leaving in place. The UEFN setup lesson still assumes that legacy app on the machine where you learn the editor.

Blank sheet

Copy this block into a note before you open the preview site. Empty fields are the point. A sheet with blank hostnames and a finished install is a failed lab.

epic_games_launcher_lab_receipt_v1
date:
operator:
shipping_hostname:
spare_hostname:
shipping_role: cook | editor | uefn | store-build
spare_can_be_wiped: yes | no
spare_os:
os_on_epic_list: yes | no | intel_mac | untested_distro
installer_host:
shipping_legacy_shortcut_after: present | missing | not_checked
signed_in: yes | no
purchases_visible: yes | no
game_row: title and state, or none
opened_game_or_tool: yes | no | not_attempted
missing_screen:
feedback_filed: yes | no
latch: LAB_SPARE | ONLY_PC | HOLD

LAB_SPARE means the preview ran on the spare and the shipping hostname still has its legacy shortcut. ONLY_PC means you discovered you do not have a spare, so you did not install. HOLD means a hostname collided, the OS is off Epic’s list, or someone already started an installer on a machine you have not finished naming.

Section A — Name the shipping machine

The shipping machine is the one that would block tomorrow if its launcher disappeared. Use a hostname people can find in a chat log. “My PC” fails the section.

Write shipping_hostname and shipping_role. The role is whichever of these is true:

• cook — last package or cook you would trust ran here
• editor — the only Unreal install for the current project
• uefn — the only UEFN install
• store-build — the only machine that uploads or smoke-tests the store binary

If two computers share the work, the shipping hostname is the one you cannot wipe tonight. The other one might be the spare. If you cannot name either, latch HOLD and stop. Do not download yet.

Walk to that computer, or remote in, and look at the taskbar or the applications list. You want to see the legacy Epic Games Launcher before the lab, so you will recognize it after. Note the shortcut in your head. You will check it again in Section E. Do not update it. Do not click a “new launcher” banner if one is sitting on that desktop.

Sample line, not a studio:

shipping_hostname: cook-pc
shipping_role: cook

Section B — Prove the spare is spare

A spare qualifies only when wiping it tonight would not block the next cook, editor session, or UEFN upload. Answer spare_can_be_wiped.

Reject these as spares:

Accept these:

• An old tower that does not have the project’s only editor
• A personal laptop that plays store games and does not cook
• A Linux install on its own disk, when the Windows cook disk is a different install the preview installer will not touch
• A cloud VM you can delete

Write spare_hostname. If it equals shipping_hostname, latch ONLY_PC and stop. The correct outcome of a one-laptop studio is a sheet that says you did not install. That sheet is finished. Borrow a machine on another day if you still want the preview.

The preview site can send the download link to another computer. Use that control in Section D. It exists so the excited person and the installer are not stuck on the cook PC.

Section C — Check the OS before the installer

Epic publishes the preview’s requirements on the preview site. The launcher is a small install compared with a game. The lab still records the OS, because an unsupported box teaches you nothing about the preview and can waste the only spare you have.

Also glance at RAM and free space. Epic’s floor is 4 GB of RAM, 700 MB free on Windows, 200 MB on macOS, and 2 GB on Linux. That floor is the launcher, not Unreal. If the spare cannot meet it, pick another spare. Do not “make room” by deleting the shipping project if the spare and the shipping disk are the same physical drive. That is the collision Section B already forbids.

Write spare_os the way the computer reports it, plus the yes/no field. Example:

spare_os: Windows 11 24H2
os_on_epic_list: yes

Linux note, one paragraph. A native launcher does not mean the game you click is a native Linux build. Epic says many games are Windows-only and may need a compatibility layer, and that you should check each game before installing. For this lab, prefer a game you already know, or skip launching a huge title. Do not turn the sitting into a Fortnite-on-Linux test. Fortnite on Linux is a later anti-cheat pilot. The what-changed article has that plan. Your sheet has one game row.

Section D — Install on the spare only

You are allowed to download now if A, B, and C passed and the latch is still empty.

1. On the shipping PC, do nothing. Leave the legacy launcher closed or open. Do not run an installer there.
2. On a phone or on the shipping PC’s browser, open launcher.epicgames.com only to send the download link, if you need to. Do not run the Windows installer on the shipping PC because the browser happened to be open there.
3. On the spare, run the installer for that OS.
4. Write installer_host as the spare hostname. If you cannot honestly write the spare hostname, you installed in the wrong place. Latch HOLD and follow the recovery list in the refusal article before anyone else clicks.

Sign in with the account that owns the games you expect to see. Epic says purchases, installed games, cloud saves, and progress carry over because they are tied to the account, and that switching between the legacy launcher and the preview should not affect that data. “Installed” on a spare that never had the game means Epic may still know the license while the spare still needs a download. Record that difference in Section E. Do not describe a download prompt as missing purchases.

The store post’s updated note comes next, after you are in. It does not apply to the installer window. If the spare never finishes installing, you have a spare-machine failure. The shipping PC should still be on the legacy app. Keep it that way while you retry or stop.

Section E — Four observations and the shipping shortcut

This section is the lab. The install was only the setup.

E1. Purchases

Open the library on the spare. Do you see games the account owns?

• purchases_visible: yes when at least one title you know you own is listed
• purchases_visible: no when the library looks empty after a completed sign-in

An empty library is a feedback case, not a reason to install the preview on the shipping PC “to compare.” Compare later, from memory or from a screenshot you take on the shipping PC without updating it. If you are unwilling to look at the shipping library without touching the update banner, skip the comparison. The sheet does not require it.

E2. One game row

Pick one title. Write the name and the state you see: installed, needs download, update, or failed. If you launch it, write opened_game_or_tool: yes only if you reached the game or the tool, not if you reached a download bar.

Epic’s store note says that once you are in a game or developer tool, nothing there would prevent development or casual and competitive play. The FAQ answers competitive Fortnite the same way: once you are in, you are good to go. If you do not launch anything, write not_attempted. That is a valid lab. Launching is how you test the note. It is not a requirement to call the sheet done, as long as the field is explicit.

Do not install Unreal or UEFN on the spare just to make this line say yes, unless the spare already had the editor and wiping it is still acceptable. The Unreal guide is for learning the engine on a machine you intend to keep. This lab is for the launcher.

E3. One missing screen

Epic’s FAQ says some legacy features are not in the preview yet, including certain social features and account-management options. Find one thing you expected.

Examples that count:

• The account or organization screen you use for seats or payment is absent or different
• A social or party control you use is absent
• A legacy settings page you use by habit is not where you looked

Write missing_screen as a short clause. “Could not find payment method” is enough. “Social is broken” is not, unless you name the control. If everything you tried was present, write missing_screen: none found in this pass and list the two screens you opened. A blank field fails the gate.

E4. Feedback

If E1 was no, or E3 was a real block, use Send Feedback in the launcher. Epic repeats that button, and also points at Discord, the Epic Developer Community forums, and Player Support. Write feedback_filed: yes when you sent something, no when the pass was clean enough that you chose not to. no is allowed. A missing field is not.

E5. The shipping shortcut, again

Go back to the shipping hostname. Look for the same legacy shortcut you saw in Section A.

• present — the lab may continue toward LAB_SPARE
• missing — the installer ran on the wrong computer, or something else removed it. Latch HOLD. Stop other installs. Use the recovery steps in the refusal article
• not_checked — the lab is not done. Check before you latch

This is the gate that keeps the sheet honest. A beautiful spare install with an unchecked cook PC is not LAB_SPARE.

Section F — Latch

Set one latch.

Do not invent a fourth latch for “we installed on the cook PC and it seems fine.” That situation is HOLD plus recovery. Fine on a preview, after an uninstall, is not the lab’s success condition. The success condition is a spare machine and an untouched shipping shortcut.

Paste the finished block under the day’s build note or in the team channel. One sheet per spare. A second spare on the same day is a second sheet, not a studio rollout.

Gates

Check these in order. The first failure sets the latch. Later gates stay unchecked rather than half-passed.

Sample sheet

This sample is a blank filled with hostnames you can read. It is not a report from a shipped game.

epic_games_launcher_lab_receipt_v1
date: 2026-10-17
operator: lab
shipping_hostname: cook-pc
spare_hostname: old-laptop
shipping_role: cook
spare_can_be_wiped: yes
spare_os: Windows 11 24H2
os_on_epic_list: yes
installer_host: old-laptop
shipping_legacy_shortcut_after: present
signed_in: yes
purchases_visible: yes
game_row: a store title you own, state needs download
opened_game_or_tool: not_attempted
missing_screen: payment method screen not where the legacy app had it
feedback_filed: yes
latch: LAB_SPARE

A one-laptop sample looks like this, and it is also a finished lab:

epic_games_launcher_lab_receipt_v1
date: 2026-10-17
operator: lab
shipping_hostname: only-laptop
spare_hostname:
shipping_role: editor
spare_can_be_wiped: no
spare_os:
os_on_epic_list:
installer_host:
shipping_legacy_shortcut_after: present
signed_in: no
purchases_visible:
game_row:
opened_game_or_tool:
missing_screen:
feedback_filed: no
latch: ONLY_PC

The second sheet is the one a solo developer should be proud of. Nothing was uninstalled. The preview is still available tomorrow if a spare appears. The Verge quotes Martin Keely saying the old launcher remains available and that Epic has no specific date when everyone must move. Waiting matches that calendar.

What you are not proving

A passed LAB_SPARE sheet proves four things. The spare could be wiped. The OS was on the list Epic published. You signed in and wrote what you saw. The shipping shortcut was still there afterward.

It does not prove the preview is faster than Steam on your hardware. Epic’s clocks live on the preview site and are explained in the what-changed article, including the Keywords Studios footnote. Your sheet does not add a stopwatch unless you choose to, and a stopwatch on one spare is your note, not a replacement for that footnote.

It does not prove Fortnite is on Linux. It does not prove your Easy Anti-Cheat game is supported on Linux. It does not prove account billing screens have parity. G7 asked you to name one missing screen because Epic already said some are missing.

It does not authorize a studio image. One spare is this worksheet. An image is a decision the refusal article tells you to delay until Epic calls the build stable.

Common ways to fail

Installing because the browser was already open on the cook PC. Section D says the browser may send a link. The installer runs on the spare. If those are the same computer, you are in Section B again.

Calling a second user account a spare. The uninstall line is about the computer. Until you have evidence the other account keeps its launcher, do not use that trick on the cook PC.

Testing an Intel Mac and writing os_on_epic_list: yes. Epic’s FAQ says Intel Macs are not supported. The field is intel_mac, and the latch is HOLD.

Launching a 100 GB game so the sheet looks serious. not_attempted is a legal value. A download you did not need is how a 45-minute lab becomes a weekend.

Leaving shipping_legacy_shortcut_after as not_checked and latching LAB_SPARE anyway. G5 and G8 both fail. Check the cook PC.

Filing the sheet as a player announcement. Players do not need your hostnames. If you talk about the preview in public, say you tried it on a spare machine and the daily launcher stayed. That sentence is the devlog. The receipt stays internal.

Monday, after the sheet

If the latch is LAB_SPARE, pin the note next to the build log and do not install on a second important PC the same day. If the latch is ONLY_PC, the work is finding a spare or waiting. If the latch is HOLD because the shipping shortcut is missing, stop and recover that one computer before any other launcher experiment.

Bring the missing_screen line to anyone who wanted to standardize the office. That line is the argument against an image, written from your spare rather than from a headline.

Key takeaways

• The lab installs the October 14, 2026 Epic Games Launcher preview on a spare computer only.
• The preview site says trying it uninstalls the legacy launcher on that computer.
• shipping_hostname and spare_hostname are written before any download, and they must differ.
• A second user account on the cook PC is not a spare for this sheet.
• Intel Macs are unsupported. Other Linux distros outside Ubuntu 22.04 LTS, Fedora 43, and Debian 12 are not this lab’s supported list.
• Sign-in should show purchases. A game row may still need a download on a computer that never had the files.
• Record one missing screen. Epic already says some social and account-management options are absent.
• Send Feedback is optional when the pass was clean, and the field still has to say yes or no.
• LAB_SPARE requires the shipping PC’s legacy shortcut to be present afterward.
• ONLY_PC with no install is a finished sheet when you have one computer.
• The sheet does not ship Fortnite on Linux, adopt a studio image, or replace Epic’s published speed footnote.

FAQ

What is the Epic Games Launcher lab?

A 45-minute spare-computer pass for the October 14, 2026 preview. You name the shipping PC, install only on a machine you can wipe, sign in, write four observations, and confirm the shipping shortcut is still there.

Can I run the lab on my only PC if I promise to reinstall?

No. That promise is a recovery project. The lab’s pass condition is an installer that never ran on the shipping hostname. One computer latches ONLY_PC and stops.

Do cloud saves need a special step?

Epic says cloud saves and progress carry over with the account. This sheet does not add a save-migration procedure. If a title you care about is local-only, do not treat the spare install as a backup of that folder.

What if purchases do not show up?

Set purchases_visible: no, file Send Feedback from the spare, leave the shipping PC alone, and latch HOLD if you cannot finish the other fields. Do not install the preview on the cook PC to see if the library looks different there.

What if I already installed the preview on the cook PC?

Do not start this sheet as if the lab succeeded. Latch HOLD, stop anyone else from installing, and use the recovery order in the refusal article. You can fill a lab sheet later on a real spare.

Does the lab include Unreal or UEFN install?

Only if that editor was already on the spare and you still accept wiping the spare. Do not install the engine on the spare just to tick a box. Learn the engine on the machine you mean to keep, with the legacy launcher this lab refused to remove.

Which Linux PCs are in bounds?

Ubuntu 22.04 LTS or newer, Fedora 43 or newer, and Debian 12 or newer, matching Epic’s launcher list. The lab does not ask you to enable the EAC Linux v2 boot requirements. Those belong to a different announcement.

Can the whole studio share one sheet?

No. One receipt is one spare hostname plus one shipping hostname. A second spare gets a second copy of the block. None of those copies authorize replacing the cook PC.

Where the sheet ends

You are done when the block has one latch and the cook PC’s shortcut matches what you wrote. Leave the preview on the spare if you want to look again tomorrow. Leave the daily launcher where the project already opens. That split is the whole lab.