Here's a puzzle beginners rarely stop to notice: the operating system lives on the storage drive… but something has to know how to read the storage drive before any operating system is running. What reads the thing that everything else loads from? The answer is firmware — permanent software burned into a chip on the motherboard, awake the instant power arrives.
The night-watchman routine
Press the power button and the firmware runs the same checklist every time: check the CPU responds, count the RAM, take inventory of connected drives and devices (old-timers call this POST — the power-on self test), then find a drive containing an operating system, hand control over, and step back. The whole handover takes a few seconds. Those beeps an old PC makes when RAM is missing? That's the firmware reporting a failed checklist in the only language available before graphics exist.
BIOS vs UEFI: same job, forty years apart
BIOS is the 1980s original — keyboard-only blue screens, tight limits (it can't even boot from drives over 2TB). UEFI is its modern replacement: mouse support, faster startup, big-drive support, and networking before the OS even loads. Everything made in the last decade uses UEFI, though everyone still says "the BIOS" the way people still say "hang up" about phones. In practice the terms get used interchangeably; in exams and documentation, the distinction matters.
Secure Boot — the firmware as doorman
UEFI's most consequential feature: before handing over control, it checks the operating system's digital signature — proof the OS hasn't been tampered with. This blocks a particularly nasty malware family (bootkits) that infect the startup process itself to load before any antivirus can. When Windows 11 demanded Secure Boot and TPM support as installation requirements, this firmware layer suddenly became every IT department's problem.
Firmware updates follow a different rule from normal updates. A failed app update is an inconvenience; a failed firmware update — power cut mid-flash — can permanently kill a motherboard. The professional convention: update firmware to fix a specific problem or patch a security advisory, not just because a newer version exists. When you do, use mains power, never battery.
You'll meet firmware constantly in real work: changing boot order to reinstall an OS, enabling virtualisation for developers, troubleshooting Secure Boot conflicts, and pushing coordinated firmware updates across a fleet. It's a small layer — but it's the foundation every other layer stands on.