If a computer won't start, the fix often begins with boot methods. In CompTIA A+ (220-1202), Core 2, Domain 1, Objective 1.2, you're expected to know how a system can start from different sources, and why a technician might choose one over another. A boot method is simply the way a PC starts an operating system or a recovery tool, based on what the firmware is told to try first.
Techs change boot methods for practical reasons: to install an OS, run repairs, capture or restore an image, or recover data from a failing drive. The same PC can boot several ways because its firmware checks devices in a set order, and it will switch paths when one option isn't available or isn't bootable.
This guide explains the common boot methods you'll see on the exam and on the bench: USB, network, solid-state or flash media, internet-based recovery, external or hot-swappable drives, internal partitions, and multiboot setups.
What boot methods are and how a PC chooses one
A boot method describes the approach used to start a system, such as booting from USB, from the internal drive, or over the network. A boot device is the thing the firmware tries, like a specific SSD, a USB stick, or a network adapter. Boot order is the priority list that tells the firmware which devices to try first.
At a high level, the boot process follows a predictable chain. First, the system powers on and the firmware runs basic checks (like detecting memory and storage). Next, it looks for a bootable option based on the configured boot order. Then it hands control to a bootloader (a small program that knows how to start an operating system or recovery environment). Finally, the OS loads drivers and services, and you reach the login screen.
The selected method depends on three things:
- Firmware settings (boot order, secure boot policies, and whether USB or network boot is allowed)
- Available hardware (a connected USB drive, a working internal SSD, a supported network card)
- Admin policy (enterprise rules for imaging, encryption, and approved tools)
Techs switch boot methods for clear, job-driven reasons:
- OS installation or repair: start Windows Setup or a recovery environment
- Malware cleanup: scan offline so malware can't defend itself
- Disk cloning and imaging: capture a reference image or restore one fast
- Failed or missing drive: boot from external media to confirm hardware issues
- Firmware update utilities: run vendor tools that require a bootable device
A boot method is less about "what you prefer" and more about "what the system can trust and access right now."
Boot order, one-time boot menus, and when to use each
Changing boot order in firmware settings makes a persistent change. The system will keep trying that device first until someone changes it back. This works well for planned deployments, such as a lab where every machine should network boot for imaging.
A one-time boot menu (often opened with a function key during startup) makes a temporary choice. The system boots from your selected device once, then returns to its normal order on the next restart. For most service tasks, this is safer because it reduces surprises for the user.
Persistent changes carry a real risk. A PC might keep trying to boot from an empty USB port, or it might hit a network boot prompt and confuse a non-technical user. For that reason, many technicians rely on the one-time menu during installs and troubleshooting, then confirm the internal drive returns to the top of the list.
How to confirm what the system actually booted from
After startup, don't guess. Confirm the boot source and document it, especially if you changed settings.
On Windows, practical checks include looking at Disk Management to see which disk holds the system volume and which partition is marked for boot functions. File Explorer can also help you verify whether removable media is mounted, and whether you are running tools from a USB drive versus the internal disk. In managed environments, you may also confirm whether a deployment agent is running, or check logs that indicate a PXE or imaging workflow completed.
When you finish service, record what you changed (boot order, secure boot, or device enablement). Then restore normal startup and run a final restart test. That last reboot is your proof the system is ready to hand back.
Local boot options: internal drives, partitions, and removable media
Local boot methods start from hardware connected to the machine. In everyday support work, they are popular because they don't require servers or special network settings. They also tend to be faster and more predictable than remote methods, assuming the storage is healthy.
The CompTIA A+ boot method list includes internal hard drive (partition), solid-state or flash drives, USB, and external or hot-swappable drives. Each option has a typical role. Internal storage supports normal startup. USB handles most repair and install workflows. External drives often carry images and tools. Flash media can work in the field, but it has limits.
Here's a quick comparison to frame the trade-offs:
| Boot method (local) | Typical speed | Reliability | Common use cases |
|---|---|---|---|
| Internal hard drive (partition) | High | High (if disk is healthy) | Normal boot, built-in recovery |
| USB flash drive | Medium | Medium | OS install, repair tools, offline scans |
| SD or other flash media | Low to medium | Low to medium | Lightweight tools, field kits |
| External HDD or SSD | Medium to high | Medium | Imaging, data recovery, portable diagnostics |
In practice, boot failures often come from simple mistakes. The system might select the wrong device because of boot order. A tech might pick the wrong partition during repair.