Every time you press the power button, decades of engineering history play out in a few seconds. The way Windows boots today is almost unrecognizable compared to the MS-DOS era, and tracing that evolution explains a lot about why modern boot is so much faster and harder to break.
The MS-DOS and Windows 9x Era
Early PCs booted via BIOS reading a Master Boot Record (MBR), which loaded IO.SYS and MSDOS.SYS, eventually handing off to COMMAND.COM. Windows 95/98 booted DOS first, then loaded the graphical shell on top — which is why a corrupted AUTOEXEC.BAT could still land you at a DOS prompt.
NT Architecture: A Clean Break
Windows NT (and its descendants, up through XP) replaced this with NTLDR reading boot.ini to locate the OS partition, then handing off to the NT kernel — a fundamentally different, more robust design that separated the boot loader from the OS itself.
Vista Onward: BOOTMGR and UEFI
Windows Vista introduced BOOTMGR and the Boot Configuration Data (BCD) store, replacing the old text-based boot.ini. Combined with UEFI’s replacement of legacy BIOS starting around Windows 8, this is the boot chain still in use today: UEFI firmware → BOOTMGR → winload.efi → the NT kernel.
Inspecting Your Own Boot Configuration
# View the current boot configuration data bcdedit /enum # Check whether you're booting via UEFI or legacy BIOS Confirm-SecureBootUEFI
Why This History Still Matters
Understanding this chain is what lets you actually fix a “boot device not found” error instead of just reinstalling Windows — knowing whether the failure is in firmware, the boot manager, or the kernel itself tells you exactly which tool to reach for.