Lesson 5 of 60 beginner

Boot Process & Firmware

From power button to login screen

Open interactive version (quiz + challenge)

Real-world analogy

Booting is like opening a theater before a show: lights on, doors unlocked, staff check themselves, tickets loaded, seats ready, doors open to the audience. If any step fails, the show doesn’t start — and you have to know which person to talk to.

What is it?

The boot process is a sequence: firmware (BIOS/UEFI) initializes hardware, reads the boot device, loads the bootloader, which loads the OS kernel, which starts drivers, services, and finally presents a login screen. A stall at any stage tells you exactly where to look.

Real-world relevance

A corporate laptop won’t boot after a power outage. A junior recognizes ‘Automatic Repair loop’ as an OS integrity issue, boots to WinRE, runs startup repair + bootrec commands, and captures logs — instead of reinstalling Windows and destroying user data.

Key points

Power on → firmware → bootloader → kernel → services → login — Every modern PC goes through this chain. If it fails at any stage, the symptom tells you where to look. Knowing the chain lets you diagnose instead of guess.
BIOS vs UEFI — BIOS is the older firmware. UEFI is the modern replacement — faster, supports larger disks, Secure Boot, and a richer interface. Enterprise laptops are almost all UEFI + Secure Boot today.
Boot order and boot devices — Firmware tries devices in a configured order: internal NVMe → USB → network (PXE). If your laptop won’t boot, check boot order first — someone may have plugged in a USB or changed the list.
MBR vs GPT — MBR supports up to 2 TB and 4 primary partitions. GPT is modern, supports huge disks and many partitions. Modern UEFI systems use GPT.
Common boot failures and what they mean — ‘No bootable device’ → boot order or disk issue. ‘Operating system not found’ → corrupted bootloader. ‘Automatic Repair loop’ → OS integrity. Blue screen early in boot → driver or disk driver problem.
Recovery tools a junior should know — Windows Recovery Environment (WinRE), Startup Repair, bootrec commands (bootrec /rebuildbcd, /fixmbr, /fixboot), safe mode, last known good config, and a bootable USB with diagnostic tools.
When to touch BIOS/UEFI settings — Only to change boot order, enable/disable Secure Boot (for specific OS installs), enable virtualization (VT-x/AMD-V), or toggle TPM for BitLocker. Document every change. Never flash firmware unless required and approved.

Code example

// The full boot chain (Windows example)

Power on
  |
  v
Firmware (BIOS / UEFI) runs POST
  |
  v
Firmware reads boot order -> finds a valid boot device
  |
  v
Bootloader (bootmgr / Windows Boot Manager) loads
  |
  v
Kernel (ntoskrnl.exe) + HAL load drivers
  |
  v
Session Manager (smss.exe) starts
  |
  v
Services start (Winlogon, LSA, etc.)
  |
  v
Login screen appears

Line-by-line walkthrough

1. Boot chain diagram
2. Power on — signal reaches firmware
3. POST — hardware self-check
4. Firmware picks a boot device from the ordered list
5. Bootloader is located and loaded
6. Kernel and hardware abstraction layer load
7. Session Manager spawns
8. Services come up
9. Login screen is rendered

Spot the bug

User reports: 'Laptop shows Automatic Repair loop every morning. I keep cancelling it.'

Need a hint?

Cancelling means you never let the OS attempt repair. What should you do BEFORE reinstalling?

Show answer

Let Automatic Repair finish. If it still fails, boot into WinRE, run Startup Repair, then bootrec /rebuildbcd, /fixmbr, /fixboot if appropriate. Check disk health (SMART/chkdsk). Only reinstall after confirming disk is healthy and data is backed up. Document steps in the ticket.

Explain like I'm 5

A computer starts like an airport in the morning: staff check everything, the runway opens, the plane (Windows) is cleared to land. If the runway isn’t ready, the plane waits. That waiting is your boot error message.

Fun fact

Early PCs took so long to POST that engineers added beep codes specifically to tell you which component failed — because there was no screen output yet. Beep codes are still useful on modern enterprise hardware.

Hands-on challenge

Reboot your own PC and enter UEFI setup (often F2/F10/F12/DEL). Without changing anything, note: firmware version, boot order, Secure Boot state, TPM state. Exit without saving. You just performed the first step of a real hardware triage.

More resources

Windows boot process (MS) (Microsoft Learn)
UEFI Specification overview (UEFI Forum)
BIOS vs UEFI explained (Professor Messer)

Open interactive version (quiz + challenge) ← Back to course: IT Jobs Bootcamp