Installation media

On this page 7

Installation media is the physical or virtual carrier that holds the files needed to install an operating system or application on a computer, such as a USB flash drive, an optical disc, an ISO image or a network boot source. Within the Installation & packages topic of Software, it is the starting point of the delivery chain: before an installer can run or a package manager can resolve dependencies, the bits must reach the target machine from a trusted, readable source.

The term covers both bootable media, which start a computer before any operating system exists on the internal disk, and non-bootable media, which simply carry setup programs or packages for a system that is already running. The distinction matters because bootable media must satisfy firmware requirements, while non-bootable media only need a readable file system.

How installation media starts a computer

Bootable installation media works by presenting the firmware with a recognized boot structure that loads a small setup environment into memory. On modern PCs, UEFI firmware looks for an EFI System Partition formatted with FAT32 and an executable at a standard path such as \EFI\BOOT\BOOTX64.EFI. Older legacy BIOS systems instead read a boot sector in the first 512 bytes of the device.

Once loaded, the setup environment is usually a minimal operating system that runs entirely from RAM or from the medium itself. Windows uses Windows PE, many Linux distributions use a live system or a dedicated installer image, and macOS uses a recovery environment. This environment partitions the target disk, copies or extracts the system image and configures the bootloader.

Secure Boot adds a verification step: the firmware only runs boot code signed by a trusted key. Media built from official images normally pass this check, while media altered by third-party tools may fail with a signature violation unless Secure Boot is reconfigured. The table below lists the main boot paths and what each expects from the medium.

Boot pathRequired structureTypical file systemMain constraint
UEFI bootEFI System Partition with boot loaderFAT324 GB file size limit on FAT32
Legacy BIOS bootMaster boot record boot codeFAT32, NTFS or ISO 9660Obsolete on most new hardware
Optical bootEl Torito boot catalogISO 9660 or UDFRequires an optical drive
Network boot (PXE)DHCP and TFTP or HTTP serverServed over the networkNeeds prepared infrastructure
Boot paths and what they require from the medium

Types of installation media

Installation media has evolved from floppy disks and CDs toward USB drives, disk images and network delivery. Each type balances capacity, speed, cost and the infrastructure it needs. Physical media remain essential for bare-metal installation and recovery, while virtual media dominate in virtualization and cloud environments.

MediumTypical capacityStrengthWeakness
USB flash drive8-256 GBFast, rewritable, universalEasy to lose or tamper with
DVD or Blu-ray disc4.7-50 GBRead-only, hard to alterSlow and drive-dependent
ISO image fileMatches the source imageEasy to download and verifyMust be written or mounted first
Virtual mounted imageMatches the source imageIdeal for virtual machinesOnly works in hypervisors or mounts
Network installation sourceUnlimited in practiceScales to many machinesDepends on network services
Common forms of installation media

An ISO image is a sector-by-sector archive of an optical disc file system, typically ISO 9660 or UDF. Many Linux distributions publish hybrid ISO images that contain both an optical boot catalog and a disk partition table, so the same file can be burned to a disc or written directly to a USB drive.

Creating reliable installation media

Reliable media creation starts with verifying the source image before writing it. Vendors publish cryptographic checksums, usually SHA-256, and often a detached GPG signature. A matching checksum proves the download is intact; a valid signature additionally proves that the image came from the publisher.

Writing methods fall into two families. Raw image writing copies the image byte for byte to the device, as dd on Unix-like systems does, which preserves hybrid boot structures exactly. File extraction formats the drive and copies files into a new file system, which is how vendor creation tools for Windows usually work and which allows splitting files that exceed the FAT32 4 GB limit.

The following table matches common situations with a suitable creation approach.

SituationRecommended approachReason
Linux hybrid ISO to USBRaw image writingKeeps both boot paths intact
Windows setup on a UEFI PCVendor creation toolHandles large image files correctly
Many images on one driveMulti-boot loader toolAvoids rewriting the drive each time
Virtual machine installMount the ISO directlyNo physical device is needed
Fleet of office computersNetwork boot deploymentRemoves per-machine media handling
Choosing a media creation approach

A common error is selecting the wrong target device in a raw writing tool. Because raw writing overwrites the whole device without confirmation in many command-line tools, a wrong device name can destroy data on an internal disk. Careful administrators confirm the device by size and model before writing.

Installation media is one of several ways to put software onto a system, and it differs from neighbors such as a software package or a deployment pipeline in scope and timing. Media usually carries an entire product or operating system, while packages carry individual components that a package manager installs into an existing system.

ConceptWhat it deliversWhen it is usedNeeds a running system
Installation mediaComplete system or productInitial setup or recoveryNo, if bootable
Software packageOne component with metadataAdding or updating softwareYes
Online installerSmall stub that downloads filesSetup on connected machinesYes
System image deploymentPrebuilt disk imageMass provisioningNo, uses a boot environment
How installation media differs from related concepts

Offline installers sit between these categories: they bundle every required file so that installation succeeds without internet access, which makes them a form of installation media for air-gapped environments. Online installers are smaller but fail when the download source changes or disappears.

Limitations, risks and common mistakes

The main risk of installation media is supply-chain tampering: a modified image can install a backdoored system that looks normal. Downloading only from official sources and checking signatures is the decisive defense. In regulated environments, organizations keep verified golden copies of media in controlled storage.

  • Outdated media installs a system that is missing months of security fixes, so the first boot should be followed immediately by updates.
  • Mismatched boot mode occurs when media boots in legacy mode on a UEFI machine, producing a disk layout that the firmware will not boot later.
  • Cheap or worn USB drives cause silent read errors that appear as random installer crashes rather than clear media faults.
  • Missing storage drivers prevent the installer from seeing the target disk, especially on new RAID or NVMe controllers.
  • Reusing media without wiping can leave stale partitions that confuse firmware boot menus.

Put simply

Installation media is the delivery vehicle for new software. Think of it as the moving truck that brings furniture to an empty house. Without the truck, nothing arrives, no matter how good the furniture is.

Most people today use a USB stick or a downloaded image file instead of a disc. A special kind of media can even start a computer that has no system on it yet. The key point is simple: get the media from the official source and check it, because a tampered copy installs a tampered system.

In practice

An IT technician at a twelve-person accounting office needs to replace a failed laptop drive. She downloads the official operating system image on a working computer, compares its SHA-256 checksum with the value on the vendor page and writes it to a 16 GB USB drive with the vendor creation tool.

The laptop is set to boot in UEFI mode with Secure Boot enabled, and it starts from the USB drive without any firmware changes. The installer does not see the new NVMe disk at first, so she loads the storage driver from a second folder on the same drive. Setup completes in about 25 minutes, after which she installs all pending updates before handing the laptop back. The labeled USB drive goes into the office recovery kit, with a note to refresh the image every quarter.