Install T2 on your computer, step by step
No Linux experience assumed. If you're coming from Windows — or a distro that broke on you — this is the whole path, in plain English.
You don't need to be a wizard to run T2. The desktop edition comes as a ready-to-use image you write to a USB stick and boot — the same way you'd install any Linux. Below we walk the whole thing: which file to download, what its intimidating name actually means, how to put it on a USB stick safely, how to boot it, and where to get help when you're stuck. Total hands-on time is usually well under an hour.
1.Download the right ISO
Head to the download page and, for a normal 64-bit Intel/AMD laptop or desktop, grab the file that looks like this:
t2-26.6-x86-64-desktop-glibc-gcc-nocona.isoExample current file: t2-26.6-x86-64-desktop-glibc-gcc-nocona.iso — this exact one is what René ships as the standard PC desktop.
What each part of the name means:
- t2The project
Just says it's a T2 image. Every T2 download starts with this.
- 26.6Version
The version, which is simply year.month — 26.6 means the 2026.6 (June 2026) build. Bigger number = fresher. Grab whatever's newest.
- x86-64Which chip it's for
Your CPU type. x86-64 is the normal 64-bit Intel/AMD PC — the right pick for almost any laptop or desktop from the last ~15 years.
Other values you might see: i686 = 32-bit (very old PCs) · arm64 = ARM (Raspberry Pi 4/5, newer ARM laptops) · ppc64le = PowerPC · riscv64 = RISC-V boards.
- desktopThe edition
What's inside. desktop = a complete, ready-to-use KDE Plasma desktop — the one you want if you just want a working computer.
Other values you might see: base-wayland / minimal = leaner, fewer apps · bootstrap = bare essentials · container = for WSL/containers, not a PC install.
- glibc-gccThe toolchain
The under-the-hood C library + compiler it was built with. glibc + GCC is the standard, most-compatible combo. This is the safe default.
Other values you might see: musl-clang = a leaner, more modern build. Interesting, but more adventurous — some machines that boot the glibc image won't boot the musl one. Beginners: stick with glibc-gcc.
- noconaCompatibility tuning
The oldest CPU it's optimized for. "nocona" is an early 64-bit Intel core, so this image is built to run on basically any 64-bit PC — maximum compatibility. Good thing, not a warning.
- .isoThe file type
A disk image. You don't open it — you write it onto a USB stick, then boot your computer from that stick.
The short version
Normal 64-bit PC and you just want it to work? Take the x86-64 + desktop + glibc-gccfile. That's the recommended default. Reach for a 32-bit (i686) image only if the machine is genuinely ancient.
2.Write it to a USB stick
An .isoisn't something you double-click — you "flash" it onto a spare USB stick (8 GB is plenty), which turns the stick into a bootable installer. Two trusted, free tools:
balenaEtcher
Windows, macOS, Linux
The friendliest option: pick the .iso, pick your USB stick, click Flash. Hard to get wrong.
etcher.balena.ioRufus
Windows
Tiny, fast, Windows-only. If it asks about a partition scheme, leave it on the default (GPT / UEFI) for any modern PC.
rufus.ieFlashing erases the USB stick — move anything you care about off it first. The rest of your computer is untouched at this stage.
"Is this safe? Can I trust Rufus / balenaEtcher?"
Yes — both are well-known, open-source tools used by millions, and both are the community's go-to for T2. Two honest caveats worth knowing:
- Download only from the official sites linked above (rufus.ie, etcher.balena.io) — never a random "download" ad or mirror.
- Your antivirus may briefly flag Rufus or the write operation. That's a false positive: tools that write directly to a whole disk look "suspicious" to AV heuristics — it isn't a virus.
- Want proof the download itself is genuine? The T2 download page publishes a SHA-256 checksumnext to each ISO. If the checksum of your file matches, it wasn't tampered with in transit. (Optional, but it's the real answer to "how do I know it's clean.")
3.Boot your computer from the stick
Leave the stick plugged in and restart. As the machine powers on, tap the one-time boot menukey and pick the USB stick. If it just boots back into Windows, or the stick isn't listed, work through these — they cover almost every case:
The USB stick doesn't show up in the boot menu
Open your firmware setup (tap Del, F2, or F10 at power-on) and turn off Secure Boot. That's the single most common thing blocking a Linux USB from booting.
It still won't boot, or boots to a blank screen
In firmware setup, look for CSM / Legacy boot and try toggling it. When you pick the stick from the one-time boot menu, prefer the entry labelled "UEFI: <your USB name>".
You can't find the boot menu at all
The one-time boot menu key is usually F12, F11, F9, or Esc — it varies by brand (the screen flashes it for a second at startup). Alternatively set the USB first in the boot order.
"It doesn't enter the installer"
Almost always the USB wasn't written as bootable, or Secure Boot is on. Re-write the stick with balenaEtcher and disable Secure Boot, then try again.
4.Try it live, then install
The current desktop ISO boots straight into a live KDE Plasma desktop — a full T2 running from the USB stick. Nothing is written to your computer yet, so you can click around, open the browser, and check your Wi-Fi and trackpad work before committing.
When you're ready, launch the installer (T2's installer is called stone). It's a guided, menu-driven flow: it can partition the disk automatically, sets up a swap area for you, and prompts you to create your username and password. Follow the prompts and reboot when it's done.
Two honest heads-ups
- • It's a straightforward guided installer, not (yet) a glossy one-click wizard like Ubuntu's — a friendlier one-click flow is actively being built. It's clear and it works; just read each screen.
- • Installing to a disk erases what's on it. Back up your files first. Keeping Windows alongside (dual-boot) is possible but is the fiddly path — if it's your only machine and your data matters, practice on a spare drive or ask in the community first.
5.Installing software afterwards
T2 has its own package manager, driven by the t2 command. To add an app you name it and T2 fetches and builds it for you, dependencies and all:
$ t2 install firefox # and to update everything later: $t2 up && t2 upgrade
Wondering whether the software you need is available? T2 ships 6,000+ packages— browse the full list on the official package index. If something's missing you can package it yourself (René and Claude can both help), or ask the community to.
One honest note: T2 builds from source, so a big install or update can use real CPU time. Fast pre-built binary updates are on the project's roadmap.
6.Getting help fast when you're stuck
T2 is a smaller project than Ubuntu or Fedora — which actually means real humans (often René himself) answer questions. Where to ask, fastest first:
René's Discord — the quickest personal help
Access comes with supporting René on Patreon (his low-cost ~$2 tier is the usual ticket in). It's where install and "why won't this boot" questions get answered by people who actually run T2.
Support & join on PatreonThe live streams — ask in chat, free
René live-codes T2 for hours on YouTube and Twitch, and answers chat as he goes. "How do I install T2?" is a welcome question there.
Code Therapy on YouTubeGitHub issues & the handbook — free, for the record
Reproducible bugs belong on GitHub; the handbook is the authoritative reference for architectures and the build system.
Reviving something unusual instead?
Old 32-bit laptop, a Raspberry Pi, a retro game box, or exotic vintage hardware? The build finder points you at the right image.