UEFI vs Legacy BIOS

Comparison chart of UEFI vs legacy BIOS showing code mode differences, GPT vs MBR boot schemes, firmware drivers, NVRAM vs CMOS, and security features such as Secure Boot, TPM, and Boot Guard

UEFI vs Legacy BIOS

Most modern laptops ship with UEFI, but the word “BIOS” is still used colloquially. This article clarifies what changes in practice when a platform uses UEFI instead of legacy BIOS—covering boot flow, disk formats, firmware architecture, security, and what these mean for repair and imaging work.

1) What UEFI Changes Compared to Legacy BIOS

  • Code model: Legacy BIOS executes 16‑bit code; UEFI runs 32/64‑bit with drivers and services.
  • Boot target: BIOS loads from the MBR boot sector; UEFI executes an EFI file from the EFI System Partition (ESP) on GPT disks.
  • Configuration: BIOS settings are limited; UEFI stores variables in NVRAM and exposes runtime services.
  • Security: UEFI introduces Secure Boot, TPM/fTPM measurements, and OEM policies (e.g., Boot Guard).

2) Boot Flow: UEFI vs Legacy

Both start with power sequencing and POST. Differences emerge at the boot hand‑off:

  • Legacy BIOS: POST → read the MBR boot sector → stage‑1 loader → OS loader.
  • UEFI: POST → find the ESP → execute an EFI application (e.g., Windows Boot Manager) → OS loader.

UEFI can enumerate multiple boot entries, load firmware drivers, and pass richer runtime services to the OS.

3) Disk & Partitioning: GPT vs MBR

  • MBR: Up to ~2 TB, four primary partitions (without extended), single boot sector.
  • GPT: Very large disks, many partitions, redundancy in headers and tables, dedicated ESP.

For modern deployments and large NVMe drives, UEFI + GPT is the norm.

4) Firmware Architecture

  • Legacy BIOS: Monolithic, minimal services; relies heavily on OS loaders.
  • UEFI: Phased design (SEC → PEI → DXE → BDS/RT), firmware drivers, NVRAM variables, capsule updates; integrates with platform regions (Intel ME / AMD PSP).

5) Security Model & Repair Implications

  • Secure Boot validates boot components; unsigned or tampered images won’t run.
  • TPM stores keys/measurements; used for BitLocker and measured boot.
  • Boot Guard (OEM policy) verifies firmware authenticity at very early stages.

For technicians: after reflashing, a board may still refuse to boot if signatures or ME/PSP regions don’t match OEM policy. Keep a known‑good pre‑programmed BIOS chip for A/B isolation; always preserve or restore DMI/Serial/UUID/MAC.

6) Compatibility Notes

  • Cloning drives between systems? Match the firmware mode: legacy images expect MBR; UEFI images expect GPT + ESP.
  • Legacy OS installers may require Legacy/CSM mode; modern OS should use UEFI.

Summary

  • UEFI is the modern, extensible successor to legacy BIOS.
  • UEFI improves boot flexibility, disk support (GPT), and security—but adds signature policies that affect repairs.
  • For current laptops, default to UEFI + GPT; switch to legacy only for specific compatibility reasons.

Further Reading

Shop & Learn

Browse BIOS chips

Programmers & adapters

BIOS Guide Hub

0 comments

Leave a comment