The moment you decide to switch
You just finished reading a thread about systemd service files and decided Windows Update is no longer acceptable. You downloaded the Fedora Workstation ISO, plugged in a USB drive, and now you are staring at a black screen with a blinking cursor. The installer never appeared. Or worse, it appeared, asked about disk layout, and you froze because you do not know what LVM means. This is the exact moment most new Linux users panic. The process is straightforward once you understand what the installer is actually doing to your drive.
What the installer actually does under the hood
Fedora does not use a traditional setup wizard that copies files one by one. It uses Anaconda, a background installer that prepares the disk, formats partitions, copies the base system, and configures the bootloader simultaneously. When you select your language and click Start Installation, Anaconda drops into a terminal-like state in the background while the GUI shows you a progress bar. It is writing block devices, setting up LVM volumes, and generating a GRUB configuration. If the USB drive is corrupted or the partition table is misaligned, Anaconda will refuse to proceed and print a traceback. Understanding this background process saves you from guessing why the progress bar stalls at 40 percent.
The live ISO you downloaded is actually a compressed root filesystem wrapped in a bootable kernel. When the firmware hands control to the USB drive, the kernel mounts the ISO as a loop device and unpacks the live environment into RAM. Anaconda then takes over. It scans your hardware, detects storage controllers, and builds a transaction plan. The plan includes formatting, package extraction, bootloader installation, and SELinux relabeling. Every step runs in a separate background thread. The GUI is just a status reporter. Trust the package manager. Manual file edits drift, snapshots stay.
Preparing the boot media
The first step is getting the ISO onto a USB drive correctly. Many users drag and drop the file into the drive's root directory. That does not work. The drive needs the ISO contents written directly to the block device so the firmware can read the boot sector. Use dd or cp with the correct device path. Never guess the device path. Run lsblk first to identify your USB drive. It will usually show up as /dev/sdb or /dev/sdc with a size matching your stick.
Here is how to write the image safely without destroying your main drive.
# List block devices to identify the USB drive letter and filesystem type
lsblk -f
# Write the ISO directly to the raw block device
# Replace /dev/sdX with your actual USB device
sudo cp Fedora-Workstation-Live-x86_64-43-1.5.iso /dev/sdX
# Flush the kernel write cache to ensure all data hits the physical media
sync
The cp command works reliably on modern Linux systems because it handles sparse files and block writes efficiently. The sync command forces the kernel to flush pending writes. Skipping sync is the most common reason for a corrupted boot drive. If you prefer a graphical tool, balenaEtcher or Fedora Media Writer handle the flush automatically. Verify the write by checking the SHA256 sum of the ISO against the checksum file provided on the download page. A mismatched checksum means the download was interrupted or the USB controller dropped packets. Verify the checksum before you reboot. A bad image wastes an hour of troubleshooting.
Walking through the Anaconda installer
Insert the USB drive and reboot. Press the boot menu key for your hardware. This is usually F12, F9, or Esc depending on the manufacturer. Select the USB drive. If you see a GRUB menu, choose the default Fedora Workstation entry. The installer will load the live environment and launch Anaconda.
The first screen asks for language and keyboard layout. Pick your options and click Start Installation. You will see a configuration dashboard. Do not rush through the Storage section. This is where you define how your data lives on the disk. The default Automatic layout creates a Btrfs root volume, a separate EFI system partition, and a swap file inside the root volume. This works for 95 percent of desktop users. Btrfs provides transparent compression and snapshot capabilities out of the box. If you select I will configure partitioning, you take full responsibility for mount points and filesystem types. Only choose manual partitioning when you need a separate /home partition or are dual-booting with strict size requirements.
Create your user account on the User Creation screen. The installer will ask for a root password. Leave it blank unless you specifically need direct root access for legacy scripts. Fedora enforces sudo for administrative tasks. The blank root password locks the root account while keeping sudo functional. This matches the security model used by Red Hat Enterprise Linux.
Click Begin Installation. Anaconda will format the partitions, copy the base packages, and configure the bootloader. The progress bar will move quickly, then pause while it installs the kernel and system libraries. Wait for the Done button to appear. Do not force a shutdown. The installer is writing the GRUB configuration and setting up SELinux contexts. Interrupting this process leaves the bootloader in an inconsistent state.
Click Reboot when prompted. Remove the USB drive only after the screen goes black. The system will drop into GRUB, load the kernel, and drop you into the GNOME login screen. Reboot before you debug. Half the time the symptom is gone.
Verifying the fresh install
Log in with your new user account. Open a terminal and run a few verification commands. The first thing to check is whether the package manager can reach the mirrors.
# Refresh the metadata cache and pull the latest package versions
sudo dnf upgrade --refresh
# Check the current kernel version and verify it matches the release
uname -r
The --refresh flag forces dnf to ignore cached metadata and fetch fresh repository information. This is the standard weekly maintenance command. If the command completes without Failed to download metadata errors, your network configuration and DNS resolution are working correctly. Check the journal for any hardware initialization warnings.
# View recent boot logs with explanatory context
journalctl -xe -b 0
The -x flag adds explanatory text to priority messages. The -e flag jumps to the end of the log. Scan for [FAILED] markers. A few warnings about missing firmware or disabled drivers are normal on fresh installs. Critical errors will show up as red text with a clear unit name. Address those before installing additional software.
When you modify system configuration, always edit files in /etc/. Files in /usr/lib/ ship with the package and will be overwritten during updates. Config files in /etc/ are user-modified. Files in /usr/lib/ ship with the package. Edit /etc/. Never edit /usr/lib/. Run journalctl first. Read the actual error before guessing.
Common pitfalls and what the error looks like
The most frequent installation failure happens during the bootloader stage. If your system uses UEFI and Secure Boot is enabled, Anaconda will attempt to sign the GRUB shim. If the machine's firmware rejects the signature, you will see a boot loop back to the UEFI setup screen. Disable Secure Boot in the firmware settings, or enroll the Fedora Machine Owner Key during installation. The installer provides a clear prompt for this.
Another common issue is the partitioning conflict. If you are dual-booting with Windows, Anaconda will detect the existing NTFS partition and the EFI system partition. It will ask whether to shrink the Windows partition or install alongside it. If you select Replace Existing System, Anaconda will wipe the entire disk. Read the confirmation dialog carefully. The installer prints Error: Transaction test error: disk /dev/sda is already mounted if you try to format a partition that the live environment is currently using. Unmount the partition in the GUI or reboot the live USB to clear the lock.
USB boot failures usually stem from a corrupted write. If the GRUB menu never appears and the system drops to a grub rescue> prompt, the ISO was not written correctly or the USB controller is faulty. Rewrite the image using dd with the conv=fsync flag, or try a different USB port. The grub rescue> prompt is not a dead end. It means the bootloader found the EFI partition but cannot locate the core image. You can manually chainload the kernel, but rewriting the drive is faster.
SELinux denials show up in journalctl -t setroubleshoot with a one-line summary. Read those before disabling SELinux. Fedora's release cadence is 6 months. The N-2 release goes EOL when N+1 ships. Plan upgrades on that cycle. If the boot menu is gone, GRUB rescue is your friend, not your enemy.
When to use Workstation versus other spins
Use Fedora Workstation when you want a complete desktop environment with GNOME, Wayland support, and automatic hardware detection. Use Fedora Server when you are deploying headless services and need minimal background processes. Use Fedora Silverblue when you require an immutable base image with atomic updates and instant rollback. Use Fedora KDE Plasma Spin when you prefer the KDE desktop environment over GNOME. Stay on the standard Workstation image if you only deviate from the defaults occasionally.