BIOS vs UEFI: What’s the Difference?
“BIOS” is often used as a catch‑all term for firmware, but most modern laptops actually use UEFI. This article explains the practical differences technicians should know: how they boot, how they store configuration, what each supports (GPT vs MBR, 32/64‑bit, drivers), and why UEFI security changes your repair workflow.
1) Quick Definitions
- BIOS (Basic Input/Output System): Legacy firmware model that initializes hardware and passes control to a bootloader. Traditionally runs in 16‑bit mode and uses MBR disks by default.
- UEFI (Unified Extensible Firmware Interface): The modern replacement. Runs 32/64‑bit code, supports drivers and services in firmware, and typically boots from GPT disks.
2) Boot Flow Differences
- BIOS: POST → read boot sector (MBR) → load stage‑1 bootloader → OS loader.
- UEFI: POST → locate EFI System Partition (ESP) → execute an EFI application (e.g., Windows Boot Manager) → OS loader.
UEFI can enumerate files in the ESP, select entries from NVRAM boot variables, and load runtime drivers. That flexibility makes recovery and multi‑boot easier—but also adds security checks that can block tampered images.
3) Disk & Partitioning
- BIOS: MBR partitioning (up to 2 TB, four primary partitions without extended).
- UEFI: GPT partitioning (very large disks, many partitions, redundancy in headers).
4) Firmware Architecture
- BIOS: Monolithic, limited services; relies on OS loaders for complex needs.
- UEFI: Modular phases (SEC/PEI/DXE), drivers, and runtime services; stores settings in NVRAM; integrates with platform regions (e.g., Intel ME / AMD PSP) and capsule updates.
5) Security Model
- BIOS: Minimal signature checks; recovery often unrestricted.
- UEFI: Secure Boot signature validation, TPM/fTPM measurements, OEM policies like Intel Boot Guard, rollback protection. These features improve trust but can prevent boot when images are unsigned, corrupted, or mismatched.
6) Compatibility & Use Cases
- Legacy/older OS (or imaging tools that expect MBR) → BIOS/legacy mode can be simpler.
- Modern OS & large disks → UEFI with GPT is recommended; faster boot, more robust disk layout, better security.
7) Technician Notes
- When replacing or reflashing the firmware chip, UEFI platforms may enforce signatures (Boot Guard). If boot fails after a “good” flash, re‑check vendor keys/policy and the ME/PSP region integrity.
- For drive cloning, validate that the target firmware setting (UEFI vs Legacy) matches the cloned image’s boot scheme (GPT vs MBR).
- Keep a known‑good pre‑programmed BIOS chip for fast A/B isolation when a board shows black screen or boot loop.
Comparison Table
| Aspect | BIOS (Legacy) | UEFI (Modern) |
|---|---|---|
| Code Mode | 16‑bit | 32/64‑bit |
| Disk Scheme | MBR | GPT + ESP |
| Drivers | Minimal | UEFI drivers in DXE |
| Config Storage | CMOS/NVRAM (limited) | NVRAM variables |
| Security | Basic | Secure Boot, TPM, Boot Guard |
| Updates | Vendor tools | Capsule updates + vendor tools |
0 comments