> ## Content Index > Fetch the complete content index at: https://www.winsolvetech.com/llms.txt > Use this file to discover other available public pages before exploring further. # Common Boot Errors and Solutions by Error Message - URL: https://www.winsolvetech.com/common-boot-errors-solutions/ - Published: 2026-10-03T22:20:16.000Z - Updated: 2026-10-03T22:20:16.000Z - Author: MD Syful Islam Rasel - Tags: Boot Issues, Error Fixes [A boot error usually](https://www.winsolvetech.com/troubleshoot-computer-boot-problems/) means the machine can’t find a valid startup path, not that it’s dead. Start with the safest checks: unplug external devices, confirm the boot order in BIOS/UEFI, and make sure the internal SSD or HDD is still detected. If the drive is present but the machine still won’t start, the problem is usually boot files, firmware settings, or a recent hardware change. ## What the boot message is really pointing to Before you start: this applies to Windows laptops and desktops, including systems that use BIOS or UEFI firmware. You do not need Administrator rights just to check the error, unplug peripherals, or enter BIOS/UEFI, but you may need Administrator rights [later if you boot](https://www.winsolvetech.com/boot-troubleshooting-faqs/) into Windows recovery tools from inside Windows. A restart is part of the process, and you should back up files first if the machine still boots sometimes. The exact message varies, [but boot errors usually](https://www.winsolvetech.com/fix-boot-configuration-data-errors/) fall into four buckets: the drive is not being detected, the firmware is pointing at the wrong startup device, the Windows boot files are damaged, or a hardware change upset the setup. If the machine powers on but cannot find a disk, think drive detection or boot order first. If the drive shows up in BIOS/UEFI but the error names the operating system, think boot files or partition damage. If the error began right after an update, storage setting change, or parts swap, that change is a strong clue. A simple way to narrow it down is this: - No drive listed in BIOS/UEFI: suspect the SSD/HDD, cable, slot, or motherboard connection. - Drive listed, but no startup: suspect boot order, UEFI vs legacy mismatch, or missing boot files. - Error appears after changing BIOS settings or reinstalling hardware: suspect a storage mode or compatibility change. - Freezing before any error: could be display, RAM, or a failing drive that is hanging the startup process. If you can still reach BIOS/UEFI, that is the fastest place to sort out which layer is failing. ```text No bootable device Boot device not found Operating system not found Inaccessible boot device ``` Error These are the common messages this guide covers. The exact message varies by maker, but the fix usually depends on whether the drive is missing, the boot order is wrong, or the boot files are damaged. ## If it says "No bootable device" or "Boot device not found" This message usually means the firmware looked for a startup device and did not find one it can use. Start with the least risky checks: unplug USB drives, memory cards, external disks, and docks, then restart. A stray USB stick or an external drive can pull priority away from the internal SSD or HDD. Next, enter BIOS/UEFI and confirm the internal drive appears in the storage list. The settings path varies by maker, but it is usually under Storage, Main, Boot, or Information. ```text BIOS/UEFI > Boot ``` Settings path If the drive is detected, check that the internal SSD or HDD is first in boot order. If you see both `UEFI` and `Legacy` options, match the mode to how Windows or the other operating system was installed. Most modern systems use UEFI. A mismatched mode can make a healthy drive look empty. If the drive does not appear at all, do not keep rebooting over and over. On a desktop, reseat the SATA and power cables or the M.2 drive if you are comfortable opening the case. On a laptop, if the drive is user-accessible, reseating it may help, but if you are not used to opening the machine, stop there and move on to hardware diagnosis. If the drive appears and disappears between restarts, that points more toward a failing drive or connection than a simple boot-order issue. ![A desktop tower is connected to a monitor showing a boot device not found message.](https://tse1.mm.bing.net/th?q=Windows%20desktop%20tower%20with%20boot%20device%20not%20found%20screen&w=624&h=352&c=7) ## If it says "Operating system not found" This message usually means the machine found a drive, but it could not find valid boot files or a bootable partition on it. In Windows systems, that often points to a damaged boot record, a missing EFI boot entry, or a broken BCD store. On Linux, it can mean GRUB is missing or the boot partition is damaged. On macOS, the wording is different, but the idea is the same: the startup loader is missing or unreadable. First, check whether the drive is still visible in BIOS/UEFI. If it is, the problem is less likely to be dead hardware and more likely to be startup files or boot mode. If the drive is not visible, follow the drive-focused checks in the other section instead. For Windows, the safest next step is the built-in recovery environment. Boot from a Windows installation USB or recovery media, then choose Repair your computer, Troubleshoot, and Startup Repair. That tool tries to fix the boot path without wiping data. If Startup Repair fails, boot into Command Prompt from recovery and try these commands on the Windows partition letter you see in recovery, not necessarily `C:`. ```cmd bootrec /scanos bootrec /rebuildbcd ``` Command Prompt `/scanos` looks for installed Windows copies. `/rebuildbcd` tries to rebuild the boot list. If those commands find Windows and rebuild the entry, restart and test again. If they report no installations, the partition layout or boot files may be more damaged than a quick repair can fix. For non-Windows systems, the exact repair steps depend on the loader, but the pattern is the same: confirm the disk is seen, then repair the boot loader rather than reinstalling immediately. ![A Windows laptop shows an operating system not found error on the display.](https://tse1.mm.bing.net/th?q=Windows%20laptop%20with%20operating%20system%20not%20found%20screen&w=624&h=352&c=7) ## If it says "Inaccessible boot device" This error is common after a Windows update, a BIOS change, or a storage mode change because Windows cannot talk to the system drive early in startup. The most common causes are a switch between AHCI, RAID, or Intel RST modes, a bad update, or a damaged storage driver path. Start with the least risky checks. If you changed anything in BIOS recently, go back and restore the previous storage mode before trying anything else. A sudden switch from AHCI to RAID, or the other way around, can trigger this error even when the drive itself is fine. ```text BIOS/UEFI > Storage Configuration ``` Settings path If the error began right after an update, use recovery mode and try Startup Repair first. If that does not work, open Command Prompt from recovery and run an offline system file check if you can identify the Windows partition. ```cmd sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows ``` Command Prompt If Windows is not actually on `C:`, replace the letter with the correct offline Windows volume. This checks for system file damage that can sometimes accompany a boot-device error. If you can get into Safe Mode after changing the storage setting back, that is a strong sign the issue was the firmware mode, not a dead drive. If the message keeps returning even after restoring the original settings, or the drive drops out of BIOS/UEFI, suspect a hardware problem or serious file damage. ## If the screen stays black or the logo freezes A black screen or a frozen logo is not always a boot error message. It can mean the system is hanging before the operating system loads, or it can mean the display path is failing and the machine is actually booting in the background. Start by separating display trouble from boot trouble. If the machine has a dedicated graphics card, try another video output, or move the cable to the motherboard video port if your system supports integrated graphics. On a laptop, connect an external monitor if you can. If the external display works but the built-in panel does not, you are dealing with a display problem, not a boot problem. If the logo freezes, remove all external devices and try again. Then power off completely, hold the power button for a few seconds, and restart. That clears some stuck startup states. Bad RAM can also stop the machine before the operating system loads. If the machine has removable memory and you are comfortable opening it, reseating the RAM is a reasonable check. If the machine has multiple sticks, test one at a time if you know how to do that safely. If the machine does not respond differently after these checks, and the drive is still visible in BIOS/UEFI, the problem is less likely to be the operating system and more likely display hardware, memory, or a board-level fault. ## The first checks that solve a lot of cases These are the safest first checks because they do not risk data loss and they often fix the problem on the spot. 1. Shut the machine down fully and disconnect power. On a laptop, unplug the charger. If the battery is removable, take it out only if that is easy and safe for your model. 2. Remove external devices. Unplug USB drives, memory cards, printers, docks, external disks, and any other accessories that can affect boot order. 3. Power on and enter BIOS/UEFI. The key varies by maker, but common ones are `F2`, `Delete`, `Esc`, or `F10`. ```text BIOS/UEFI > Boot ``` Settings path 1. Confirm the internal drive is detected and first in boot order. If a USB device, network boot, or optical drive is first, move the internal SSD or HDD ahead of it. 2. Save changes and restart. If the machine boots now, the issue was likely a temporary boot-order problem or a device blocking startup. If none of these steps changes anything, stop repeating restarts and move to the drive and boot-file checks. Repeated blind restarts do not fix a missing boot path, and they can make troubleshooting harder if the drive is failing. ## How to confirm the drive and boot settings are correct The goal here is to make sure the firmware sees the right drive and is trying the right startup mode. In BIOS/UEFI, check two things: the drive is listed, and the boot mode matches the installation. ```text BIOS/UEFI > Information / Storage / Boot ``` Settings path If the SSD or HDD is listed, that is a good sign. If it is missing, the problem is below the operating system level, and you should stop chasing Windows tools for now. Then check the startup mode: - UEFI is common for modern Windows installations and most newer systems. - Legacy or CSM is used by older installs and some older operating systems. If the drive is visible but the machine still will not start, look for a boot entry such as `Windows Boot Manager`. On a UEFI system, that entry usually needs to be first. If you only see the raw drive name and no boot manager entry, the boot files may be missing or the UEFI entry may have been lost. If you changed boot mode and the machine suddenly starts, note the original setting before you forget it. If changing modes causes the drive to disappear or the error to worsen, put the setting back where it was and continue with recovery tools instead of guessing. ## When the problem is probably the drive itself A failing SSD or HDD usually shows a pattern: the drive vanishes from BIOS/UEFI, takes a long time to appear, makes odd noises in the case of some hard drives, or causes different boot errors on different attempts. A drive that works one day and is missing the next is especially suspicious. If you suspect the drive, stop treating this as a simple boot-order issue. The first goal is to protect the data. If the machine still reaches BIOS/UEFI but not the operating system, avoid repeated repair installs or repeated restart loops. Those can make a weak drive worse. What to do next depends on the type of drive: - If it is a desktop SATA drive, check the data and power cables, then the port. - If it is an M.2 SSD, reseat it only if you are comfortable opening the machine. - If the drive repeatedly disappears across restarts, assume the hardware is unstable. If the drive is still readable, copy important files off it before trying aggressive repairs. If the system cannot hold onto the drive long enough to boot or copy data, that is the point where cloning or recovery help becomes the safer path. A drive that is actively failing can cross the line from flaky to unreadable without warning. ## How to tell if Windows boot files are damaged When the drive is visible but Windows will not start, boot file damage is a common cause. Clues include `Operating system not found`, `Boot configuration data is missing`, `Inaccessible boot device` after an update, or a machine that reaches the Windows logo and then loops back into repair. The safest built-in repair is Startup Repair from Windows recovery media. If that fails, use Command Prompt in the recovery environment and check whether Windows can be found on the disk. ```cmd bootrec /scanos bootrec /rebuildbcd ``` Command Prompt If Windows is found, rebuilding the BCD can restore the boot path. If Windows is not found, the partition may be damaged, the drive letter may not match what you expect, or the disk layout may be more complicated than a simple fix. If you can get to an offline command prompt, a system file check can also help when the core Windows files are damaged. ```cmd sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows ``` Command Prompt Use the correct offline drive letter. If these repair tools report errors they cannot fix, or the error returns after a successful boot and restart, that points to deeper file corruption or a drive that is failing under load. ## How to stop the same boot error coming back Once the machine starts again, verify the fix before you call it done. Restart the machine once, then let it boot normally without a USB installer, external drive, or recovery media attached. If Windows loads the same way twice in a row, the startup path is probably stable. A few habits reduce repeat boot trouble: - Shut down cleanly instead of forcing power off unless the machine is completely frozen. - Keep firmware updates and chipset/storage driver updates controlled, not random. - If you change storage mode in BIOS/UEFI, write down the original setting first. - Leave the boot manager entry alone unless you have a reason to change it. - If the machine has shown drive warnings before, back up files before the next restart. If a boot error returns after a reboot, recheck BIOS/UEFI, confirm the drive is still detected, and look for patterns tied to updates or hardware changes. A recurring error after a clean startup is often a sign of unstable storage or unfinished repair work, not a one-time glitch. ## When to get data recovery or repair help Stop DIY troubleshooting when the drive disappears from BIOS/UEFI, the machine becomes unstable during recovery, or the same error returns after you have already confirmed the boot order and repaired the obvious files. Those are signs that you may be dealing with failing hardware rather than a simple configuration problem. Move to data recovery or repair help sooner if: - The drive is not detected at all. - The drive appears and disappears between restarts. - You hear clicking from a hard drive. - Startup repair and boot repair commands do not hold after reboot. - The files on the machine matter more than getting it started quickly. If you still have access to the drive, back up or clone it before trying more aggressive fixes. If the drive is unstable, every extra boot attempt carries some risk. At that point, the safest choice is to preserve what you can and work from a copy instead of the original disk. ## Conclusion If the machine still will not boot, focus on the layer that is actually failing: the drive, the boot files, BIOS/UEFI settings, or recent hardware changes. If the error comes back after a restart or the drive keeps disappearing, stop pushing it and protect the data first. ## Frequently Asked Questions ### Can a USB drive cause a boot error even if my internal SSD is fine? Yes. Many systems will try USB devices before the internal drive if the boot order allows it, so a flash drive or external disk can trigger a no-boot message even when the internal drive is healthy. ### What if BIOS/UEFI sees the drive but Windows still will not start? That usually points away from hardware detection and toward boot files, boot mode, or storage-driver trouble. Startup Repair and offline boot repair are the right next steps. ### Should I reinstall Windows if I get one of these errors? Not first. Try the safe checks, boot-order fixes, and recovery tools before reinstalling, because a reinstall can overwrite data or hide the real fault if the drive is failing.