By You press the power button, the fans spin up, and then you stare at a black screen or a "boot device not found" message with no idea what actually happens between that button and your desktop. This page breaks down the exact sequence a bootloader follows to load your operating system, so you can tell which stage failed when it does not boot.
In short: A bootloader is a small program that runs after firmware and before your OS. It finds the kernel file on your drive, copies it into RAM, and hands the CPU over to it. If that handoff fails, you get a frozen screen or a missing boot error, and the fix depends on which stage broke.
Our pick
Tap to see today's price on AmazonLets you boot into repair tools to fix a damaged bootloader or missing system files without reinstalling the OS.
What a bootloader actually does in plain words
Think of your hard drive as a library and the kernel as a specific book. The bootloader is the librarian who finds that book, checks out the copy, and hands it to you. Without it, the library is just shelves of data with no instruction on which item to open first. If that sounds like your bench, read up on how systems start up next.
Firmware, like UEFI or legacy BIOS, is the building guard. It powers the building, checks the doors, and then hands the keys to the librarian. The librarian does the specific work of getting the right file.
When a PC fails to boot, the problem is rarely the “book” (your installed Windows or Linux). It is almost always the librarian (the bootloader) or the handoff between the guard and the librarian.
- Firmware initializes hardware and finds a bootable device.
- Bootloader locates the kernel and initramfs files.
- Kernel takes control and loads the rest of the OS.
Pro tip: If you see a GRUB menu or a Windows boot manager screen, the firmware succeeded and the bootloader is running. If you see a black screen immediately after the logo, the firmware-to-bootloader handoff likely failed.
The three stages from power button to kernel start
Stage 1: Firmware initialization. The CPU starts in a minimal state. The firmware runs a Power-On Self-Test, detects available RAM, and identifies which drive to boot from. This stage is locked inside the motherboard chip and cannot be changed by software updates.
Stage 2: Bootloader execution. Firmware loads the bootloader into memory. On UEFI systems, this is an “.efi” file from the EFI System Partition. On legacy BIOS, it is the Master Boot Record code. The bootloader now has enough tools to read your file system.
Stage 3: Kernel handoff. The bootloader finds the kernel image, decompresses it into a reserved memory region, and jumps execution to the kernel’s entry point. The kernel then starts loading drivers and launching the graphical login screen. Before you buy anything, it is worth looking at process before os loads.
- Press power button.
- Firmware POST and device scan.
- Bootloader loads and runs.
- Kernel loads into RAM.
- OS userspace starts.
Safety first: Never attempt to edit bootloader files on a work or school device. These systems are locked down, and modifying them can violate security policies or trigger disk encryption locks.
BIOS versus UEFI: why the boot path differs
Legacy BIOS systems use a simple search. Firmware scans drives for a specific signature in the first 512 bytes. If found, it loads that tiny chunk of code. This code is too small to understand modern file systems, so it must load a second, larger piece of code.
UEFI systems are more complex. The firmware itself understands GPT partition tables and FAT file systems. It reads a larger bootloader file directly from the EFI System Partition. This allows features like Secure Boot, which verifies a digital signature before running the code.
This matters when you reinstall your OS or replace your drive. If you install Windows in UEFI mode, the bootloader lives in a specific ESP partition. If you install it in Legacy mode, it lives in the MBR. Mixing these modes is a common cause of “no bootable device found.”
| Feature | Legacy BIOS | UEFI |
|---|---|---|
| Partition style | MBR or GPT | GPT |
| Bootloader size | 512 bytes | ~2 MB file |
| Security | None | Secure Boot |
| Max drive size | 2 TB | Unlimited |
Pro tip: Check your firmware settings to see which mode your PC is currently using. On Windows, open Settings > System > About and look under Device specifications for "BIOS mode." If it says UEFI, do not switch to Legacy without reinstalling the bootloader.
How the kernel gets loaded into memory
The kernel is usually stored compressed on disk to save space. The bootloader’s job is to find this compressed file, read it into RAM, and then decompress it in a specific memory location. This location is reserved so the rest of the operating system does not overwrite it. We cover pc boot sequence in a guide of its own.
Before jumping to the kernel, the bootloader must tell the CPU to switch from its initial 16-bit mode to 32-bit or 64-bit mode. The kernel expects to start in this newer mode. If the bootloader forgets this switch, the kernel will crash immediately after loading.
The bootloader also fills a data structure with important info: where the memory map is, where the initial RAM disk (initramfs) is, and what command-line arguments the user typed. The kernel reads this structure as its very first act.
- Decompression: Expands the kernel file in RAM.
- Mode switch: Changes CPU to protected or long mode.
- Data handoff: Fills the boot_params structure.
- Jump: Executes the first kernel instruction.
When the bootloader fails: three common real-world scenarios
Scenario 1: Dual boot confusion. You install Linux next to Windows. The Linux bootloader takes over the boot process but does not see the Windows entry. You now only get a Linux menu. The bootloader is working, but its configuration file is missing the Windows entry.
Scenario 2: Deleted EFI partition. A disk cleanup tool or a hard drive reset wipes the small EFI System Partition. The firmware boots, but has no file to read. You get a generic “Boot device not found” error. The hardware is fine; the librarian file is gone.
Scenario 3: Corrupt bootloader file. A power outage during an OS update breaks the bootloader file. The firmware tries to load it, hits a bad sector, and hangs. The screen stays black after the manufacturer logo.
Each scenario has a different fix. Scenario 1 is a config edit. Scenario 2 is a partition rebuild. Scenario 3 is a file repair. Knowing which one you have saves hours of trial and error. Loaders in this spot often ask about multi-os setup specs as well.
Boots you into a Windows recovery environment where you can run command-line tools to rebuild the EFI partition or repair the bootloader files.
See options on AmazonMyths about bootloaders and what actually happens
Myth: The bootloader is part of the operating system.
Fact: The bootloader is independent of the OS. You can have the same bootloader load Windows, Linux, or even a live USB. It is a bridge, not a component of the final system.
Myth: If the screen is black, the hard drive is dead.
Fact: The drive is likely fine. A black screen after the logo usually means the firmware found the drive but could not execute the bootloader file, or the bootloader could not find the kernel.
Myth: Reinstalling the OS fixes all boot problems.
Fact: Reinstalling the OS often wipes the bootloader and starts the process over. For a missing bootloader, a targeted repair is faster and safer than a full reinstall.
Myth: Secure Boot prevents all malware.
Fact: Secure Boot only verifies that the bootloader has a valid digital signature. A signed bootloader can still be exploited, though it blocks the most common rootkit attacks that replace the boot process.
The bottom line
Most boot failures happen at the firmware-to-bootloader handoff or the bootloader-to-kernel jump. For Windows systems, use a recovery USB to rebuild the EFI partition or repair the boot files. For Linux systems, boot from a live USB to access and repair the bootloader configuration. If the drive itself is not detected by firmware, the problem is hardware, not software.
Frequently asked questions
How do I know if my PC uses BIOS or UEFI?
On Windows, press Windows key + X and select System. Look under “Device specifications.” If it says UEFI, it is UEFI. If it says BIOS, it is legacy. You can also check the firmware settings screen, which will look very different for UEFI (usually a graphical interface) versus legacy BIOS (text-based). We go through apple operating system explained step by step in its own article.
Can I update a bootloader without reinstalling the OS?
Yes. On Linux, you update the bootloader with standard system package updates. On Windows, you use the built-in recovery tools or the Windows Recovery Environment to rebuild the boot files. You do not need to reinstall the entire operating system for a standard bootloader update.
What happens if the bootloader cannot find the kernel?
The bootloader will usually display an error message like “error: no such device” or “Failed to load kernel” and drop you into a command prompt (on Linux) or a generic blue screen (on Windows). The computer is stuck because it has loaded the librarian but not the book. You must fix the file path or the partition containing the kernel.
Does the bootloader affect Windows performance after boot?
No. Once the kernel has taken over, the bootloader is no longer running in memory. Its only job is the handoff. Windows performance issues are related to drivers, disk speed, and RAM, not the bootloader itself.
Can I have two bootloaders on one drive?
Yes, but only one is active at a time. The firmware loads the one it is pointed to. You can configure the active bootloader to chain-load the other one, which is how dual-boot systems work. However, editing this chain can be tricky and requires precise configuration file edits.