For CompTIA A+ Core 2 (220-1202), Domain 3.0 Software Troubleshooting, Objective 3.1 (Given a scenario, troubleshoot common Windows OS issues), the startup error No OS found is a classic case where the PC fails before Windows even loads. The message can look simple, yet it points to several possible causes, from a wrong boot target to a damaged bootloader, or even a dying drive. Because the failure happens early, good troubleshooting depends on order and restraint. This article explains why the error appears, how to confirm the cause, and the safest fixes, starting with basic BIOS or UEFI checks and ending with Windows recovery steps.
Think of startup like a relay race. If the first runner drops the baton, the rest of the team never starts. Your goal is to identify where the baton gets dropped, then fix only that part.
Why you get a "No OS found" error at startup
A modern PC starts in stages, and each stage depends on the one before it. First, firmware (BIOS or UEFI) powers up hardware and runs basic checks. Next, it searches for a bootable device based on its boot order. After that, it loads a bootloader from that device. Only then can Windows begin to load its kernel and drivers.
A "No OS found" message usually means the chain breaks before Windows starts. You might also see "Operating system not found" or "No bootable device". Although the wording differs, the practical meaning is often similar: the firmware did not find a valid boot path on the device it tried to boot from.
This is why the error feels abrupt. Windows did not fail, because Windows never started. Instead, the system stopped at the firmware and bootloader stage.
Mode also matters. Many systems can boot in UEFI mode or Legacy BIOS mode (often via CSM, Compatibility Support Module). Those modes expect different disk formats and boot files. If firmware mode does not match how Windows was installed, the firmware may see the drive but still refuse to boot.
The table below summarizes the most common "same problem, different message" scenarios.
| Message on screen | What it often means | Where the failure occurs |
|---|---|---|
| No OS found | Boot device has no valid boot files | Firmware to bootloader handoff |
| No bootable device | Firmware can't find a bootable target | Device selection stage |
| Operating system not found | Boot code can't locate an OS loader | Boot sector or EFI stage |
The main takeaway is simple: treat these errors as pre-Windows failures, then troubleshoot from hardware detection upward.
Boot order, wrong drive, or unplugged storage
Sometimes the PC is fine, but it's looking in the wrong place. Firmware always follows a priority list. If that list changes, the system may try to boot from a device that has no operating system.
External devices often trigger this, even by accident. A USB flash drive used for backups can become the first boot device. An empty SD card slot can show up as a "removable" boot option. On desktops, a new storage drive can shift the boot order after a BIOS update or reset.
Start with quick, low-risk checks:
- Disconnect USB drives and external disks, then reboot.
- Remove any SD cards, even if they look irrelevant.
- Enter BIOS or UEFI setup and confirm the internal SSD or HDD appears.
- Set the internal Windows drive (or "Windows Boot Manager" in UEFI systems) as the first boot option.
If the internal drive doesn't appear at all, stop here and switch to hardware detection steps. Firmware can't boot what it can't see.
UEFI vs Legacy mode and Secure Boot conflicts
Windows installed in UEFI mode normally uses a GPT disk with an EFI System Partition (ESP) that stores boot files. Windows installed in Legacy mode typically uses an MBR disk with boot code in the master boot record and a system partition marked active.
Problems arise when someone toggles firmware settings after installation. If you switch from UEFI to Legacy (or the reverse), the firmware may no longer recognize the boot method on that disk. Secure Boot can add friction too, especially after firmware resets, drive cloning, or changes to boot entries.
A simple rule helps on both the exam and real systems: match the firmware boot mode to the way Windows was installed. If the machine previously worked and no one reinstalled Windows, a sudden mismatch usually comes from a BIOS reset, a firmware update, or someone "trying options."
Before changing settings, write them down or take photos. That record helps you undo a change that makes symptoms worse.
If a system worked yesterday and shows "No OS found" today, assume a boot target or firmware setting changed, until you prove the disk failed.
Fast triage: confirm the cause before you try fixes
When you see "No OS found," it's tempting to jump into repairs. However, fast troubleshooting depends on confirming the failure point.