Getting a lightweight boot environment onto an older machine should take about thirty minutes. In practice, it takes most people two to three hours - not because the process is difficult, but because they skip the preparation steps and then spend the extra time diagnosing problems that were entirely avoidable. After more than a decade of walking people through first installs on hardware ranging from 2008 netbooks to 2018 business laptops, the same handful of skipped checks account for nearly every failed attempt I see. This page covers those checks in the order they matter, so you can get through the process in one clean session.
The sections below cover system verification, boot media preparation, BIOS configuration, what to expect during the first boot, and the post-install steps that most guides skip entirely. If your machine has specific hardware quirks - a problematic Wi-Fi chipset, an unusual storage controller, or a BIOS that does not behave as expected - the support section covers those cases individually.
The first thing to establish is whether your hardware can run a lightweight boot environment at all. The bar is low - most machines manufactured after 2008 with at least 1 GB of RAM and a working USB port will manage it. But knowing the specifics of your machine before you start eliminates the most frustrating class of problems: the ones that only surface halfway through an install.
Pre-install system verification
- Processor architecture: Confirm your CPU is x86_64 (64-bit). Nearly all machines from 2008 onward are, but a handful of Atom-based netbooks from that era are 32-bit only. On Windows, check System Information (msinfo32) under System Type. If it says x86-based, you need a 32-bit image.
- RAM: 1 GB is the functional minimum. 2 GB is comfortable for a lightweight desktop environment. 4 GB handles a modern browser with several tabs. Check Task Manager or System Information for the installed amount.
- Storage interface: Know whether your machine uses SATA, mSATA, M.2 SATA, or M.2 NVMe. This matters for driver loading during install and for any drive swap you might be planning alongside the OS change. Most machines from 2008 to 2015 use standard 2.5-inch SATA.
- Storage health: Run CrystalDiskInfo on Windows or smartctl on Linux. A drive with reallocated sectors or pending sectors will cause random failures during and after install. Replace it before starting.
- USB ports: Test the specific port you plan to boot from. Some machines have USB 3.0 ports that the BIOS firmware cannot boot from in legacy mode. If USB boot fails, try a USB 2.0 port before investigating further.
- Network adapter: Identify your Wi-Fi chipset. Intel chipsets are almost universally supported. Broadcom and Realtek often require additional firmware packages. If you are unsure, have an ethernet cable ready for first boot - you can sort out Wi-Fi drivers once you have a working network connection.
For detailed hardware requirements and known compatibility notes, see the system requirements page.
A reliable USB drive and a properly written image are the foundation of every install. The drive itself matters more than most people expect - cheap flash drives with failing cells produce write errors that look exactly like a corrupted download. I keep a set of tested drives on the workbench specifically for installer work, and I recommend anyone doing this regularly does the same.
Step 1 - Choose and verify your USB drive
Use a drive of at least 4 GB. 8 GB is better - it gives headroom for larger images and avoids tight-fit write failures. Before writing anything, do a full format (not quick format) to detect bad cells. On Windows, right-click the drive in File Explorer, select Format, and uncheck Quick Format. On Linux, usebadblocks -wsv /dev/sdX (this destroys existing data).
Step 2 - Write the installer image
Use a dedicated image writing tool - Rufus on Windows, Etcher on any platform, or dd on Linux. Do not simply copy the ISO file onto the drive; it must be written as a raw disk image. In Rufus, select the ISO, confirm the target drive, and use the recommended partition scheme (GPT for UEFI machines, MBR for legacy BIOS). If you are unsure which your machine uses, the support section has a reference for checking.
Step 3 - Verify the write
After writing, safely eject and re-insert the drive. The drive should appear with the installer's boot files visible (on UEFI systems, look for an EFI folder). If the drive appears empty or prompts you to format it, the write failed - reformat and try again, preferably with a different drive.
This is where most first-time installers lose time. The BIOS configuration needs three things to be correct: boot priority must include USB, Secure Boot must be in the right state, and the boot mode (UEFI or Legacy) must match the installer image you wrote. Getting any one of these wrong produces a machine that either ignores the USB drive entirely or shows a cryptic error on boot.
BIOS settings checklist
- Access the BIOS: Restart the machine and press the setup key during POST. Common keys: F2 (Lenovo, Acer, Toshiba), Delete (ASUS, MSI), F10 (HP). If the key does not register, hold Shift while clicking Shut Down in Windows to force a full shutdown, then try again on the next power-on.
- Boot priority: Move USB to the top of the boot order, or use the one-time boot menu (usually F12) to select the USB drive directly.
- Secure Boot: Disable it for unsigned Linux images. Some distributions ship signed bootloaders that work with Secure Boot enabled, but the safest approach for a first install is to disable it and re-enable later if needed.
- CSM/Legacy mode: If your installer was written in MBR format, enable CSM or Legacy mode. If it was written in GPT format for UEFI, make sure CSM is disabled. Mismatching these causes the drive to not appear in the boot menu at all.
- AHCI mode: Ensure your SATA controller is set to AHCI, not IDE or RAID. Some machines default to IDE mode, which causes performance issues and occasional detection failures with Linux kernels.
With the USB drive inserted and the BIOS configured correctly, restart the machine. You should see the installer's boot menu within a few seconds. If you see the normal operating system starting instead, the BIOS is still booting from the internal drive - go back and check the boot priority.
The first boot from a USB drive is always slower than a final installed system. USB 2.0 ports in particular add noticeable delay during file loading. This is normal and not a reflection of how the installed system will perform. On a typical 2012-era laptop with a USB 2.0 port, expect 30 to 60 seconds to reach the live desktop. From a USB 3.0 port on newer hardware, 10 to 20 seconds is common.
Once the live environment loads, check the following before proceeding to install:
Live environment verification
- Screen resolution is reasonable - not stuck at 800x600 or showing artefacts
- Wi-Fi adapter appears in the network manager (or ethernet is connected)
- Keyboard and trackpad respond correctly
- Internal storage drive is visible in the file manager or disk utility
- Sound output works (optional but worth checking now rather than later)
If any of these fail in the live environment, they will also fail after install. Address hardware compatibility issues now rather than discovering them after writing to disk. The support section has troubleshooting guidance for each of these checkpoints.
After the installer finishes and the machine reboots from its internal drive, there are a few steps most guides skip that make a real difference to the experience.
Update everything immediately
Run the full system update before doing anything else. On Debian-based systems, that is sudo apt update && sudo apt upgrade. On Fedora-based systems, sudo dnf upgrade. This pulls in kernel updates, firmware packages, and security patches. Some hardware - particularly newer Wi-Fi chipsets - will not work correctly until the kernel is updated past the version on the install media.
Install proprietary drivers if needed
Broadcom Wi-Fi, Nvidia graphics, and certain Realtek network adapters need proprietary drivers that are not included by default in most distributions. On Ubuntu and Mint, the Additional Drivers utility handles this. On other distributions, check the installer notes for driver guidance specific to common chipsets.
Verify boot time
Run systemd-analyze to see total boot time and systemd-analyze blame to identify slow services. Anything taking more than five seconds is worth investigating. Common offenders are NetworkManager wait-online (which can be disabled if you do not need network-dependent services at boot) and Plymouth splash screen processes on low-spec machines.