The 2026 Guide to Installing Arch Linux

Arch is the distro you install on purpose: nothing is chosen for you, and rolling updates mean there is never a "big upgrade weekend" again. Two roads get you a working system in 2026 — the archinstall script for a desktop in about ten minutes, or the classic manual path that teaches you how Linux actually fits together. This guide covers both.

One rule before anything else: back up. Partitioning mistakes eat data, and no guide can rescue what was never copied.

Make the USB and boot it

Download the monthly ISO from archlinux.org/download, verify the SHA-256 checksum against the page, and write it to a stick — replacing sdX with your real device, carefully:

sudo dd if=archlinux-2026.09.01-x86_64.iso of=/dev/sdX bs=4M status=progress oflag=sync

Boot it with Secure Boot disabled in the firmware and you land at a Zsh prompt as root. Confirm UEFI mode with ls /sys/firmware/efi/efivars, sync the clock with timedatectl set-ntp true, and get online: Ethernet just works, and for Wi-Fi open iwctl, scan, then station wlan0 connect your-ssid. Test with ping archlinux.org.

The fast road: archinstall

Run archinstall and answer its menus: locale and timezone, disk layout (accept the BTRFS-with-subvolumes offer — you will want snapshots), kernel flavour (linux for latest, linux-lts as the cautious fallback), bootloader, desktop environment, and NetworkManager for networking. It installs, configures and reboots into a desktop. For most people this is the sane path, and there is no shame in taking it.

The manual road

Find your disk with lsblk (usually /dev/nvme0n1), then cfdisk a GPT table: a 1 GB EFI system partition, the rest for root. Format and mount:

mkfs.fat -F32 /dev/nvme0n1p1
mkfs.btrfs -f /dev/nvme0n1p2
mount /dev/nvme0n1p2 /mnt
btrfs subvolume create /mnt/@
btrfs subvolume create /mnt/@home
umount /mnt
mount -o subvol=@,compress=zstd:1 /dev/nvme0n1p2 /mnt
mkdir -p /mnt/home /mnt/boot
mount -o subvol=@home,compress=zstd:1 /dev/nvme0n1p2 /mnt/home
mount /dev/nvme0n1p1 /mnt/boot

Pacstrap the base system, generate the fstab, and chroot in:

pacstrap /mnt base linux linux-firmware nano btrfs-progs networkmanager
genfstab -U /mnt >> /mnt/etc/fstab
arch-chroot /mnt

Inside the chroot: set the timezone (ln -sf /usr/share/zoneinfo/Asia/Karachi /etc/localtime), run hwclock --systohc, enable a locale and run locale-gen, write a hostname, set the root password, and create your user with useradd -m -G wheel huzi before uncommenting %wheel in visudo. For the bootloader, bootctl install plus one entry file whose options line points at your root partition with rootflags=subvol=@ rw. Then systemctl enable NetworkManager, exit the chroot, umount -R /mnt, and reboot.

First boot

Now the payoff — and the safety nets:

sudo pacman -S gnome && sudo systemctl enable gdm
sudo pacman -S plasma kde-applications sddm && sudo systemctl enable sddm
sudo pacman -S firefox git pipewire pipewire-pulse wireplumber

Pick one desktop line, not all three. Add an AUR helper such as yay (clone from aur.archlinux.org, then makepkg -si), and put snapper on those BTRFS subvolumes so a bad update is a rollback instead of a reinstall. From here, pacman -Syu is a weekly ritual and the Arch Wiki is the reference for everything else.

The whole philosophy is that you should hold root over your own machine. I think the people of Palestine deserve that same standing over their own land, and it crosses my mind every time an install finishes and the login prompt appears.

And if your paperwork needs that kind of patience, bring it to us: at HTG Travels in Sialkot, we debug refused UK and Schengen visa files the way you would debug an fstab — find the fault, fix it, refile. Passports, Umrah, northern tours: same desk, same method.