First run

Playable client first

Splash is not ready. Then Xeno, then attach once. Not a 200-script hub on minute one.

Prompts

First run is extract, then a supported client already in a playable state, then Xeno, then attach once. Skipping “playable state” is the splash-screen failure mode. Tutorial.

Mark-of-the-web and SmartScreen often appear together on a first internet extract. SmartScreen.

If the window opens and closes, you are in runtime or policy land, not first-run magic. .NET desktop pack, then retry. Requirements.

Do not pair first run with a 200-script hub. Prove attach with a tiny print you wrote. Then load files from Script Hub.

First run is not a license to disable AV “just this once”. Antivirus.

If first run is a 402-byte ZIP, you extracted a docs stub. Replace the archive, keep the name, try again. Download.

Playable client, extract, attach once, tiny print

First run is a sequence, not a vibe. Extract Xeno_1.3.6.0.zip to a writable folder. Start a supported desktop Roblox client and wait until it is playable — not splash, not a crash dialog. Start Xeno from the folder. Attach once. Paste a tiny print you wrote, not a 200-script hub.

SmartScreen may interrupt between extract and attach. That is reputation. Filename match, then continue. Do not disable protection to “make first run smoother”. SmartScreen, extract.

If the ZIP is 400 bytes, first run will be a README. You do not have the executor yet. Download.

Store channel first-run is a trap. Confirm desktop. Microsoft Store. Missing .NET is a trap. Requirements.

After a successful tiny print, you can load files you already trust. Tutorial is the longer version of this page. Troubleshooting is the failure tree. Tutorial, troubleshooting, attach.

Skip the YouTube “full setup 2026” that inserts a key and a Discord. Those videos are optimizing for ads, not for this hostname. The four steps on Home are the first run. Everything else is a branch on troubleshooting.

If first run is a crash before the window paints, check 64-bit Windows, .NET desktop runtime, and that you are not on ARM emulation experiments this page does not document. Requirements chapter owns the matrix. Then come back to attach.

Success is ready plus a tiny print, not a crowded hub. Save the hub for after the print. That single habit removes half the false bug reports.